Skip to content
MyCasinoSetup

TRACKINGGUIDES

Casino traffic tracking: clicks, postbacks and conversions

KEY POINTS

  • Tie every click to the registration and deposit it led to: store the click ID, pass it to the casino, get it back in a postback.
  • Send conversions server to server. Browser cookies get blocked or expire: Safari caps cookies set by scripts to 7 days, and to 1 day after a tracker link.
  • Give each traffic source its own link and its own postback key, log every incoming postback as received and count each event once.
  • Test with a source that is not forwarded, never with production keys: a test conversion sent to an ad network ends up in your campaign statistics.

Updated 3 November 2026 · 4 min read

Paid traffic to a casino comes from ad networks, Meta and influencers. To know what each source brings, you need to connect every click to the registration and deposit it led to, and report those conversions back to the source, so that its algorithm optimises for players, not for clicks. Here is how we set this up for operators’ campaigns.

1. The chain from click to deposit

  1. Click. The ad network or Meta sends the visitor to your link with its click ID in the address.
  2. Landing page. Your tracker saves the click ID together with the source and campaign, then sends the visitor to the casino with your own tracking parameter.
  3. Registration and deposit. The casino platform records the tracking parameter with the new player.
  4. Postback. On registration and on deposit the platform sends a server-to-server request to your tracker with the tracking parameter.
  5. Forwarding. Your tracker finds the original click and sends the conversion to the source that brought it.

If one link in the chain loses the ID, the conversion still happens, but nobody can tell which campaign earned it.

2. Why server to server

A pixel in the browser loses events: ad blockers cut it, visitors refuse cookies, and browsers limit how long cookies live. Since 2019 Safari has capped persistent cookies created by scripts to 7 days, and to 1 day when the visitor arrives from a domain classified as a tracker with a query string or fragment in the link.

A postback does not depend on the player’s browser. The casino platform reports the conversion directly to your server, and your server reports it to the source.

Give each source its own tracking link and its own partner code in the casino platform: one for each ad network, one for Meta, one per influencer (for example, a short path like /i/name). Then the platform’s reports already split players by source, before any tracker is involved.

4. A safe postback endpoint

The endpoint that receives postbacks moves money-relevant data, so treat it that way:

  • A separate secret key per source. A leaked key can be replaced for one source without breaking the others.
  • Reject unknown keys and malformed requests instead of guessing.
  • Store every incoming postback as received. When a source disputes a number, you show the raw request, not a reconstruction.
  • Count each event once. Platforms retry; the same deposit arriving twice must not become two conversions.

5. Forward conversions to the source

  • Ad networks usually take a postback URL with their click ID and the event type. Send registrations and deposits as the events your campaign optimises for.
  • Meta takes server events through the Conversions API. Meta recommends running it alongside the Pixel and deduplicates the two when both report the same event with the same event ID and event name within 48 hours. See our guide on Meta Pixel and Conversions API.

6. Test without spoiling the statistics

A test conversion sent to an ad network with a production key lands in your real campaign statistics. So:

  • test with a source or a click your tracker does not forward;
  • keep production keys out of test scripts;
  • check the whole path once, as a player would go through it: click, landing page, registration, deposit, postback, forwarded conversion;
  • after each release, check from outside which version is running.

7. Read the numbers

For each source, compare clicks, registrations and first deposits in your tracker with the source’s own dashboard. A gap is normal; a sudden change usually means a lost ID or a broken link in the chain, and the stored postbacks show where.

Checklist

  • Click ID saved on the landing page, passed to the casino, returned in postbacks.
  • Postbacks for registration and deposit, server to server.
  • A link, a partner code and a postback key per source.
  • Every incoming postback stored as received; each event counted once.
  • Conversions forwarded to ad networks and to Meta, deduplicated with the Pixel.
  • Tests that never reach the source with production keys.

We set up landing pages with click tracking and postbacks for operators’ campaigns, also for casinos that do not run on our platform. See landing pages for paid traffic.

Frequently asked questions

What is a postback in casino marketing?

A server-to-server request that reports a conversion, such as a registration or a first deposit, together with the click ID it belongs to. The casino platform sends it to your tracker, and the tracker forwards it to the traffic source.

Why not just use a tracking pixel?

A pixel runs in the player's browser, where ad blockers, refused consent and cookie limits cut events. A postback travels between servers, so the conversion arrives even when the browser did not report it.

Should every traffic source have its own postback key?

Yes. Then a leaked key can be replaced for one source without touching the others, and every incoming postback shows which source it belongs to.

How do I test tracking without spoiling campaign statistics?

Use a test source or a click that your tracker does not forward, and keep production keys out of tests. Check the whole path: click, registration, deposit, postback, forwarded conversion.

SOURCES

  1. WebKit — Intelligent Tracking Prevention 2.1 · 21 Feb 2019
  2. WebKit — Intelligent Tracking Prevention 2.2 · 24 Apr 2019
  3. Meta for Developers — Conversions API · accessed 3 Nov 2026
  4. Meta for Developers — Handling duplicate Pixel and Conversions API events · accessed 3 Nov 2026

NEXT STEP

See it running.

Tell us which model fits. We will walk you through the back-office and answer the commercial questions.