Skip to main content
A game build cannot read your website’s cookie. So a new install has no link to the website visit that caused it. Install attribution makes that link, and the Attribution page shows it on the Installs tab.

What counts as an install

An install is the first open of the game: a game_open event with is_first_open: true. The Godot and Unity SDKs send it for you. See app events for other engines.

How the match works

  1. A visitor opens your website. The collector makes a match key from the visitor’s network: a keyed hash (HMAC-SHA256) of your project ID and the IP address. It keeps the key with the visitor’s anonymous ID for 72 hours.
  2. A player opens the game for the first time. The collector makes the same key from the game’s request and looks for website visitors with that key.
  3. With one to three visitors, the collector picks one: a visitor on the same operating system first, then the same clock offset from UTC, then the same language, then the most recent. It writes the match and its confidence on the game_open event.
  4. The report credits a page view of that visitor: the first, the last, or the last that is not Direct (the default).
A browser game on your project domain needs no match. It uses the same anonymous ID as the website.

Signals and confidence

The network makes the candidates. Three more signals rank them: the operating system (from the browser on the website, from the platform in the game), the clock’s offset from UTC (context.utc_offset, sent by the web SDK and the Godot and Unity SDKs) and the language. A value that one side does not have is neutral. A game’s HTTP client sends no browser user agent, so the user agent text itself cannot be compared. Use Match confidence on the report (or min_confidence in the API) to count only stronger matches. Weaker matches then go to Unattributed. A network match is used only when there is no certain link. A certain link is a website visitor with the same identity as the install:
  • the player is identified with the same user ID on the website and in the game, or
  • the game opened the website with a handoff link, or
  • the game runs in the browser on your domain.
Match precision on the report compares the two where an install has both: the share of network matches that agree with the certain link, in total and for each confidence level. It is a lower limit, because a second browser of the same player that was never identified counts as wrong. To get this number, identify players on both sides or use handoff links.

The report

Open Attribution, then Installs.
  • Installs: first opens in the date range.
  • Matched: installs linked to a website visitor, by a certain link or by a network match.
  • Match precision: network matches that agree with a certain link.
  • Attributed: matched installs with a page view in the lookback (30 days by default, up to 365).
  • Group by: channel, source, medium, campaign, creator (ref), short link, ad network or referrer.
  • Unattributed: installs with no match, or with no page view in the lookback.
The API is GET /v0/projects/{project_id}/attribution/installs with date_from, date_to, model (last_non_direct, first_touch, last_touch), group_by, lookback_days, min_confidence (low, medium, high), and the optional filters app_platform, app_storefront and country.

Accuracy

A match is likely, not certain.
  • Two people on one home network can be mixed up.
  • A network with more than three website visitors in 72 hours (a school, an office, a mobile carrier, a VPN) gets no match.
  • A player who saw your site on a phone network and installed on home Wi-Fi gets no match.
  • A website on IPv6 and a game client on IPv4 get no match.
  • A website that sends events through its own proxy gets no match, because the collector sees the proxy’s address for every visitor.
Because of this, a network match never joins the two profiles. The website visitor and the game install stay two profiles. For a certain link, identify the player on both sides, or open your website from the game with a handoff link.

Privacy

  • The IP address is not stored and not logged. Only the keyed hash is stored, and the hash is different for each project.
  • The collector deletes each match key 72 hours after the visitor’s last website event.
  • Visitors without a visitor ID (before consent in the SDK consent mode) get no match key. Bots get none.
  • A project that sends no game events gets no match keys.
  • An owner or admin can turn the feature off in Project settings, Install matching. This deletes the project’s match keys at once.
If your privacy policy says how you use IP addresses, add this use to it.