// Blog · Marketing
Casino affiliate tracking software: what to check before you sign
Affiliates bring a third to a half of first deposits for most casino brands. The tracking system is the contract you have with them. Here is what it has to do, and the questions that find out whether it does.
Affiliate marketing in gambling runs on trust that is verified by software. The affiliate sends traffic, your system records who came from where, and at the end of the month you pay out on what it recorded. If the recording is wrong, you either overpay or you lose partners. If it is opaque, you lose both.
That makes the tracking system one of the few pieces of software where the details genuinely are the product. These are the ones to check.
Attribution that survives the real world
A click lands with a tracking link, a cookie is set, and some time later a player registers and deposits. In between, cookies get blocked, players switch from phone to laptop, and a second affiliate's link gets clicked. The system has to answer "whose player is this" consistently, and the rules have to be written down.
- Cookie plus fingerprint. A cookie alone loses a meaningful share of attributions on iOS and privacy browsers. Device fingerprinting as a second signal recovers most of it.
- Attribution window. Thirty days is the common default. It must be configurable per partner, because your contracts will not all say the same thing.
- First click or last click. Pick one, document it, and make sure the partner portal shows the same rule. Disputes come from partners discovering the rule after the fact.
- App and web. If you have a native app, attribution has to bridge the install, or every app player is "organic".
Postbacks: the events, the retries, the idempotency
Serious affiliates do not read your dashboard, they consume your postbacks: server-to-server calls that tell their own system "registration happened", "first deposit happened, amount X". The system needs to send them for the events partners care about (click, registration, KYC approved, first deposit, subsequent deposits, revenue), retry on failure, and never send the same event twice. A postback that fires twice is a partner invoicing you twice. One that silently fails is a partner who thinks you are stealing.
Sub-IDs: the only way to know what is worth paying for
A partner is not one traffic source. The same affiliate runs a YouTube review, a top-ten list, a push notification feed and an email list, and they perform completely differently. Sub-ID tracking lets the partner tag each source in the link, and lets you both see conversion and value by source.
In the console we rendered for this article, one partner's YouTube reviews convert at 3.2% with €212 of NGR per first deposit, while their push traffic converts at 0.5% and produces €38. On a flat CPA deal, the push traffic loses money on every player. Sub-ID reporting is how you find that out before the quarter ends, and it is what lets you pay the partner more for the traffic that deserves it.
Commission models, and the definitions that cause disputes
| Model | How it pays | Where it goes wrong |
|---|---|---|
| CPA | Fixed amount per qualifying first deposit | "Qualifying" must be defined: minimum deposit, KYC passed, not a duplicate, not refunded. Fraud risk is highest here. |
| RevShare | Percentage of NGR from referred players, forever or for a term | NGR has to be defined identically in the contract and the software: which bonus costs, which fees, which taxes, whether negative months carry over. |
| Hybrid | Smaller CPA plus smaller RevShare | Both sets of problems, and the system has to handle tiers that change with volume. |
The single most common dispute is NGR. If your BI defines NGR one way and the affiliate statement another, every statement is an argument. The affiliate system and the finance reporting have to read from the same definition, ideally the same data.
Fraud: what the system must catch on its own
Affiliate fraud is not rare and it is not subtle once you look. Click spam from a handful of IPs to inflate conversion denominators. Multi-accounting, where the "players" are the affiliate's own devices depositing the CPA minimum and withdrawing. Bonus abuse rings routed through a partner link. Cookie stuffing that claims organic players.
The system needs velocity rules on clicks, device and IP matching across registrations, flags on minimum-deposit-then-withdraw patterns, and a hold period on CPA before it becomes payable. It also needs to make the evidence visible, because the conversation with the partner is easier when you can show them the data.
Payouts and the partner experience
Partners stay where the money arrives on time with a statement that matches their own numbers. That means automatic monthly invoices, statements by sub-ID, a choice of payment methods including bank, e-wallet and crypto, and a portal that shows them live stats, not a PDF on the fifth of the month. A good partner portal is a recruiting tool. A bad one is churn.
Ownership
Three questions: is the tracking data yours, exportable, in a documented format? Is the tracking link domain yours, so that if you change systems the links keep working? And is there an exit from the system without losing history? Affiliate relationships are long-lived; a platform migration that resets every partner's stats is a migration that loses partners.
The checklist
- Cookie plus fingerprint attribution, configurable window, documented first or last click rule
- S2S postbacks for every event, with retries and idempotency
- Sub-ID reporting with NGR per source, not just FTD counts
- CPA, RevShare and hybrid with tiers, negative carryover and an NGR definition that matches finance
- Built-in fraud rules and visible evidence
- Automatic invoicing, statements, multiple payout methods, a live partner portal
- Your data, your link domain, documented export
How we handle it
A full affiliate and tracking system is part of the BetCode platform, not a third-party bolt-on: tracking links on your domain, postbacks, sub-ID reporting on NGR from the same data as the BI, CPA, RevShare and hybrid deals with tiers, fraud detection, and automated partner payouts. If you are running affiliates on a separate system today and want to see what consolidation would look like, get in touch.
Questions we get asked
Should I pay affiliates on FTD count or on NGR?
Pay on NGR, or on a CPA whose qualifying rules are strict, with a hold period. Paying on raw FTD count rewards traffic that deposits the minimum and leaves, and sub-ID reporting usually shows that a share of any partner's sources lose money on that basis.
What is a postback in affiliate tracking?
A server-to-server call from your system to the affiliate's system when an event happens, such as a registration or a first deposit. It lets the partner track performance in their own tools. It has to be reliable, retried on failure and never duplicated.
Can affiliate tracking be part of the casino platform?
It can and it should. Running it on the same data as the player accounts and the BI means attribution is accurate, NGR is defined once, fraud checks see the whole picture, and a platform migration does not reset partner history.
How do I detect affiliate fraud?
Velocity rules on clicks, device and IP matching across registrations, flags on deposit-minimum-then-withdraw patterns, and a hold on CPA until the player has shown real activity. The system should show you the evidence so the conversation with the partner is about data, not accusations.