How to Post Call Data from TrackDrive to TrackDrive

Overview

Two TrackDrive accounts can exchange call data directly.
The upstream account (the traffic source) posts lead and
call data to the downstream account (the buyer) before
the call bridges.

This guide covers the forward post. For the postback
half, see how_to_postback_trackdrive_to_trackdrive.

Step 1: Create the Global Webhook in the Traffic

Source Account

In the traffic source account, open
Company > Event Triggers from the
sidebar.

Click the Global Event Triggers tab, then click the blue
New From Template button. The modal is titled
"New Template" and asks you to Select A Template To
Copy.

In the template dropdown, search for TrackDrive and
select:

GLOBAL TRIGGER: TRACKDRIVE Post Call Data from TrackDrive
to TrackDrive Account

Click Create. The template ships pre-configured with
the webhook URL, params, and response-acceptance checks
needed for a TD-to-TD post.

Note: the TrackDrive template set is maintained in a
shared templates account.

Step 2: Optional Edits to the Copied Trigger

In most cases no edits are needed. If the downstream
buyer uses different field names or values, you may
adjust:

• Map Lead Data to Custom Values: map values where the two accounts disagree (for example, gender M/F vs Male/Female).
• Webhook Params: standard TrackDrive fields are already configured. If the downstream buyer uses non-standard field names, add per-buyer Filters to remap names at post time.
• Was the Response Acceptable: the template sets response-acceptance checks so the call is only sent when the buyer accepts the data. Clear those values if you want to send the call regardless of response.

Step 3: Activate the Post on a Buyer

To trigger the global webhook for a specific buyer, open
the buyer's edit page and use the Manage next to
Extra Token button to add three tokens:

• buyer_td_subdomain - the buyer account's subdomain (the value before .trackdrive.com).
• buyer_td_lead_token - the lead token the buyer account issued for inbound leads.
• buyer_td_traffic_source_id - the traffic source id the buyer account assigned to you.

The buyer provides all three values in their posting
instructions.Without these tokens on the buyer,
the global webhook does not fire for that buyer.