...
Our platform supports many of the possible macros that can be passed back to the publisher to maintain a highly transparent transaction between you and the publisher’s tracking system. The macros used are always contained between curly brackets “{}” and include underscores. Here is the complete list of macros that the platform supports:
Parameters:
{aff_name}, {aff_username}
Token | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
{adv_id} | User ID of Advertiser the advertiser for which the campaign is running .(alias to {advertiser_id}) | ||||||||||||
Alias for {advadvertiser_id} | User ID of the advertiser for which campaign is running | ||||||||||||
{aff_id} | User ID of Publisher running the Campaignthe publisher (alias to {publisher_id}) | ||||||||||||
{aff_name} | Name of Publisher running the Campaign (alias to {publisher_name}) | ||||||||||||
{aff_username} | Username of Publisher running the Campaign (alias to {publisher_username}) | ||||||||||||
{agent} | Browser on which the Click Event occurred | ||||||||||||
{campaign_id} | Campaign IDOffer ID (alias to {offer_id}) | ||||||||||||
{campaign_title}Campaign title | Title of Offer (alias to {offer_title}) | ||||||||||||
{click_id} | Unique ID of Click Event RecordedClick ID generated by tracker | ||||||||||||
{click_time} | Timestamp for the Click Event | ||||||||||||
{conversion_date} | Date on which conversion took place, formatted as Conversion Date (YYYY-MM-DD (example: 2017-06-25DD) | ||||||||||||
{conversion_datetime} | Conversion Date and Time of the conversion, formatted as YYYY(YYYY-MM-DD HH:MM:SS(example: 2017-06-25 11:27:06mm:ss) | ||||||||||||
{conversion_id} | Conversion ID of the record of any Conversion, Sale, Goal etc. | ||||||||||||
{conversion_time} | Conversion Time HH:mm:ss | ||||||||||||
{country_id} | 2 Digit Country ID | ||||||||||||
{currency} | Conversion currency | ||||||||||||
{ip} | Click IP of User | ||||||||||||
{offer_id} | Offer ID | ||||||||||||
{offer_title} | Title of Offer | ||||||||||||
{p1} | Custom parameter, sub ID 1 | ||||||||||||
{p2} | Custom parameter, sub ID 2 | ||||||||||||
{p3} | Custom parameter, sub ID 3 | ||||||||||||
{p4} | Custom parameter, sub ID 4 | ||||||||||||
{payout} | Specified payout for publisher, in conversion currency | ||||||||||||
{payout_usd} | {publisher_id} | {publisher_name} | {publisher_username} | {random} | {referer} | {sale_amount} | {sale_amount_usd} | {status} | {sub1} | {sub2} | {sub3} | {sub4} | {txn_id} |
{campaign_id}
Id of Campaign
{campaign_title}
Title of Campaign
{aff_id}
ID of Publisher running the Campaign
Specified payout for publisher, in USD | |
{publisher_id} | User ID of the publisher (hash) |
{publisher_name} | Name of Publisher running the Campaign |
{ |
publisher_ |
username} |
{adv_id}
ID of Advertiser for which the campaign is running.
{adv_id} is an alias for {advertiser_id}!
{tdomain}
Tracking domain on which the Campaign Runs
{click_id}
Unique ID of Click Event Recorded
{click_time}
Username of Publisher running the Campaign | |
{random} | 7-15 Digit number randomly selected |
{referer} | Referring Domian for the Click Event |
{ |
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 occurred
{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
...
sale_amount} | Amount of generated sale (on conversion), in conversion currency. Not always available! |
{sale_amount_usd} | Amount of generated sale (on conversion), in USD. Not always available! |
{status} | Conversion status |
{sub1} | Tracking parameter which was appended to conversion by advertiser |
{sub2} | Tracking parameter which was appended to conversion by advertiser |
{sub3} | Tracking parameter which was appended to conversion by advertiser |
{sub4} | Tracking parameter which was appended to conversion by advertiser |
{txn_id} | Unique Transaction ID |
How to Test Postback
Under the “Account” menu, there is a “Postback” sub-menu that will open the Global Postback page
...