What you need from PeerClick
Two things: the token PeerClick replaces with its click ID, which is {clickid}, and your postback address with the names of its parameters. RevRake fills each parameter with a macro:
| PeerClick parameter | Filled by | Meaning |
|---|---|---|
cid | {sub1} | sub1 of the click: the click ID your tracker put on the link. |
payout | {commission} | Your commission as a decimal (40.00). Empty for a registration, 0 for a rejected commission, negative for a chargeback. |
txid | {conversion_id} | An ID that is the same for every event about one commission: its first deposit, approval, rejection, payment and chargeback. A registration has its own. |
status | {status} | The word for where the conversion stands, in the words PeerClick knows. They are in the table further down. |
currency | {currency} | The ISO code of the commission's currency. |
PeerClick shows the postback address in the "Postback URL" field of the offer settings and of the offer source settings. Addresses differ per account: copy yours, put its host in the template, and keep any parameter your address already carries.
cid takes the click ID and is required. payout, status, txid, the transaction ID, and currency are optional.
Step by step in RevRake
1Create a tracking link
Open the Links page of your affiliate portal and create one link per campaign. Each link has its own short address on track.revrake.com and can land on a page of the program's site that you choose.
2Put PeerClick's click ID in sub1
Add sub1= with PeerClick's click ID token to the link, and use the result as the offer URL in PeerClick:
https://track.revrake.com/c/a8Kq2Zx?sub1={clickid} PeerClick replaces {clickid} with its click ID on every click. RevRake stores the value with the click, up to 200 characters, and gives it back in your postbacks as {sub1}. sub2 to sub5 are free for your own values, and UTM tags on the link are stored too.
3Add a postback destination
Open the Postbacks page and press "Add a destination". The address is a template: anything in braces is a macro that RevRake fills in for each conversion.
https://YOUR-TRACKER-DOMAIN/postback?cid={sub1}&payout={commission}&txid={conversion_id}&status={status}¤cy={currency} RevRake ships this template as the PeerClick preset: choose PeerClick in the list and it is filled in for you.
Replace YOUR-TRACKER-DOMAIN with the address of your own PeerClick postback, as PeerClick shows it to you. The portal refuses a template that still has the placeholder host. If your postback address has a parameter with another name than in the template, change the name and keep the macro.
4Choose the events
Tick the events this destination should hear about. registration and ftd tell PeerClick about a new player and their first deposit within seconds of the operator reporting them. commission_approved, commission_rejected, commission_paid and chargeback follow the money afterwards.
RevRake has two IDs for a postback. {conversion_id} is the same for every event about one commission, so a tracker that updates a conversion by its ID keeps one conversion per commission. {event_id} is different for every event. The PeerClick preset uses the one that fits how PeerClick treats a repeated ID; the sections below say which. An account can have up to 10 destinations.
5Send a test and read the delivery log
Press "Send test" on the destination. RevRake sends a made-up conversion at once and shows what PeerClick answered and how fast. The test looks like a first deposit: it carries the click ID TEST-CLICK-ID and a commission of 40.00. PeerClick does not know that click, so it may ignore the test or answer with an error: what the test proves is that the address is reachable and how the filled-in address looks.
For a check from end to end, open your campaign link through PeerClick, so that a real click ID travels in sub1, and ask the operator to register a test player from that visit. The conversion then appears in the delivery log, with each attempt and PeerClick's answer, and in PeerClick.
How {status} maps to PeerClick
RevRake names each event and also gives it a status word. A destination made from the PeerClick preset sends the words PeerClick knows in {status}; {event} always carries the event name. A destination made with "Other / custom" sends lead, sale, approved, rejected and paid.
| Event | {status} | When |
|---|---|---|
registration | lead | A player was attributed to the affiliate. |
ftd | sale | A first deposit earned the affiliate a CPA commission. |
commission_approved | approved | A commission was approved when its hold period ended. |
commission_rejected | rejected | A commission on hold was rejected after a review. |
commission_paid | paid | A commission was paid in a payout batch. |
chargeback | rejected | A chargeback took back a commission. |
PeerClick has no fixed status words. Under Settings → Custom conversion you choose a preset of columns, of which one is made for iGaming, and enter the status values the other side sends. Enter the words of the table above for the events you tick.
PeerClick keeps one conversion per click ID unless postbacks carry different transaction IDs: a different txid makes a separate conversion, and without one a later postback replaces the earlier. The preset sends {conversion_id} in txid, so the first deposit of a commission, its approval and its payment share one transaction ID, and the registration has another. Check in PeerClick that a repeated transaction ID updates the conversion as you expect.
Troubleshooting
- PeerClick shows no conversions. Open the delivery log on the Postbacks page. If there is no row, the event has not happened yet, or the destination is not ticked for it. If there is a row, it shows the address that was called and what PeerClick answered.
- The click ID arrives empty. The click had no
sub1. Check that the offer URL in PeerClick ends withsub1=and{clickid}, and that the click went through PeerClick: a link opened directly has no click ID to carry. - A macro arrives as written, in braces. RevRake sends a name it does not know unchanged, so a typo is visible in the delivery log. Compare the name with the list of macros.
- The payout is empty or zero. A registration carries no money, so
{commission}is empty for it. It is0for a rejected commission and negative for a chargeback. - A delivery failed. PeerClick must be reachable on a public address and answer with a
2xxstatus within 5 seconds. A failed delivery is retried after 1 minute, 5 minutes, 25 minutes, 2 hours, 10 hours and 24 hours, and then marked as given up; you can send it again by hand. - The destination was switched off. After 20 failures in a row RevRake switches a destination off, with an email after 5 and after 15. Fix the address and switch it back on: every postback that queued meanwhile is sent.
- A status column stays empty in PeerClick. The word RevRake sends is not entered in PeerClick's custom conversion settings.
- PeerClick answers with an error. Compare the address in the delivery log with the one PeerClick shows you: the host and any account parameter must be yours.
PeerClick is a product of its own vendor (https://peerclick.com/) and is named here only to say which tracker the guide is for. RevRake is not affiliated with it.
Questions
- Do I need an API key to connect PeerClick?
- No. Tracking links and postbacks are set up in your affiliate portal and need no key. A key is only needed if you want to read your reports and commissions by API.
- Which token do I put in sub1 for PeerClick?
{clickid}. PeerClick replaces it with its click ID on each click, and RevRake returns the value in the postback as{sub1}.- Which events can RevRake send to PeerClick?
- Six:
registration,ftd,commission_approved,commission_rejected,commission_paidandchargeback. You tick the ones you want per destination. - Does the postback carry the deposit amount?
- The templates send your commission in
{commission}. The deposit behind it is available as{amount}, with its currency in{amount_currency}: add them to the template if PeerClick has a parameter for them. - Can I send conversions to PeerClick and to another tracker at once?
- Yes. An account can have up to 10 destinations, each with its own template and its own events.
- What happens if PeerClick is down when a conversion happens?
- The postback is retried six times over about a day and a half. Every attempt is kept in the delivery log, and a delivery that was given up can be sent again by hand.
Sources
What this guide says about PeerClick comes from PeerClick's own documentation, as it read on the day given. Trackers change: if a name on your postback page differs from this guide, trust your postback page. What it says about RevRake is in the integration guide and the API reference.
- Track Conversions via S2S Postback URL | Peerclick Help Center https://help-center.peerclick.com/en/articles/6643019-track-conversions-via-s2s-postback-url read on October 4, 2026
- Conversion Statuses Settings | Peerclick Help Center https://help-center.peerclick.com/en/articles/10225260-conversion-statuses-settings read on October 4, 2026
- Custom Conversion Settings | Peerclick Help Center https://help-center.peerclick.com/en/articles/4314836-custom-conversion-settings read on October 4, 2026
- Available Macros for Offer / Lander URL | Peerclick Help Center https://help-center.peerclick.com/en/articles/4269573-available-macros-for-offer-lander-url read on October 4, 2026