How to Ping/Post from Ringba to TrackDrive

Overview

Note: steps performed inside Ringba's own interface
reflect that product as of June 2026 and may differ as
Ringba updates its UI.

Ringba's ping/post equivalent is a Ring Tree
Target inside a Ring Tree. Ringba pings the
TrackDrive buyer's inbound webhook for a bid, and
if TrackDrive responds with acceptance, Ringba
posts the call and transfers the caller to the
TrackDrive DID.

Use this pattern when the TrackDrive buyer must
pre-qualify leads (state eligibility, caps, dedupe)
before committing to take the call.

Step 1 (In TrackDrive): Confirm the Buyer Is

Accepting Ping/Post

In the TrackDrive buyer account, confirm the
buyer's Conversion Setting is of type PING (not
DURATION) and that the buyer is attached to an
inbound webhook on the Offer. The URLs TrackDrive
exposes look like:

• Ping: https://<subdomain>.trackdrive.com/api/v1/inbound_webhooks/ping/<vanity_uri>
• Post: https://<subdomain>.trackdrive.com/api/v1/inbound_webhooks/post/<vanity_uri>

These would appear once you are done generating
the Ping/Post instructions from the Posting instructions
inside the offer, you would be required to key in
source ID and the DID you want the source to route
to on successful pings. After putting in both traffic
source ID and DID, click on get instructions link and
share the URL with the traffic source.

Step 2 (In Ringba): Configure the Ring Tree

Target

In Ringba, navigate to Ring Trees > Manage Ring
Tree Targets and create a new Target.

• Dynamic Number: false. Use a Static DID supplied by the TrackDrive buyer. SIP parsing for dynamic delivery is not supported at time of writing.
• Confirmation Request: true. Real-Time Bidding without a Confirmation Request triggers warnings; TrackDrive's ping/post is designed for two-step exchanges.

Ringba's ring tree cannot parse a ping id across
to a separate post in the way some platforms do,
so any contact fields destined for the buyer must
be sent on the ping payload.

Step 3 (In Ringba): Revenue Settings

Pick one based on the contract with the TrackDrive
buyer:

• Static Revenue: only if the TrackDrive buyer will not postback revenue. Static cannot be used together with postbacks.
• Use Payout Returned From TrackDrive: pick this when TrackDrive's ping response carries the authoritative bid. Only one buyer on the ring tree can be checked for this option because Ringba does not surface multi-buyer ping responses in the portal.
• Override With Postback: conversion type Webhook Postback. Use this when the buyer will post revenue back after the call.

Step 4 (In Ringba): Ping Request Settings

• URL: the ping URL from Step 1.
• HTTP Method: POST
• Authentication: blank.
• Content Type: application/json
• Body (minimum):

{
  "trackdrive_number": "<assigned_buyer_did>",
  "traffic_source_id": "<assigned_traffic_source_id>",
  "caller_id": "[tag:InboundNumber:NumberE164]",
  "ringba_call_uuid": "[Call:InboundCallID]"
}

When the Ring Tree Target is part of an RTB
number, [Call:InboundCallID] is an RTB id rather
than a final Call ID. Use a Target Connect trigger
on the Campaign to forward the final
trackdrive_call_uuid to TrackDrive later.

Include a test helper so a staging call can be
pinged without triggering live routing: add
"ping_test": "true" to the body during setup,
then remove it before going live.

Step 5 (In Ringba): Parse Ping Response Values

TrackDrive's ping response is JSON. Configure
Ringba to read these expressions:

• Dynamic Bid Parsing: JPath, buyers[0].offer_conversion_payout
• Call Acceptance Parsing: JavaScript, return JSON.parse(input).status == "accepted";
• Dynamic Duration Parsing: JPath, buyers[0].current_conversion_duration

Some TrackDrive clients pay on a static forwarded
timer and return buyers[0].offer_conversion_duration
instead. Confirm with the TrackDrive buyer before
going live.

Step 6 (In Ringba): Confirmation Request (Post)

• Bid ID Parsing: JPath, try_all_buyers_ping_id.
• URL: the post URL from Step 1.
• HTTP Method: POST
• Authentication: blank.
• Content Type: application/json
• Body (minimum):

{
  "traffic_source_id": "<assigned_traffic_source_id>",
  "caller_id": "[tag:InboundNumber:NumberE164]",
  "ringba_call_uuid": "[Call:InboundCallId]",
  "ping_id": "[bid-id]"
}

Ringba has no parsing to read the Lead ID
TrackDrive returns in the POST response at time of
writing. The call is transferred to the
TrackDrive-assigned DID on confirmation.

Step 7 (Optional): Postback From TrackDrive to

Ringba

Follow how_to_post_call_data_ringba_to_trackdrive
Step 3 through Step 5 to wire the Global Postback
Webhook in Ringba and the Global Ringba Postback
Trigger in TrackDrive. The postback half is
identical between direct-post and ping/post
configurations.