On Buyer Platform

Post Back Call Data to TrackDrive using “auth_token”

URL: 

Below is the URL to use but you MUST replace the TrackDrive Subdomain to the Subdomain of the TrackDrive client.  HINT: TrackDrive will send “trackdrive_subdomain” as a field along with “trackdrive_call_uuid" . If you can do Token Replacement in the Subdomain part of the domain name, you can make this a GLOBAL postback for all of TrackDrive Traffic Sources. 

https://TRACKDRIVE_SUBDOMAIN_HERE.trackdrive.com/api/v1/calls/update_call/TRACKDRIVE_CALL_UUID_HERE

Example 1) Your platform can not replace the SubDomain :

https://example_subdomain.trackdrive.com/api/v1/calls/update_call/[trackdrive_call_uuid]

Note that example_subdomain is a static value you type in that spot, while the TrackDrive Call UUID is replacing the value from the database on your system using what is called Token Replacement.  In this example, we are using square brackets for token replacement, but many systems use different methods that you must know.  If you are not sure, ask your Platform Support Team.  For example, while TrackDrive uses [token_name], others might do {{token_name}} and ViciDial is really unique: --A--token_name--B--

There really is no rhyme or reason to what a programmer decides to use to indicate you want to replace that part of the URL or Data being sent with information from the database, they choose a pattern they don't think would ever happen naturally in any string.

Example 2) Your platform can replace the SubDomain :

https://[trackdrive_subdomain].trackdrive.com/api/v1/calls/update_call/[trackdrive_call_uuid]

HTTP Method: 

POST

Headers: 

Content Type: application/json  (NOTE: If doing a POST URL or GET do not use this header)

Body:

For ease in setting this up, the JSON Payload is below, just fix the highlighted fields 

{
    "auth_token": "REPLACE_ME: With Your TrackDrive Authorization Token",
    "buyer_converted": "true",
    "revenue": "REPLACE_ME: Using Token Replacement OR a Static Dollar Amount",
    "offer_converted": "true",
    "post_call_tokens": {}
}

Find your Auth_Token when you login to TrackDrive and use the User Menu/Profile.  Your TrackDrive Traffic Source can not Provide this to you, but you may reach out to support@trackdrive.com from the email on your TrackDrive Team Account, and we can get this for you.

The JSON Payload above is the minimum setup to use to Postback to TrackDrive.  However, more data can be appended if available in the Buyer data.  For example, the “first_name” and “last_name” may be fields a TrackDrive user wants back in the hashed “post_call_tokens” values of the Postback.  However, additional data is usually not sent on Postbacks for most tracking purposes, and the example payload above is all you will need.

NOTE: Your TrackDrive Traffic Source (publisher/affiliate/vendor) must have the email address you login to TrackDrive with on a TEAM that has permissions to update a call.

NOTE: It is preferable that the Authorization uses the method with credentials in the Header vs the Data on the webhook.  Contact TrackDrive support for help in getting your Private and Public Keys for Basic Authorization.

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: