What is Ping/Post and What Do I Give to a Traffic Source?

The Two-Step Bidding Model

Ping/post is a two-request protocol that lets multiple buyers bid on the same lead before the lead is committed. The traffic source first sends a ping containing the lead data buyers bid on (state, vertical, jornaya token, and so on). A new ping webhook requires the caller's phone number on every ping by default, and rejects a ping that carries no caller ID or an invalid one. Trackdrive shops the ping to eligible buyers, collects their bids, and returns the winning bid (or a list of bids) to the traffic source.

The traffic source then sends a post containing the full lead, referencing the original ping's ID, and the lead is dispatched to the buyer who won the bid.

What to Hand the Traffic Source

The traffic source needs four things to integrate:

• The ping URL: /api/v1/inbound_webhooks/ping/:vanity_uri
• The post URL: /api/v1/inbound_webhooks/post/:vanity_uri
• The company access token, to be sent as either an Authorization header or an auth_token parameter.
• The list of expected fields and their names, taken from the Posting Instructions on the offer.

Why the Bid is Returned, Not Auto-Committed

Returning bids to the traffic source rather than auto-posting lets the traffic source decide whether the bid clears their own margin floor before they post the full lead. Auto-commit is also supported for simpler integrations.