Do I need an API key to connect Voluum?

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

{clickid}. Voluum 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 Voluum has a parameter for them.

Can I send conversions to Voluum 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 Voluum 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 Voluum: link and postback

Q: Which events can RevRake send to Voluum?

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

What you need from Voluum

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

Voluum 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.
`currency`	`{currency}`	The ISO code of the commission's currency.
`txid`	`{event_id}`	An ID that is different for every event and the same on every retry.
`et`	`{event}`	The event name: `registration`, `ftd`, `commission_approved`, `commission_rejected`, `commission_paid` or `chargeback`.

Voluum's postback address is on your own Voluum domain, with the path /postback. Copy it from Voluum and keep its domain. cid takes the click ID; payout, currency and txid, the transaction ID, are optional. currency overrides the currency set on the offer in Voluum.

Voluum has no status parameter. The kind of conversion travels in et, the event type, which the preset fills with the event name.

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

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

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

Voluum 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}&currency={currency}&txid={event_id}&et={event}

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

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

How {status} maps to Voluum

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

The Voluum preset sends {event} in et and does not send {status}. To tell the events apart in Voluum, set up a custom conversion in Voluum for each event you tick, with the event name exactly as RevRake sends it, for example registration and ftd. The values are case sensitive.

Voluum counts the same click ID and transaction ID once, and discards a postback that repeats them. The preset therefore sends {event_id}, which is different for every event, in txid, so that later events are not discarded. Each event you tick arrives with its payout: if you tick ftd, commission_approved and commission_paid, Voluum adds the commission three times. Tick the one you want as revenue.

Troubleshooting

Voluum 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 Voluum answered.
The click ID arrives empty. The click had no sub1. Check that the offer URL in Voluum ends with sub1= and {clickid}, and that the click went through Voluum: 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. Voluum 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.
All conversions look the same in Voluum. The event names have not been set up as custom conversions in Voluum, or differ in case.
The payout in Voluum is not the one sent. Check the payout setting of the offer in Voluum: a payout fixed on the offer is used instead of the value in the postback.

Voluum is a product of its own vendor (https://voluum.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 Voluum?: 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 Voluum?: {clickid}. Voluum 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 Voluum?: 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 Voluum has a parameter for them.
Can I send conversions to Voluum 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 Voluum 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 Voluum comes from Voluum'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 Using S2S Postback URL - Voluum Documentation https://doc.voluum.com/article/track-conversions-using-s2s-postback-url read on October 4, 2026
Parameters in Postback URLs - Voluum Documentation https://doc.voluum.com/article/parameters-in-postback-urls read on October 4, 2026
Custom conversions - Voluum Documentation https://doc.voluum.com/article/custom-conversions read on October 4, 2026
Upselling: Tracking subsequent conversions - Voluum Documentation https://doc.voluum.com/article/upselling-tracking-subsequent-conversions read on October 4, 2026

How to use RevRake with Voluum.