Do I need an API key to connect RedTrack?

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 RedTrack?

{clickid}. RedTrack replaces it with its click ID on each click, and RevRake returns the value in the postback as {sub1}.

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 RedTrack has a parameter for them.

Can I send conversions to RedTrack 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 RedTrack 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.

How to use RevRake with RedTrack: link and postback

Q: Which events can RevRake send to RedTrack?

Six: registration, ftd, commission_approved, commission_rejected, commission_paid and chargeback. You tick the ones you want per destination.

What you need from RedTrack

Two things: the token RedTrack 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:

RedTrack parameter	Filled by	Meaning
`clickid`	`{sub1}`	`sub1` of the click: the click ID your tracker put on the link.
`sum`	`{commission}`	Your commission as a decimal (`40.00`). Empty for a registration, `0` for a rejected commission, negative for a chargeback.
`status`	`{status}`	The word for where the conversion stands, in the words RedTrack knows. They are in the table further down.
`type`	`{event}`	The event name: `registration`, `ftd`, `commission_approved`, `commission_rejected`, `commission_paid` or `chargeback`.
`rdtk_event_id`	`{event_id}`	An ID that is different for every event and the same on every retry.

RedTrack generates the postback address in the settings of the offer source: add RevRake there as an offer source, name clickid and sum as its click ID and payout parameters, and copy the address. It is on your tracking domain, with the path /postback.

type names a conversion type. A type has to exist in RedTrack before it is sent: add each event name you tick under Tools → Conversion tracking → Conversion types, written exactly as RevRake sends it. The names are case-sensitive.

rdtk_event_id carries an ID by which RedTrack can leave out a postback it has already received: choose the duplicate mode "Ignore duplicate postbacks by event id" in RedTrack. The preset sends {event_id} there, so each event is kept and a repeat of the same event is not.

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 RedTrack's click ID in sub1

Add sub1= with RedTrack's click ID token to the link, and use the result as the offer URL in RedTrack:

https://track.revrake.com/c/a8Kq2Zx?sub1={clickid}

RedTrack 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?clickid={sub1}&sum={commission}&status={status}&type={event}&rdtk_event_id={event_id}

RevRake ships this template as the RedTrack preset: choose RedTrack in the list and it is filled in for you.

Replace YOUR-TRACKER-DOMAIN with the address of your own RedTrack postback, as RedTrack 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 RedTrack 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 RedTrack preset uses the one that fits how RedTrack 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 RedTrack 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. RedTrack 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 RedTrack, 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 RedTrack's answer, and in RedTrack.

How {status} maps to RedTrack

RevRake names each event and also gives it a status word. A destination made from the RedTrack preset sends the words RedTrack 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`	`other`	A player was attributed to the affiliate.
`ftd`	`pending`	A first deposit earned the affiliate a CPA commission.
`commission_approved`	`approved`	A commission was approved when its hold period ended.
`commission_rejected`	`declined`	A commission on hold was rejected after a review.
`commission_paid`	`approved`	A commission was paid in a payout batch.
`chargeback`	`declined`	A chargeback took back a commission.

RedTrack has four statuses of its own: other, approved, pending and declined. The preset sends those: pending for a first deposit, whose commission is still on hold; approved when the commission is approved and when it is paid; declined for a rejected commission and for a chargeback; other for a registration, which carries no money.

RedTrack's documentation recommends conversion types for telling events apart, and type carries the event name for that. The preset calls the status parameter status: check on your RedTrack postback page that yours has the same name.

Troubleshooting

RedTrack 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 RedTrack answered.
The click ID arrives empty. The click had no sub1. Check that the offer URL in RedTrack ends with sub1= and {clickid}, and that the click went through RedTrack: 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 is 0 for a rejected commission and negative for a chargeback.
A delivery failed. RedTrack must be reachable on a public address and answer with a 2xx status 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.
RedTrack records the conversion without its type. The event name is not in your list of conversion types, or differs in case.
The same commission adds revenue more than once. Each event you tick arrives with its payout. Tick the one you want as revenue, or check how your duplicate mode in RedTrack counts them.

RedTrack is a product of its own vendor (https://redtrack.io/) 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 RedTrack?: 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 RedTrack?: {clickid}. RedTrack 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 RedTrack?: Six: registration, ftd, commission_approved, commission_rejected, commission_paid and chargeback. 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 RedTrack has a parameter for them.
Can I send conversions to RedTrack 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 RedTrack 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 RedTrack comes from RedTrack'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.

Conversion tracking: S2S, script, API | RedTrack Help https://help.redtrack.io/knowledgebase/kb/conversion-tracking/postback-offer-source/ read on October 4, 2026
Conversion tracking: types, statuses, duplicates, roles | RedTrack Help https://help.redtrack.io/knowledgebase/kb/conversion-tracking/tracking-event-types/ read on October 4, 2026
Dynamic Parameters/Tokens/UTMs | RedTrack Help https://help.redtrack.io/knowledgebase/kb/conversion-tracking/supported-dynamic-parameters/ read on October 4, 2026

How to use RevRake with RedTrack.