Ping/Post Flow
How Ping/Post Works
Ping/Post is a two-step process that matches inbound leads with available buyers before a call is ever connected.
Step 1: PING
Send a PING request with lead data (caller ID, contact fields, traffic source) to check which buyers are available. TrackDrive evaluates buyer schedules, concurrency caps, geographic targeting, and custom filters to return a list of matching buyers with their bids.
Step 2: POST
After selecting a buyer from the PING response, send a POST request with the
ping_id to retrieve a unique tracking number. Alternatively, use the
try_all_buyers_ping_id to let TrackDrive try all
matched buyers in priority order. Forward the inbound call to the tracking number
to connect the caller.
Post-Only Mode
For simpler integrations, TrackDrive also supports a post-only mode that skips the PING step. Submit the lead directly via POST and the system finds available buyers and returns a tracking number in one step, reducing integration complexity.
Dynamic Buyer Selection
TrackDrive evaluates buyers in real time using multiple criteria to find the best matches:
- Business hours and schedules — only route to buyers who are currently accepting calls
- Concurrency caps — respect per-buyer limits on simultaneous active calls
- Geographic targeting — match callers to buyers by state, area code, or zip code
- Contact field filters — filter on custom lead attributes like vertical, age, or insurance type
- Bid-based ranking — sort available buyers by payout to maximize revenue
Ping/Post Buyers
Buyers can be configured to participate in Ping/Post by enabling external ping endpoints on their buyer settings. When a PING comes in, TrackDrive can fan out sub-pings to each buyer's external system, collecting real-time availability and bids before responding to the publisher.
Rate Limiting
Protect your endpoints and buyers with built-in rate limiting at multiple levels:
- Per-minute, per-hour, and per-day rate limits on each Ping/Post endpoint
- Per-traffic-source rate limits to control volume from individual publishers
- Traffic Source Rate Limiters for granular per-source overrides
Concurrency Cap Buffer
To prevent race conditions when multiple PINGs arrive simultaneously, configure a concurrency cap buffer percentage. This reserves a portion of each buyer's concurrency cap so that POST requests are not rejected due to rapid-fire PINGs consuming all available slots.
Test Mode
Enable test mode on any Ping/Post endpoint to receive detailed diagnostic logs with each request. Debug buyer matching, filter evaluation, and response construction without affecting live traffic.