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

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 Inbound Data Enrichment (IDE) endpoint accepts a
GET/POST with URL parameters per call. This guide wires a
TrackDrive traffic source account to post lead data to a
Ringba buyer's IDE endpoint before bridging, and covers
the optional postback from Ringba back to TrackDrive.

Field Naming Guidance

Ringba calls custom fields "URL Parameters"; TrackDrive
calls them "Contact Fields". Pick one field name per concept
(for example, first_name) and use it everywhere. Both
platforms can remap names when a publisher uses
something different.

Step 1 (In Ringba): Create URL Parameters

In Ringba, navigate to Integrations > URL Parameters
and click + CREATE URL PARAMETER. For each field:

• URL Parameter: the database name (no spaces). Create at least trackdrive_call_uuid and trackdrive_subdomain so that any postback from Ringba back to TrackDrive can reference the call.
• Reporting Menu Name: set to User if the field must be selectable on reports, pixels, or webhooks.
• Report Name: the friendly name on report headers. For any field used in tag filters that trigger pixels, the URL Parameter and the Report Name MUST match exactly, or pixel filters fail to match.

Step 2 (In Ringba): Copy the IDE Webhook URL

Edit the Ringba campaign, scroll to Publishers, and
click the hyperlink icon to copy the publisher URL.

Ringba emits a URL like:

https://display.ringba.com/enrich/1882570683251575656?callerid=<<E.164-CALLER-NUMBER>>&key1=value1&key2=value2

Rewrite it to pass TrackDrive tokens:

https://display.ringba.com/enrich/1882570683251575656?callerid=+1[caller_id_short]&trackdrive_call_uuid=[call_uuid]&first_name=[first_name]&last_name=[last_name]&email=[email]&address=[address]&city=[city]&state=[state]&zip=[zip]&jornaya_leadid=[jornaya_leadid]&trusted_form_cert_url=[trusted_form_cert_url]

The only part that changes per buyer is the numeric id
after /enrich/. That id goes into a per-buyer token
named ringba_enrich_token.

Step 3 (In TrackDrive): Install the Ringba IDE

Global Webhook

In the TrackDrive traffic source account, open
Company > Event Triggers. On the
Global Event Triggers tab, click New From Template.

Search the Select A Template To Copy dropdown for
Ringba and select:

GLOBAL TRIGGER: RINGBA ENRICH: before calling a buyer,
send Ringba additional data

Click Create. No edits are typically required.
Optional edits:

• Map Lead Data to Custom Values: map values where Ringba and TrackDrive disagree (for example, M/F vs Male/Female). Standard Ringba and TrackDrive field names are already mapped. Ringba ignores extra params it does not recognize as URL Parameters.
• Was the Response Acceptable: template sets checks so the call only proceeds when Ringba accepts the data. Clear the values to send regardless.

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

Step 4 (In TrackDrive): Activate the Post on a Buyer

For each buyer that should enrich through Ringba, open
the buyer's edit page and use the Manage button next
to Extra Tokens add:

• ringba_enrich_token - set to the numeric id from the Ringba publisher URL (the value after /enrich/).

Step 5 (Optional): Ringba Postback to TrackDrive

Before configuring the postback, grant the buyer
permission on TrackDrive to update calls:

1. Open the buyer's edit page on TrackDrive.
2. Scroll to Team Access and add a team by email.
3. Open Company > Teams, edit the new team's permissions, and turn on:
   • Calls: Buyer Converted?, Buyer Revenue, TS Converted, TS Payout
   • Contact Fields (only if the postback will include contact data)
4. Create an Auth Basic for the buyer to use in their headers for the postback by going to Integrations and then selecting New Access Token, grant access to calls so the postback is allowed through.

In Ringba, set up a Postback Pixel on the campaign:

• Name: descriptive, for example TrackDrive Global Postback for Publisher <name>.
• Fire Pixel On: Payout. Two filters: publisher sending the call, and trackdrive_call_uuid exists.
• URL: https://<traffic_source_subdomain>.trackdrive.com/api/v1/calls/update_call/[tag:user:trackdrive_call_uuid]
• Turn on Advanced Options to switch to JSON POST.
• HTTP Method: POST
• Authorization: Basic
• Content Type: application/json
• Body (minimum payload):

{
   "buyer_converted": "true",
  "revenue": "[Call:ConversionPayout]",
  "offer_converted": "true",
  "post_call_tokens": {}
}