Postback Conversions from Ringba to TrackDrive

(Using “auth_token” Authorization)

NOTE: Before a buyer can Postback conversion to TrackDrive, in TrackDrive you must add the Buyer to a Team and turn on the API Permission, then on the Calls section, give permission to update the Buyer Converted, Revenue, Traffic Source Converted, Payout, and Contact Fields (optional, only needed if additional data will come in the Postback payload).

In Ringba - Setup Postback Pixel to TrackDrive in the Campaign

Ringba has a section of the Campaign Setup for Tracking Pixels, you have the option to use existing Pixels or add a new one, for simplicity, we will only discuss adding a new pixel to be used to send the Postback to TrackDrive when a call converts for the Publisher.  NOTE: Once you have a pixel configured for a Publisher Postback, it can be used on any Campaign in Ringba for a Postback to TrackDrive since we are using the “trackdrive_call_uuid” to do the update to the call, which will allow this to work for any call update on any offer.

Pictured below is a setup for posting data to TrackDrive when the Publisher converts on a call:

Name: Add a logical name for this Pixel configuration. For example: " TrackDrive Global Postback for Publisher Chris Jones".

Fire Pixel On: Select “Payout” as the trigger point for this pixel to fire.  You will want to set two filters as the Trigger for when the Postback will fire to TrackDrive.  The first will be a filter for the Publisher who is sending you the call, and the second will be a filter to ensure the field named “trackdrive_call_uuid” exists in the call data from an IDE or RTB data post from TrackDrive.

URL: Below is the URL to use but you MUST replace the TrackDrive Subdomain:

https://TrackDrive_Publisher_Subdomain_Here.trackdrive.com/api/v1/calls/update_call/[tag:user:trackdrive_call_uuid]
 

NOTE: The Filter used above to check if the TrackDrive Call UUID exists assumes that you created the URL Parameters to accept the TrackDrive Subdomain (future need to place a single Postback Pixel to all TrackDrive Publishers) and TrackDrive Call UUID as fields.

NOTE: Ensure that you turn on the Advanced Options so you can change to a Post JSON Protocol configuration as pictured.

HTTP Method: Select “POST” as the protocol. 

Content Type: Select “application/json” as the Content-type header.

Body:

(for ease in setting this up, the JSON Payload is below, just fix the fields in squiggly brackets. The tokens in square brackets do not change and you use them exactly as denoted.)

{
    "auth_token": "TrackDrive_Auth_Token_From_Profile",
    "buyer_converted": "true",
    "revenue": "[Call:ConversionPayout]",
    "offer_converted": "true",
    "post_call_tokens": {}
}

The JSON Payload above is the minimum setup to use to Postback to TrackDrive from Ringba.  However, more data can be appended if available in the Ringba data.  For example, the “external_buyer_forwarded_duration” may be a custom field 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.