Back to the tool

How to Track App Store Links With UTM Parameters Without Losing the Click

How to track app store links with UTM parameters is a trickier question than the web version, because the app stores do not treat your tagged link the way your website does.

On the web, UTM tracking is simple. You tag a link, someone clicks it, your analytics reads the values, and the campaign gets credit. App stores break that simplicity in a quiet way. The store sits between your link and your app, it has its own rules about which parameters it keeps, and on iOS it keeps almost none of them in a form you can read inside the app. I have seen teams run a launch, watch their store page traffic climb, and have no idea which email, video, or ad drove it, because every link pointed straight at the store and the attribution died at the door.

Google Play is the better behaved of the two stores, and it still requires a specific format. You do not append utm_source and friends directly to the Play Store URL the way you would on your own site. You append a single referrer parameter, and you URL encode the UTM values inside it. A link for a newsletter campaign might look like this: https://play.google.com/store/apps/details?id=com.example.app&referrer=utm_source%3Dnewsletter%26utm_medium%3Demail%26utm_campaign%3Dspring_launch. The %3D characters are encoded equals signs, and the %26 characters are encoded ampersands. Get the encoding wrong and Play Console reports garbage or nothing, which is why I recommend building these links with a URL builder rather than hand encoding them.

How to track app store links with UTM parameters on each store

On Google Play, the payoff lives in Play Console under store performance, where you can view acquisition by UTM campaign and UTM source. That reporting depends on the referrer parameter surviving the click, which it does for Play Store links shared on the web, provided the user installs through that link path. It does not survive every path. If a user sees your ad, searches for the app manually in the Play Store, and installs, there is no referrer to read, and that install lands in organic or unattributed traffic. UTM tracking measures the links people click, not the awareness those links create.

Apple is a different conversation. App Store Connect reports web referrers: traffic that reached your listing from a web page, grouped by the referring site. That tells you which web sources sent listing visitors, which is useful and also incomplete. Apple does not hand your app the UTM values from a store link the way Google Play referrer does, and Apple link tracking protection can strip parameters in private browsing contexts. So an iOS campaign measured only by store link UTM values will undercount, and the undercount will be uneven across channels, which is worse than a clean miss because it distorts the comparison.

The practical fix is a landing page between your campaign and the store. The campaign link points to a page you control, tagged normally with utm_source, utm_medium, and utm_campaign. That page records the values in your analytics, then offers a clear store button. You lose a slice of click through to the extra step, and I will not pretend otherwise. What you gain is attribution that does not depend on the store preserving your parameters, plus a page where you can test messaging, capture an email, or explain the app before asking for an install. For paid campaigns, that tradeoff usually pays for itself in the first reporting cycle, because a campaign you cannot measure is a campaign you cannot improve.

The naming discipline that makes it work

Whichever route you take, keep the naming boring and consistent. Lowercase values, underscores instead of spaces, one canonical name per channel, saved as a preset so the whole team uses it. I have seen spring_launch, spring-launch, SpringLaunch, and spring launch all used for one campaign, producing four rows in a report that should have had one. A preset in your UTM builder is not bureaucracy. It is the difference between a report you can read and a report you have to clean before every meeting.

Test the full path before launch, on a real device, not just in a browser. Click the campaign link, confirm the landing page records the values, tap through to the store, and check that Play Console or App Store Connect shows the source within a day or two. If it does not show, the problem is usually encoding on Play or a stripped parameter on Apple, and it is far cheaper to find that in testing than after a launch budget is spent. Attribution is not a feature you add after the campaign. It is the campaign link itself, built correctly the first time.

Frequently asked questions

How do you track app store links with UTM parameters on Google Play?

Use the referrer parameter on the Play Store URL, with your UTM values URL encoded inside it, for example play.google.com/store/apps/details?id=com.example.app with a referrer value of utm_source%3Dnewsletter%26utm_medium%3Demail%26utm_campaign%3Dspring_launch. Play Console then reports the campaign under store performance.

Can you use UTM parameters on Apple App Store links?

Not in the same way. Apple App Store Connect reports web referrers for traffic that reaches the listing from the web, but iOS does not pass arbitrary UTM values into the app the way Google Play referrer does. Use a landing page and App Store Connect sources together.

Why do my UTM parameters disappear on app store links?

Because the store is a different domain that strips or ignores query parameters it does not recognize, and because Apple link tracking protection strips parameters in private contexts. A tagged link to the store directly is the most fragile setup.

Should I send traffic to a landing page or straight to the store?

A landing page, for any campaign you need to measure. The landing page captures the UTM values in your own analytics, then links onward to the store. You lose some click through rate to the extra step, and you gain attribution you can actually trust.

Do I still need an attribution tool for app installs?

For install to revenue attribution, yes. UTM values and store consoles tell you where the click came from. Firebase, Adjust, or AppsFlyer connect that click to what the user did inside the app, which is the part that decides whether a campaign was worth running.

Related reading: UTM Parameters for YouTube: What Actually Survives the Click · QR Code UTM Tracking: What Survives the Scan · Why Your UTM Parameters Are Not Showing in GA4 · UTM Naming Conventions That Survive a Growing Team

Try the tool

Build your campaign URLs here with saved presets, so the values you test are the values everyone uses.

Get new free tools by email

Want the next guide in your inbox? Subscribe to the free newsletter on Substack. No spam, unsubscribe anytime.