Posting Call Data from TrackDrive TS to TrackDrive Buyer

 &

(Optional) Postback from TrackDrive Buyer to TrackDrive TS

Posting Call Data from TrackDrive Traffic Source to TrackDrive Buyer

 In Traffic Source Account - Create a Global Trigger for TD to TD Data Post

TrackDrive has a menu selection at Company/Webhooks where you can place a Global Trigger to Post data from a TrackDrive Traffic Source to a TrackDrive Buyer.

NOTE: If you already have the Global Webhook in your account, skip this step.  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 Call Data from TrackDrive to TrackDrive Account”.

Once the copy is done, you should not have to edit the Trigger or the Webhook normally.  However, you may edit the Trigger created from the copy, then edit the Webhook URL to make some optional changes as documented below:

The Webhook Params copied in on the webhook url are all the fields most commonly shared between systems like first_name, last_name, jornaya_lead_id, etc.  However, the most important and required fields to get a postback from another TrackDrive account are lead_token, caller_id, and call_uuid.

Map Lead Data to Custom Values: This section is used to map any data values that your TrackDrive Buyer may have a different acceptable value than the values you use for the same field in your TrackDrive account.  Advanced users may also wish to map the 3 TrackDrive tokens used in the Webhook URL values here instead of adding the additional tokens in the buyer as described below.  But this section will need field mappings made in certain situations.  For example: the value of “gender” in your TrackDrive is M or F, but your TrackDrive Buyer may have acceptable values of Male and Female, so you would configure a field mapping to handle that for any buyers who need it.

Webhook Params: The standard TrackDrive fields have been configured to be sent from TD to TD already; however, the field names being sent to a TrackDrive Buyer must conform to the name they used if they didn't use the standard TrackDrive Custom Token Naming Convention.  Using Filters, you will be able to map by buyer the field name they want to receive in the IDE post.

Was the Response Acceptable: The settings to ensure the TrackDrive Buyer is accepting the data before sending the call have already been set in the copied Global Webhook of this Trigger.  However, if you want to send the call to the TrackDrive Buyer even if they don’t accept the data, you need to clear the values in the boxes outlined in the picture above.

In Buyer Edit - Triggering the TrackDrive Data Post to a TrackDrive Buyer

To Trigger the TrackDrive Data Post to any TrackDrive Buyer, you simply add the three tokens needed for the Global Webhook to work configured in the Buyer Record Additional Tokens.  You will set these three tokens: “buyer_td_subdomain”, “buyer_td_lead_token”, and "buyer_td_traffic_source_id" to any buyer record using the “Manage Extra Tokens” button as pictured below:

 

 

---

           

 

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: