Do I need an API key to connect BeMob?

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

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

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

Q: Which events can RevRake send to BeMob?

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

What you need from BeMob

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

BeMob 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 BeMob knows. They are in the table further down.

BeMob's click ID token is written with a capital I: {clickId}. In BeMob, add the program as an affiliate network and copy the postback address from its settings. It looks like https://xxxxx.bemobtrk.com/postback?cid=REPLACE&payout=OPTIONAL&txid=REPLACE&status=REPLACE: put its host in the template.

cid takes the click ID and is the only obligatory parameter. payout, txid, the transaction ID, and status 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 BeMob's click ID in sub1

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

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

BeMob 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}

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

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

How {status} maps to BeMob

RevRake names each event and also gives it a status word. A destination made from the BeMob preset sends the words BeMob 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`	`new`	A player was attributed to the affiliate.
`ftd`	`approved`	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`	`chargeback`	A chargeback took back a commission.

BeMob has no status words of its own: you enter them. Tick "Use conversion statuses" in the affiliate network settings in BeMob and type the four words the preset sends into the fields of the same names: new, approved, declined and chargeback. A conversion with the status New adds no revenue in BeMob.

BeMob does not change the status of a conversion it already has: a postback with another status is recorded as one more conversion. The first deposit, the approval and the payment of one commission arrive with the same txid, which is {conversion_id}, and the same status approved. BeMob does not accept a second postback for a click that neither a new transaction ID nor another status sets apart, so the commission is counted once.

For a status BeMob does not recognise, the default postback status you chose in BeMob applies; ignoring the conversion is one of the choices.

Troubleshooting

BeMob 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 BeMob answered.
The click ID arrives empty. The click had no sub1. Check that the offer URL in BeMob ends with sub1= and {clickId}, and that the click went through BeMob: 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. BeMob 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.
A commission is counted more than once in BeMob. "Accept Double Postbacks" is ticked in BeMob, which makes it accept the approval and the payment as conversions of their own. Untick it, or tick only ftd among the money events.
The click ID token was not replaced. BeMob's token is {clickId}, with a capital I.

BeMob is a product of its own vendor (https://bemob.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 BeMob?: 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 BeMob?: {clickId}. BeMob 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 BeMob?: 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 BeMob has a parameter for them.
Can I send conversions to BeMob 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 BeMob 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 BeMob comes from BeMob'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.

Postback Settings of Affiliate Network | BeMob Help Center https://docs.bemob.com/en/postback-settings-of-affiliate-network read on October 4, 2026
Postback Statuses | BeMob Help Center https://docs.bemob.com/en/postback-statuses read on October 4, 2026
Double Postbacks and Postbacks From White IPs | BeMob Help Center https://docs.bemob.com/en/double-postbacks-and-postbacks-from-white-ips read on October 4, 2026
Click ID in Offer Settings | BeMob Help Center https://docs.bemob.com/en/click-id-in-offer-settings read on October 4, 2026

How to use RevRake with BeMob.