UTM parameters and the App Store
UTM tags are intended for web analytics. App Store campaign reporting uses its own parameters, so check the final store URL.
19 October 2026 ยท PAD team
What Apple does with UTM tags
Nothing. Append utm_source and utm_campaign to an apps.apple.com URL and Apple ignores them entirely. They do not appear in App Store Connect, they do not reach your app, and they do not affect anything.
Apple reads pt and ct instead, covered in the campaign token write-up. Google Play reads a referrer parameter, which does accept UTM-style content.
The asymmetry
| Store | Reads | Format |
|---|---|---|
| App Store | pt and ct | two flat values |
| Google Play | referrer | an encoded query string, UTM-friendly |
This is why a single link cannot carry identical tagging to both stores without translation at the last step.
Keeping one naming scheme
Decide on campaign names once and map them mechanically. If your web analytics uses utm_campaign=summer_reels, then ct=summer_reels on iOS and referrer=utm_campaign%3Dsummer_reels on Android keeps the reports readable side by side.
The failure mode to avoid is inventing separate names per platform, which makes cross-channel comparison impossible six months later when nobody remembers the mapping.
Where the tags get lost
Parameters have to be on the final store URL. Any redirect in the chain that drops the query string takes your attribution with it, and short link services are a frequent culprit.
The other loss is more expensive: if the tap dies inside an in-app browser, there is no install to attribute at all. Tagging is downstream of arriving.
Create a GoToApp link with your destinations, then test it on the devices and channels you plan to use. Free includes up to three projects.