Install Referrer is Google Play's official mechanism for passing referral and attribution data from the play-store click to the freshly installed Android app. When a user clicks a link that routes through Play Store (with the correct referrer parameters appended), Play Store captures the parameters; when the user installs the app, Google's Install Referrer API delivers those parameters to the app on first launch. MMPs and ad networks use this signal as the deterministic attribution backbone on Android.
How Install Referrer works: 1. Ad click fires a URL with referrer parameters appended (e.g., `https://play.google.com/store/apps/details?id=com.app&referrer=utm_source%3Dmeta%26campaign%3Dsummer`). 2. User taps the URL, Play Store opens with the parameters captured. 3. User installs the app. 4. On first launch, the freshly installed app calls Google's Install Referrer API. 5. The API returns the captured referrer parameters. 6. The MMP SDK reads these parameters and attributes the install to the source campaign. This flow is deterministic — no probabilistic matching, no fingerprinting required. The referrer data is passed cryptographically by Play Store and is highly reliable.
Why Install Referrer is the cleanest Android attribution
- Deterministic — no probabilistic matching, no fingerprinting. Reliable.
- Not subject to ATT-style restrictions — Apple's ATT doesn't apply to Android. Privacy Sandbox for Android (full rollout ~2027) may eventually layer aggregated attribution alongside Install Referrer, but as of 2026 Install Referrer remains broadly available.
- Privacy-preserving by design — only data the user / ad network explicitly attached to the click URL flows through; no behavioral profiling.
- Supported by all major MMPs and SANs — AppsFlyer, Adjust, Singular, Branch all integrate; Meta, TikTok, Google Ads, AppLovin, ironSource all use it.
What gets passed in referrer parameters
- UTM-style parameters — utm_source, utm_campaign, utm_medium, utm_content.
- MMP-specific identifiers — AppsFlyer click IDs, Adjust click tokens, Singular click identifiers.
- Campaign / creative IDs — for granular attribution.
- Geo / language signals — sometimes.
The payload format is configurable per ad network; MMPs typically standardize their own parameter set.
Limitations
- Only works through Play Store URL — if the user clicks a deep link that bypasses Play Store, Install Referrer doesn't fire.
- Single referrer — captures one set of parameters per install. Doesn't support multi-touch attribution natively.
- Privacy Sandbox eventual impact — full Privacy Sandbox for Android (~2027) will introduce aggregated attribution alongside Install Referrer; some industry observers expect Install Referrer to be limited / restructured at that time.
- Not iOS — no equivalent on iOS. Apple's first-party-attribution mechanisms (Apple Search Ads Attribution API) are separate; for general iOS attribution, the post-ATT stack relies on SKAN.