Setting up Advertiser CallBack/PostBack

Callback Tracking is the method of sending data to another server when a conversion, click or impressions is recorded on your campaigns/offers running through vNative.

These are very useful when your advertisers are using their own tracking system and you can build a network over it and send them data continuously.

NOTE: vNative Servers sends the Data in Callback Real-time.


In this documentation, we will study about adding two types of CallBacks/Postbacks both have the same steps.

  • Global PostBacks/CallBacks
  • Campaign Level PostBacks/CallBacks

Global PostBacks/Callbacks

It Sends every Campaign Data to another server after tracking happens, you can set the Advertiser Global PostBacks/Callbacks on vNative from its Account.

STEP I: Click on Advertisers, then click on manage, click on the Advertiser. Copy the Global PostBack Url.

STEP II: Give that Postback to your Advertiser and Edit or Add the asked Parameter.

STEP III: You can add as many parameters you want to receive as shown in table below


{campaign_id} Id of Campaign {campaign_title} Title of Campaign
{aff_id} ID of Publisher running the Campaign {aff_name}, {aff_username} Name/Username of Publisher running the Campaign
{adv_id} ID of Advertiser for which the campaign is running {tdomain} Tracking domain on which the Campaign Runs
{click_id} Unique ID of Click Event Recorded {click_time} Timestamp for the Click Event
{p1}, {p2}, {p3}, {p4} Tracking Parameter’s which was appended in tracking url {device_id} Device ID For App Installs Campaign
{payout}, {rate} Payout/Sale rate Rate in USD for the Campaign (ONLY in CALLBACKS) {reporting_rate}, {reporting_payout} Payout/Sale rate Rate in Default Currency(ONLY in CALLBACKS)
{agent} Browser on which the Click Event occured {referer} Referring Domian for the Click Event
{country_id} 2 Digit Country ID {ip} Connecting IP of User
{random} 7-15 Digit number randomly selected  {conversion_id}  Unique ID of Conversion Event Recorded
{conversion_ip} IP address of the user device, recorded on conversion
{conversion_date} Date on which conversion took place, formatted as YYYY-MM-DD; For example: ‘2017-06-25’
{conversion_datetime} Date and Time of the conversion, formatted as YYYY-MM-DD HH: MM: SS; For example:  ‘2017-06-25 11:27:06’ {conversion_time} Conversion time formatted as UNIX timestamp in epoch milliseconds; For Example: 1498370226424, // milliseconds

Every Callback/Postback have been reported under our Debug Postback Section.

If you are facing any problem you can contact your account manager and can mail us to

Create Your Account Now!

Get Started with 30 Days FREE Trial Account. No credit card required.

Get Started FREE