PeerClick Documentation


Welcome to the PEERCLICK Help Center. You'll find comprehensive guides and documentation to help you start working with the PeerClick Tracker as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

cid, payout, and txid in Postback URLs

Server-to-server (S2S) postback URLs are the most secure and reliable method to count conversions, thus it is highly recommended to use this form of automated tracking whenever you can. With PeerClick you can use either a secure (HTTPS) or nonsecure (HTTP) format for the postback URLs.

When using the postback URL, PeerClick requires specific parameters for conversion tracking to work correctly.

The cid is dedicated to passing PeerClick’s click ID. The parameter is required to track the registered event. During each campaign visit, a unique click ID is added to the offer URL, to a network (server-side). If, later, the click ID is relayed back to PeerClick via a server request, a conversion is recorded successfully in the origin PeerClick campaign. Also, when a conversion is reported in a PeerClick campaign, all primary visit attributes for the associated user are correlated within the reporting.

For a postback request to be resolved correctly, a valid PeerClick click ID must first be sent and captured by the offer’s source – affiliate network or other – for it to then be relayed back to record the conversion in PeerClick.

The offer’s source has its own dedicated parameters for receiving the PeerClick click ID (s2 in the above example), along with any additional data for each click sent to an offer. Each parameter also has its own corresponding token (network side) that enables referencing the data recorded for each click.

The conversion ID (cid) is matched to the visit ID with certain attributes such as device type, operating system, geo etc. The most important part to register conversions correctly is to match the click ID in the offer URL with the token used in the related postback URL. To do so, check the affiliate network documentation to make sure that you use the correct token.

The payout parameter is used to pass the revenue amount per conversion. There are two available options for tracking conversion payout in PeerClick: Auto or Manual. Auto payout tracking is available when a dynamic payout token or fixed value is used in your postback URL. Payout tokens/values are appended to the payout= parameter found in the PeerClick postback URL’s query string.

To find out more about the payout options in PeerClick, go to the Tracking Payout (Revenue) article.

The txid parameter is used to pass a unique transaction ID for each conversion. You can use a unique transaction IDvalue in a postback URL when you want to record secondary conversion steps, upsells, per visitor following the primary conversion. You can either manually define a transaction ID or pass it dynamically via a token supported by the offer’s source (affiliate network or other). Transaction ID tokens/values are appended to the txid= parameter found in a PeerClick postback URL/pixel query string.

To learn how to set up upsells in PeerClick, go to the Upselling: Registering Multiple Conversions per clickid article.

In the postback URL, you might also use the status parameter that is used to track different conversion types. However, the parameter requires an additional setup that you can configure in the Settings > Custom conversions tab.

In the postback URL, you might also use the conversion_id parameter that is used to sending additional parameters

Updated 4 months ago

cid, payout, and txid in Postback URLs

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.