What the SDK sends
Each event inPOST /v0/events has these fields:
A browser that opens a link from your game (the Godot SDK’s
link_url() or the Unity SDK’s LinkUrl()) also sends one identity_handoff event with the game’s anonymous ID (source_anonymous_id) and the link time (handoff_at). The SDK removes the ua_hid parameter from the address bar first.
Page URLs
The SDK sends only the URL origin and path. It removes query strings and fragments. It keeps only the allowlisted campaign fields below, and it drops unsafe values. Each value is at most 255 characters.Campaign and ad parameters
Arbitrary query parameters never enter the event. Do not put private data in campaign names or click IDs. See attribution for how these fields become channels.
What the collector derives
IP geolocation by DB-IP (CC BY 4.0).
Server-side geolocation
The collector sets the country on the server. The SDK does not send a location, and the browser asks for no location permission.- Country only. The collector keeps an ISO 3166-1 alpha-2 code, such as
USorDE. It never derives or stores a region, a city or coordinates. - In memory. The lookup uses local databases on the collector: Cloudflare’s published geofeed first, then DB-IP. No IP address is sent to a lookup service, and the address is discarded after the lookup.
- Behind a reverse proxy. The collector looks up the first public address in
X-Forwarded-For, so the country is the visitor’s, not your proxy’s. Your proxy can also sendX-Visitor-Countryto set the country itself. - Server events. The request comes from your backend, so the collector does not use its IP address. Send the player’s
iporcountryincontext. See server events. - Unknown. When no country can be found, the country is
ZZ.
Cookies and consent
First-party only
No third-party cookies, no cross-site tracking and no fingerprinting.
- The Web SDK sets only first-party cookies on your own domain. They are listed in browser storage below.
- The collector sets no cookies. Its responses have no
Set-Cookieheader. - The SDK does not read or set third-party cookies, and the visitor ID is not shared with other sites or with advertising networks.
- The visitor ID is a random value. It is never derived from the IP address, the user agent or other request data.
- Until the visitor gives consent, the SDK reads and writes no cookies and no
localStorage. Page views and events are still sent, without a visitor ID, session ID or user ID. - After
setConsent(true), the SDK stores the visitor ID and the session ID. - After
setConsent(false), the SDK removes them.
optOut(). See consent.
Whether your site needs a consent banner is a decision for you and your legal advisers. Consent mode gives you the technical control.
What we never store
- IP addresses. The collector uses the IP for the country lookup in memory. It does not store it, log it or send it to the database. For projects with a game, install attribution also keeps a keyed hash of the IP for 72 hours, then deletes it. You can turn that off. The SDKs also send the clock’s offset from UTC (
utc_offset) for this match; it is not stored on events. - Raw user agents. Only the derived device, OS and browser are kept.
- Full URLs. Query strings and fragments are removed.
- Fingerprints. No visitor ID is derived from request data.
Browser storage
The Web SDK stores these first-party values. The key prefix isua_ plus a hash of the Publishable key.
By default, cookies use the apex domain (for example
.example.com), so example.com and app.example.com share one visitor ID. Set crossSubdomainCookies: false (or data-cross-subdomain="false") for host-only cookies.