General Logic for Setting up a Postback from PeerClick

1. Getting source cid

Cid (click ID) is a unique click identifier generated by the traffic source.

Cid is passed with the campaign link through the macro of the source responsible for sending the cid to the tracker side in the tracker's reserved parameter external_id.

2. Registering a conversion in the tracker

To send a conversion postback to a traffic source, conversion data must be received by the tracker in any available way:

- via s2s postback from the offer source (for example, from the affiliate network),

- via postback pixel,

- by manually adding conversion data in the tracker panel.

3. Sending a postback from a tracker with a source cid to the source

Postback (s2s postback) is a way to send conversion data from the server (tracker source) to the server (traffic source) using the source postback link.

Postback link - a URL provided by the source and used by the tracker to send information about the conversion to the source statistics. The postback link is generated in the traffic source.

When registering a conversion, the tracker sends a postback with the cid value of the source and other necessary data to the traffic source.

Using this logic of work, you can set up a postback from the tracker both to the traffic source and to messengers / any other platform.

Conditions for Successful Conversion Registration in the Source via Postback

! Without a cid value, the source will not register the conversion.

To successfully register a conversion in the source, you need:

  • send source cid value to the tracker

  • register a conversion in the tracker

  • when registering a conversion, the tracker sends a postback with the source cid value back to the source

  • the source receives a postback with the cid value from the tracker and registers the conversion in its statistics

Setting up a Postback from PeerClick to a Traffic Source

1. Setting the source template in the tracker

In the tracker source template settings, specify the source macro that passes the source cid to the reserved parameter PeerClick external_id in the Placeholder field.

The macro of the source that transmits the cid is taken on the source side.

If necessary, add additional PeerClick parameters in the Parameter field and the corresponding traffic source macros in the Placeholder field.

To enable tracking of an additional parameter, click the slider next to the parameter.

The parameter name can be anything, the source macro is taken on the source side.

If a preset template is selected when creating a traffic source, the main available source parameters are already configured. The template preset by the tracker is a recommended setting, not a requirement.

2. Setting up a postback link

Copy the source postback link and paste it into the Traffic source postback URL field in the traffic source settings in the tracker.

Using this link, the tracker will send information to the source, which the tracker displays in the Conversions - Out postback log.

Then configure the transmission of the source cid with the postback by adding the source parameter to the postback link, which is responsible for receiving the source cid back to the source, and the {externalid} macro.

Your postback URL should look like this:

https://testpostback.com?cid={externalid}, where:

  • https://testpostback.com - source postback address;

  • ? - designation of the end of the postback URL, followed by parameters and their values;

  • cid - source parameter responsible for receiving the source cid;

  • {externalid} - PeerClick macro responsible for passing the source cid (passed parameter value).

If necessary, configure the transfer of additional data that the tracker will send to the source.

Your postback URL should look like this:

https://testpostback.com?cid={externalid}&source-parameter={PeerClick_macro}, where:

  • https://testpostback.com - source postback address;

  • ? - designation of the end of the postback URL, followed by parameters and their values;

  • source-parameter - any of the allowed additional source parameters responsible for receiving tracker data on the source side;

  • {PeerClick_macro} - tracker macro responsible for passing the parameter value. The macro is selected from the field under the postback link;

  • & - ampersand separating different parameters in the address.

Did this answer your question?