The chain, end to end
Everything you get paid for depends on one unbroken chain. Break any link and the player still plays, the casino still earns, and you are not paid.
your link → click recorded, click ID issued → casino landing page → registration → deposit → conversion reported back with that click ID → commissionThe click ID is the thread running through it. It is issued when someone clicks your link, carried into the casino's systems, and handed back when that person deposits. It lets the operator say *this deposit belongs to this affiliate* without either side sharing personal data about the player.
Your tracking link
Each affiliate gets their own link per casino. It is not interchangeable with anyone else's, and not interchangeable across casinos. The identifier inside it is what the operator maps back to you.
- Use the link as given. Stripping or rewriting parameters is the most common self-inflicted attribution failure.
- Add your own sub-ID only where the deal supports it, and confirm it survives the round trip before you rely on it for reporting.
- Do not redirect through anything that drops query parameters. Some link shorteners and some in-app browsers do exactly that.
Attribution: who gets credit
When a player touches more than one affiliate's link before depositing, an attribution rule decides who is paid. Last click, meaning the most recent affiliate before registration, is the near-universal default in iGaming.
The other half of the rule is the attribution window: how long a click stays valid. A click followed by a deposit six months later may or may not still be yours. On a lifetime revenue share, attribution is usually tied to the player account at registration rather than to the click, which is why it keeps paying.
Where conversions actually go missing
| Symptom | Usual cause |
|---|---|
| Clicks recorded, no registrations | The link lands somewhere that drops the click ID, or the casino page is broken in that market |
| Registrations but almost no deposits | The operator's onboarding, a payment method missing in that country, or traffic that was never going to deposit |
| Deposits you can see, commissions you cannot | The conversion came back without a click ID, so it could not be attributed to anyone |
| It worked, then stopped | A link was edited, a campaign was rebuilt, or the operator changed their parameter name |
Server-to-server reporting
The last step, where the operator tells the network a deposit happened, runs server to server rather than in the browser. That is what makes it reliable in a world of ad blockers and short cookie lifetimes. How S2S postbacks work covers the mechanics.
