Answer in brief
The Google Play Install Referrer is an API that lets an Android app retrieve referral content from Google Play about its own install: the referrer URL, the time of the referrer click and the time the installation began. An MMP reads it on first open and uses it as a deterministic match between an ad click and the install.
What the Install Referrer returns
Google describes the Install Referrer API as a way to securely retrieve referral content from Google Play.[1] The app asks Google Play, and Google Play answers with a small set of fields.
| Field | Why attribution cares |
|---|---|
| Referrer URL of the installed package | Carries the campaign details that were attached to the store link. |
| Timestamp of the referrer click, in seconds | Says when the person tapped through to the store. |
| Timestamp of when the installation began, in seconds | Says when the download started. |
| App version at first install | Shows which build the person first received. |
| Instant experience use in the past 7 days | Shows whether the person tried the app's instant experience first. |
The two timestamps are given both client-side and server-side.[1] The last two fields come from the same documentation.[1] Devices with a Google Play app version of 8.3.73 or later have access to the API automatically.[1]
How an MMP turns it into a match
- A person taps an ad. The tracking link records the click and sends them to the Play Store with a referrer value attached to the store address.
- Google Play keeps that value while the app downloads.
- On first open, the MMP's SDK asks for the install referrer and receives the URL and the timestamps.
- The MMP finds the click that carries the same value and credits it, if the click is inside the lookback window.
Because the value at the click and the value at first open are the same string, this is a deterministic match. The comparison with other methods is in deterministic versus probabilistic matching.
What the timestamps are good for
The click time and the install-begin time let an MMP check that events happened in a believable order. A click that is recorded after the download had already started cannot have caused the install. A claimed click with a very long gap before the install deserves less trust than a recent one. These checks are one input to fraud rules, which the fraud prevention basics guide explains.
Where the referrer does not help
- Ad views. The referrer describes a click that led to the store. An ad that was only seen leaves no referrer, so view-through attribution relies on other data.
- Installs from outside Google Play. The content comes from Google Play, so other Android stores are not covered.
- People who already have the app. The API describes an install. An ad that brings an existing user back is a re-engagement and is matched another way.
- iOS. The API belongs to Google Play, and iOS installs are matched in other ways. See how iOS and Android attribution differ.
What to check in your own app
Ask your developer three things. First, is the MMP's Android SDK reading the install referrer? Second, does a test install from a tracking link show up in the MMP's test console with the right campaign? Third, do your store links pass through a redirect or a shortener that might strip the referrer value? If a test install arrives as organic, check the third question first.
Questions and answers
Does the Install Referrer work for apps installed outside Google Play?
No. The API returns content from Google Play, so it only describes installs that came through the Play Store. Installs from other Android stores need a different matching method.
Do I have to call the Install Referrer API myself?
Usually not. An MMP's Android SDK reads the referrer on first open. Your developer adds the SDK and checks that a test install shows the expected referrer.
Continue reading
Guide
Last-touch attribution and why it is the common defaultLast-touch attribution gives all credit for an install to the final qualifying click or view. How the winner is picked, why it is the common default, and its limits.
Guide
Deterministic versus probabilistic matchingDeterministic matching ties an install to a click with an exact identifier. Probabilistic matching infers the link from device signals. When each is used.
Guide
View-through attributionView-through attribution credits an install to an ad that was shown but not clicked. How the view window works, the risk of over-crediting, and how to set it.
Guide
Re-engagement attributionRe-engagement attribution credits an ad for bringing an existing user back to the app. How it differs from install attribution and which settings define it.
Guide
Self-attributing networksA self-attributing network decides for itself whether its ad led to an install and tells the MMP the answer. What that means for your reports and settings.
How it works
Best MMP attribution starts with knowing how the match is madeHow an MMP attributes an install on Android and iOS, what lookback windows do, and which settings to check before you trust a report.
Sources
- Google: https://developer.android.com/google/play/installreferrer Checked 2026-11-10.
Cite this page
Airbridge. “The Google Play Install Referrer.” bestmmpattribution.com. Reviewed 2026-11-10. https://bestmmpattribution.com/google-play-install-referrer