Traffic source postback
Some traffic sources optimize campaigns internally which requires you to pass information about conversions.
How it works
Generally, here is how conversions get passed to the traffic source:
- — A traffic source uses a special token to pass their own click ID to Binom.
- — If a conversion gets registered for that click, Binom will send out a postback (S2S).
- — The postback to be sent will contain the ID that Binom had received from the traffic source.
S2S Postback setup
Binom has two places where the S2S postback could be set up:
- In Postback URL when editing the Traffic Source;
- In Advanced Settings > S2S Postback when editing the campaign.
Please note that the campaign and traffic source settings related to postbacks will be taken into account. In case there is a contradiction, the value set in the campaign will be used.
The traffic source ID is passed using {externalid}. You can also pass other parameters in the postback link, such as {cnv_status} for conversion status.
-
Available tokens
-
Token Description {clickid} Click ID {affiliate_network_id} ID aff.network {affiliate_network_name} Aff.network name {browser_name} Browser name {browser_version} Вrowser version {campaign_id} Campaign ID {campaign_key} Campaign key {campaign_name} Campaign name {city} City {clickcost} Click cost {continent} Continent {continent_code} Continent code {country} Country {country_code} Country code {date} Click date {device_brand} Brand of a device {device_model} Model of a device {device_name} Name of a device {device_type} Type of a device {campaign_domain} Campaign domain {event1}, {event2} ... {event30} Event number {externalid} External ID token of the traffic souce {ip} IP of a click {isp} Internet Service Provider {landing_id} Landing ID {landing_name} Landing name {landing_number} Number of a landing in a campaign's path {language} Browser language {lp_key} Landing key {offer_id} Offer ID {offer_link} Offer link {offer_name} Offer name {offer_number} Number of an offer in a campaign's path {os_name} User OS {os_version} User OS version {path_name} Path name {path_number} Path number in a campaign {referer} Referer link {referer_domain} Referer domain {region} User region {region_code} Region code {rule_name} Name of a rule {resolution} Device resolution {state} State/Province {state_code} State/Province code {t1}, {t2}, {t3} ... {t30} Traffic source tokens {traffic_source_id} Traffic source ID {traffic_source_name} Traffic source name {uclick} Uniqueness service parameter {unixtime} Server time in a Unix-time format {unixconversiontime} Conversion occurance time in a Unix-time format {user_agent} User agent {week} Week number {owner_id} ID of the campaign's owner {owner_name} Name of the campaign's owner
-
Detailed information on postbacks can be found in Binom's conversion log.
ExoClick example
Let us take a look at ExoClick for a setup example:
- Specify the relevant token as External ID in the traffic source in Binom. For ExoClick, it's
{conversions_tracking}.
- Specify
{externalid}in the Postback URL of that same traffic source and use your ExoClick API key in API_ID.
Status-postback relation
Some traffic sources might require different postback links depending on the conversion status.
In that case you can enable Status-postback relation:
Specify the required conversion status in Conversion status, and put the corresponding postback link into Postback link. This setup will have Binom sending out different postbacks according to the conversion status received.
+Add will add another status-postback pair to the list.