PING/POST: TrackDrive to TrackDrive
PING/POST from TrackDrive to TrackDrive
(Using a Static Number on TrackDrive)
In Traffic Source Account - Create PING/POST Buyer
To do a PING/POST on TrackDrive to a TrackDrive Buyer, you will make use of a PING type of Conversion Setting on the TrackDrive Buyer that you setup.
The easiest way to do this, is to copy the buyer from Templates named “** TrackDrive - PING/POST Sample Buyer”. From the Setup/Buyers menu option, use the blue button named “New From Template” and copy in the buyer. Edit the Attribute information to have the correct Number, Buyer ID, Name, etc etc to match your new buyer information.
There are some Extra Tokens that copy in with values of “REPLACE_ME” that you will get from the Posting Instructions the Buyer gives you on how to do the PING/POST before sending a call. These tokens are named: buyer_td_vanity_url, buyer_td_subdomain and buyer_td_traffic_source_id.
The values are found in the posting instructions as shown below:

You can edit the Conversion Settings Webhook and the Webhook for the post in the buyer to match exactly what you want to send and any extra data the buyer is requesting.
POSTBACK - TrackDrive Buyer to TrackDrive Traffic Source
Postback Conversions from TrackDrive Buyer
to TrackDrive Traffic Source
In TrackDrive Buyer Account - Create a Global TrackDrive Postback Trigger
TrackDrive has a menu selection at Company/Webhooks where you can place a global trigger to Postback to any call that is from a TrackDrive Traffic Source and the traffic_source_lead_id field has a value. If you have not done so already, copy in the Global Trigger from TrackDrive Templates and then only a few things need to be changed.
From Company/Webhooks, click on the blue “New From Template” button to find available webhook templates and search for “TrackDrive”. You will find a webhook to copy in called “GLOBAL TRIGGER: TRACKDRIVE Post Back Conversions to TrackDrive Traffic Sources”. You must edit this global webhook to set the Webhook Param for the “auth_token” value and set it to the main user's login Auth Token that can be found under the profile of the main TrackDrive User.
This global Trigger will be Triggered by the DID you give to the publisher having the token named “traffic_source_td_subdomain” set to a value and the traffic source sending in the “traffic_source_lead_id” field set to their call_uuid value.
In Number Edit - Triggering the TrackDrive Post Back to a TrackDrive Traffic Source
For any Number you assign to a traffic source that they wish to get a Post Back made, simply add the token “traffic_source_td_subdomain” and set it to what your Traffic Source tells you their subdomain is for their account. If they don't want a postback on all calls, they can have you not set their subdomain on the DID to stop the Post Back from happening.
Setting Buyer Permissions on a Team
On Traffic Source TrackDrive Platform
Giving the Buyer Permission to Update Calls
The postback won't work unless the Buyer has a Team setup in TrackDrive with Permissions to update the call. The best way to make a buyer team is to edit the buyer record, go down to the Team Access section and add a new team for a buyer by entering the email address. Once a buyer team is added, you can see the permissions under Company/Teams and edit the team permissions as pictured below:
