How to Post Call Data from Ringba to TrackDrive (Direct Post)

Overview

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

A Ringba traffic source can post call data to a TrackDrive buyer account in the direct-post model:
when a call connects in Ringba, a Tracking Pixel fires to TrackDrive's Leads Capture API so the buyer has identifying data the moment the call arrives. An optional postback from TrackDrive back to the Ringba traffic source closes the loop on revenue attribution.

This article covers the inbound direction (Ringba to TrackDrive). The outbound equivalent is how_to_post_data_trackdrive_to_ringba_ide.

Step 1 (In TrackDrive): Get the Lead Token and Traffic Source ID

In the TrackDrive buyer account, open the Offer that should receive these calls. From the Offer edit page, click the Posting Instructions button to open the posting documentation page. Select the Traffic Source ID for the Ringba Traffic Source. The page exposes the values Ringba needs:

• lead_token - the Offer's inbound lead token.
• traffic_source_id - the Traffic Source record id assigned to this Ringba partner.

Step 2 (In Ringba): Create the Tracking Pixel

In Ringba, open the campaign the calls flow through and add a Tracking Pixel.

• Name: a descriptive label.
• Fire Pixel On: Connected (Answered) when sending data as the buyer answers. Alternatively, Finalized with a tag filter on call length for unrouted calls that should be monetized via a TrackDrive Lead-to-Call schedule.
• URL: https://<trackdrive_subdomain>.trackdrive.com/api/v1/leads/capture
• Turn on Advanced Instructions to switch to JSON POST.
• HTTP Method: POST
• Content Type: application/json
• Body (minimum payload):

{
  "lead_token": "<lead_token_from_step_1>",
  "traffic_source_id": "<traffic_source_id_from_step_1>",
  "caller_id": "[tag:InboundNumber:Number]",
  "ringba_call_uuid": "[Call:InboundCallID]"
}

• Headers: empty
• Authentication: empty
• Tag Filters: Connection - Target - Id set to the TrackDrive Target(s) that should trigger the pixel.

Add first_name, last_name, jornaya_leadid, trusted_form_cert_url, and any other contact fields the Offer expects on the same JSON body.

Step 3 (Optional In Ringba): Global Postback Back to TrackDrive's Traffic Source

If the TrackDrive buyer converts and the Ringba traffic source wants a payout postback, create a
Global Postback Webhook in Ringba.

• Ringba menu: Integrations > Webhooks > Create Webhook.
• Name: Global Buyer Revenue Postback.
• Call Token: call_id
• Revenue Token: call_revenue
• Fire Conversion: sale_successful=true

The exact field names call_id, call_revenue, and sale_successful cannot be customized. TrackDrive's global hook on each client expects those literal names.

Ringba emits a URL like:

https://webhook.ringba.com/hook/<token>?call_id=[callUUID]&call_revenue=[conversionAmount]&sale_successful=true

The value after /hook/ is the ringba_webhook_token that TrackDrive uses to route the postback.

Step 4 (In TrackDrive): Install the Global Postback Trigger

In the TrackDrive buyer account, open Integrations > Event Triggers. On the
Global Event Triggers tab, click New From Template. Search the dropdown for Ringba and
select:

GLOBAL TRIGGER: RINGBA WEBHOOK: Do a Postback for Ringba Traffic Sources if ringba_call_uuid is populated

Click Create. No edits to the Trigger or URL are typically required.

Note: if the template is not available in your dropdown, contact TrackDrive support.

Step 5 (In TrackDrive): Map ringba_webhook_token

The trigger fires whenever a call has both ringba_call_uuid and a resolvable ringba_webhook_token. Two ways to supply the token:

• Option 1 (per-Number override): on each Number assigned to the Ringba traffic source,
  add an Extra Token named ringba_webhook_token set to the Ringba webhook token value. Use this when a single traffic source supplies many webhook tokens.

• Option 2 (preferred when the traffic source uses one global Ringba webhook): on the copied
  trigger, edit the Webhook URL and open the Ringba Webhook Token Field Mapping Group. Click + New Custom Field Mapping, filter by the traffic source record, and map the Ringba webhook token value.