App store campaign tracking with UTM
App-store listings do not consume standard utm_ parameters the way a web page does — Apple and Google each have their own campaign-tracking mechanisms (App Store campaign links / Apple Ads attribution and Google Play referrer / the Install Referrer). When you drive traffic from web links to a store, you tag the web hop with UTMs, then hand off to the store's native parameter. This page covers that handoff so install attribution is not lost.
UTMs stop at the store front door
When a user taps a UTM-tagged link to your App Store or Play listing, the store strips your utm_ values; they do not survive into the install. So UTMs measure the click-to-store step in web analytics, not the install.
For the install, use each platform's native mechanism: Google Play's Play Install Referrer API (with a referrer string you set on the store URL) and Apple's campaign/attribution tooling for the App Store.
- Web hop: standard utm_ parameters
- Google Play install: referrer parameter + Install Referrer API
- Apple App Store install: Apple's campaign/attribution mechanism
Designing the handoff
Build the web link with UTMs for analytics, and separately construct the store URL with the store's own campaign parameter (for Play, a referrer value; for Apple, its campaign mechanism). Keep the naming aligned across both so a web campaign and its installs are recognisably the same effort.
Document that utm_ is web-only and the store parameter is install-only, so teammates do not expect utm_ to appear in the store console.
How it appears in analytics and logs
A UTM on a web link tells web analytics which campaign sent someone toward your app. The install itself is attributed by the store's parameter — Google Play's install referrer or Apple's campaign/attribution — not by utm_ values, which the stores do not forward into the app.
Diagnostic use case
Attribute traffic that flows from web campaigns into an App Store or Google Play listing, by tagging the web link with UTMs and using each store's own campaign/referrer mechanism for the install step.
What WebmasterID can help detect
WebmasterID measures the web hop — the UTM-tagged click toward the store — server-side as a campaign source. Install attribution beyond that handoff is owned by the store's own console, which WebmasterID does not impersonate.
Common mistakes
- Expecting standard utm_ values to appear in App Store or Play install reports — they do not.
- Using Google Play's referrer field for Apple, or vice versa — the mechanisms differ.
- Mismatching campaign names between the web UTM and the store parameter.
- Treating a store listing visit as an install — they are separate steps.
Privacy and accuracy notes
Store campaign parameters describe the campaign, not the installer. Apple and Google constrain install attribution for privacy; you receive campaign-level signals, never an individual device or person from a UTM.
Related pages
- UTM for app deep links
When a campaign link opens a native app instead of a web page, the UTM values have to survive a web-to-app handoff that does not always preserve query strings. This page covers passing campaign data into deep links and the caveats that can drop it along the way.
- UTM vs click IDs (gclid, fbclid, msclkid)
UTM parameters are manual labels you write; click IDs like gclid, fbclid, and msclkid are opaque identifiers a platform auto-appends. This page explains how they differ, which tools read which, and why setting conflicting manual and auto-tagged values on one URL causes double-counting.
- Link-in-bio campaign tracking
A link-in-bio page is the single URL in a social profile that fans out to several destinations. Without tagging, every outbound click looks the same and you cannot tell which social platform or which button drove it. Adding UTM parameters to the destination links inside your bio hub, plus the bio link itself, makes each path measurable. This page covers a two-layer tagging approach for bio links.
- Campaign links docs
Tag the web hop while the store owns install attribution.
Sources and verification notes
- Google Play — Play Install Referrer APIInstall attribution mechanism that replaces utm_ at the store.
- Apple — Apple Ads attribution / App AnalyticsApple's own campaign/attribution mechanism for App Store installs.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.