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 minimal lead
data (state, vertical, jornaya token, and so on) without
personally identifiable information. 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 by try_all_buyers_ping_id,
and the lead is dispatched to the buyer who won the bid.

What to Hand to the Traffic Source.

The traffic source needs the following to integrate:

• The ping URL: /api/v1/inbound_webhooks/ping/:vanity_uri
• The post URL: /api/v1/inbound_webhooks/post/:vanity_uri
• The list of expected fields and their names, taken from the PING / POST instructions.

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 pay for the personally identifying
data and post the full lead. Auto-commit is also supported for
simpler integrations.