How to Configure a Traffic Source S2S Postback URL

Written by ClickFlare
Updated 2 years ago

A Server-to-Server (S2S) postback URL allows you to send data from one server to another by requesting a unique URL via an HTTP method. A postback URL request is sent to the traffic source, when a conversion is successfully registered within the connected ClickFlare campaign.

Postback URLs include unique parameters defined by the traffic source to send requested data variables. The most used of these variables, is a click id. Click ids are random alphanumeric strings generated by a traffic source to identify and record the activity of a visitor. They have become the standard method of tracking conversion events per user. In a configured ClickFlare traffic source element, click id tokens are mapped in the Parameters section. The values you put, can be found in the traffic source's documentation. 

We recommend looking at your traffic source's tracking documentation beforehand, to see which parameters it supports.
Note: Some traffic sources do not send the click id variable. 

All click ids sent by a traffic source are recorded as external ids in ClickFlare. Our supported {externalid} token needs to dynamically relay click ids to the defined postback URL when a conversion is successfully registered. 

Note: Instead of a global postback URL option, based on a click id parameter, some traffic sources also require additional parameters, such as account ids or campaign ids.

In ClickFlare you'll find a considerable amount of URL tokens available to choose from, enabling you to pass back important data to the traffic source. 

The available tokens cover the following data variants:

  • Data initially passed from the traffic source: {externalid} and custom variables, {var1}, {var2}, {var:variablename}

  • Identifiers of associated elements within ClickFlare, such as: {}, {}, {}

  • Visit and conversion data recorded within the campaign: {ip}, {}

Note: Tokens can only be defined and added to the traffic source postback URL. They cannot be used in the pixel redirect URL.

Depending on the types of data you would like to pass back, here's a table of ClickFlare's tokens that you can use:

Data Type

Available Tokens

Visit Geo Data

{country}, {countryname}, {region}, {city}

Operating system / version

{os}, {osversion}

Browser / version

{browser}, {browserversion}

Device type / Brand / Model

{device}, {brand}, {model}



Conversion data: Transaction ID / Click ID / Payout / Cost model CPA & RevShare

{}, {}, {payout}, {conversion.cost}

The existing {} token has been extended by the {conversion.cost} version. If you still use the {} token, you should immediately replace it with the updated version, because the previous token is already deprecated.

Traffic source data

{externalid}, {var1}{var2}, {var3}{var:variablename}

Referrer data / IP

{referrerdomain}, {ip}

ISP / Carrier / Connection type

{isp}, {carrier}, {connection.type}

ClickFlare Element IDs

{}, {}, {}{}

Did this answer your question?