In a nutshell, call platforms have to communicate with each for many reasons.  It has always been a good practice to send any data you have about a caller to a buyer if you have it and to request it as a buyer if your traffic source has it.  With the invention of PING/POST, posting data between systems is now being required by both buyers and traffic sources in order to protect data, and also speed up the process of connecting calls.

This document explains what you need to ask for based on if you are the buyer or the traffic source relative to what Tracking Platform you are on in the descriptions below.  

Traffic Source and Buyer

Both use TrackDrive

Direct Post

Detailed Instructions

Traffic Source Checklist:

• Copy in the Global Webhook from Templates named “GLOBAL TRIGGER: TRACKDRIVE Post Call Data from TrackDrive to TrackDrive Account”.  If you already have the Global Trigger, do not copy it in again.
• Ensure the Buyer Record has the 3 tokens set in Manage Extra Tokens: “buyer_td_subdomain”, “buyer_td_lead_token”, and “buyer_td_traffic_source_id”.
• Ensure the buyer has Team Access with the email address of the main user on the Buyer Account.  Ensure API Access it toggled to on, and that on Calls Permissions, it is set to allow Buyer Converted, Revenue, Traffic Source Converted, Payout, and Contact Fields all set to allow Update.
• If you are going to be doing a Postback from the Buyer, set Traffic Source Conversion Settings and Buyer Conversion settings to API Postback instead of the default of Duration.

Buyer Checklist:

• Copy in the Global Webhook from Templates named “GLOBAL TRIGGER: TRACKDRIVE Post  Back Conversions to TrackDrive Traffic Sources”. If you already have the Global Trigger, do not copy it in again.  If you have not done so already, edit the Webhook URL and then edit the Webhook Params and set the auth_token to that of the main user on the Buyer account.
• For any Number you assign to a Traffic Source that should Trigger a Post Back, add the token named “traffic_source_td_subdomain” and put the Traffic Sources Subdomain which is the part of the POST URL between “https://” and “.trackdrive.com”.

Traffic Source and Buyer

Both use TrackDrive

PING/POST

Detailed Instructions

Traffic Source Checklist:

• Copy in a new buyer record for the TrackDrive PING/POST Buyer from Templates. (Setup/Buyers/New from Template)
• Edit the buyer information to match that of the buyer Insertion Order (Number, filters, etc etc)
• Edit the additional tokens to match what is provided on the PING/POST Instructions provided by the TrackDrive Buyer
• Ensure the buyer has Team Access with the email address of the main user on the Buyer Account.  Ensure API Access it toggled to on, and that on Calls Permissions, it is set to allow Buyer Converted, Revenue, Traffic Source Converted, Payout, and Contact Fields all set to allow Update.
• If you are going to be doing a Postback from the Buyer, set Traffic Source Conversion Settings and Buyer Conversion settings to API Postback instead of the default of Duration.
   

Buyer Checklist:

• Copy in the Global Webhook from Templates named “GLOBAL TRIGGER: TRACKDRIVE Post  Back Conversions to TrackDrive Traffic Sources”. If you already have the Global Trigger, do not copy it in again.  If you have not done so already, edit the Webhook URL and then edit the Webhook Params and set the auth_token to that of the main user on the Buyer account.
• For any Number you assign to a Traffic Source that should Trigger a Post Back, add the token named “traffic_source_td_subdomain” and put the Traffic Sources Subdomain which is the part of the POST URL between “https://” and “.trackdrive.com”.

Traffic Source is TrackDrive and Buyer

is Ringba

DIRECT POST

Detailed Instructions

Traffic Source Checklist:

• Ensure you have the global webhook copied in from TrackDrive Templates named “GLOBAL TRIGGER: RINGBA ENRICH: before calling a buyer, send Ringba additional data”.  You can edit the global webhook params to send data relevant to an offer or add multiple fields that send the same data.  For example, TrackDrive standard name for Address is “address” and then gets sent already, but if one of your Ringba Buyers set that field up as “address1” you can send both field names in the webhook payload since Ringba only picks up field names they define as URL Parameters on their side.
• Edit the buyer tokens to include “ringba_enrich_token” and set that to the value in the Webhook URL provided to you by the Ringba Buyer.  This will trigger the global TrackDrive to Ringba IDE data post.

Buyer Checklist:

•  Create custom fields to be picked up by Ringba when data is posted.  The fields that must be setup are “trackdrive_call_uuid” and “trackdrive_subdomain”.  But you may create other URL Parameters.  The standard field names used on TrackDrive can be seen here.
• For any Number you assign to a Traffic Source from TrackDrive that is to do the IDE webhook, get the link for the TrackDrive Traffic Source in the Campaign under the Publishers section.  Provide them with any custom URL Parameters you would like them to send in the data payload.
• Setup the Postback to TrackDrive.

Traffic Source is TrackDrive and Buyer

is Ringba

PING (aka Real Time Bid in Ringba)

Detailed Instructions

Traffic Source Checklist:

• Each time you add a new buyer on TrackDrive that needs to PING Ringba with an “RTB” webhook, you have to copy in the Buyer configured in TrackDrive Templates named “** Ringba RTB Buyer Example". Edit the information you need to for the Buyer.
• On the Webhook URL edit the Webhook Params and fix the URL section to have the Token from the RTB URL provided to you by the Ringba Buyer where the URL has “REPLACE_ME”.

Buyer Checklist:

• Create custom fields to be picked up by Ringba when data is posted.  The fields that must be setup are “trackdrive_call_uuid” and “trackdrive_subdomain”.  But you may create other URL Parameters.  The standard field names used on TrackDrive can be seen here.
• Provide the TrackDrive Publisher the RTB Webhook URL and inform them of any custom URL parameters you would like them to include in the payload.
• Setup the Postback to TrackDrive.

Traffic Source is Ringba and Buyer

is TrackDrive

DIRECT POST

Detailed Instructions

Traffic Source Checklist:

• Create a Pixel in the Campaign to send data to TrackDrive using the Posting Instructions provided by your TrackDrive Target.  To ensure that TrackDrive gets the data before receiving the call, you may wish to set this up as if it was a PING Tree buyer, even tho the response is not a PING Response.  At the time of this document, Ringba only had in the campaign the ability to send data on “Connect”, which would be too late to send data to TrackDrive if we have data needed that the buyer would need (eg: jornaya_lead_id).  You can set the pixel on the on the Campaign if all you are sending is caller_id and call_uuid, but if you are sending any other data like contact info, jornaya_leadid, trusted_form_cert_url, etc, set it up as a Ping Tree Target, so that data the buyer needs is present on call answer at TrackDrive.
• Create a Global Postback in Ringba to accept call updates from any TrackDrive client.  If you use the logic defined under Details Instructions, you need only set up a Webhook for call updates from TrackDrive or any Buyer on any Platform, since the Webhook is only dependent on the ringba_call_uuid being present in data on the call.

Buyer Checklist:

• Provide your Ringba Traffic Source with Posting instructions which can be found in the Offer Edit.
• Create the Global Webhook for updating Ringba calls if you don't already have this webhook copied in from TrackDrive Templates.
• In the number you provide to Ringba Traffic Sources, ensure the token is set to Trigger the global webhook.  Add the token “ringba_webhook_token” and set it to the token value you see in the Webhook URL provided by the Ringba Traffic Source.

Traffic Source is Ringba and Buyer

is TrackDrive

PING (aka Real Time Bidding)

Detailed Instructions

Traffic Source Checklist:

• Setup a Ring Tree Target with the posting instructions provided by your TrackDrive Buyer (see the Detailed Instructions for minimum data requirements)
• Create a Global Postback in Ringba to accept call updates from any TrackDrive client.  If you use the logic defined under Details Instructions, you need only set up a Webhook for call updates from TrackDrive or any Buyer on any Platform, since the Webhook is only dependent on the ringba_call_uuid being present in data on the call.

Buyer Checklist:

• Provide your Ringba Traffic Source with Posting instructions which can be found in the Offer Edit for the Incoming Webhook.
• Create the Global Webhook for updating Ringba calls if you don't already have this webhook copied in from TrackDrive Templates.
• In the number you provide to Ringba Traffic Sources, ensure the token is set to Trigger the global webhook.  Add the token “ringba_webhook_token” and set it to the token value you see in the Webhook URL provided by the Ringba Traffic Source.