Answer in brief
UTM parameters are labels in a URL that tell a website where a visit came from. A tracking link is a link run by an attribution platform that records the click and connects it to an app install. UTM parameters stop at the web page, so any campaign that ends in an app needs a tracking link, and many journeys use both in sequence.
The short answer
Use UTM parameters when the destination is a web page. Use a tracking link when the destination is the app or the app store. When an ad leads to a web page that then leads to the app, the ad's URL carries UTM parameters and the page's store button is a tracking link.
How they differ
| UTM parameters | Tracking link | |
|---|---|---|
| What it is | Text added to the end of your own URL | A separate link hosted by the attribution platform |
| Who reads it | Code on the destination web page | The platform's server, at the moment of the click |
| Records a click | No. It labels a page load | Yes |
| Survives the app store | Not on its own | Yes, through the match made on first open |
| Can route the user | No | Yes: store, app screen or web page, depending on the device |
| Typical report | Web sessions by source and campaign | Installs and in-app events by channel and campaign |
Both are defined on their own pages: UTM parameters in this site's glossary, and the tracking link in how a tracking link carries a click to an install.
Why UTM parameters stop at the store
A UTM parameter only means something to the page that loads it. When a visitor taps through to the app store, the store opens its own listing and your page's URL is left behind. After the install, the app starts with no memory of that URL. Nothing is broken. It is simply how the handoff works, and it is one reason attribution platforms exist.
A tracking link avoids the problem by recording the click on a server before the store opens. The app's SDK later asks that server about the click. On Android there is also a store mechanism that hands a referrer string to the app, covered in the Google Play Install Referrer.
Using both on one journey
For an ad that leads to a landing page and then to the app, set up the chain like this.
- Put UTM parameters on the ad's destination URL so the landing page knows the source, medium and campaign.
- Make the page's store button a tracking link.
- Copy the UTM values into the tracking link's own campaign fields when the page loads. A web SDK from your attribution platform usually does this for you. Airbridge lists a related feature, automated UTM tracking, which it describes as collecting UTM parameters for web and web-to-app attribution analysis.[1]
- Check one test install and confirm the campaign name in the app report equals the campaign name in the ad's URL.
Without step three you get a common and confusing result: web analytics shows ten campaigns, and the app report shows one source called "landing page".
Three mistakes to avoid
- Renaming between systems. If the ad platform says "spring_sale" and the link says "Spring Sale", the reports will not join. Pick one spelling.
- UTM parameters on links inside your own site. In many web analytics tools they overwrite the original source of the visit. Keep them for links that come from outside.
- A tracking link where a web URL would do. If the destination is a blog post that nobody will install from, plain UTM parameters are enough.
What to do next
List every link you publish this month and mark its final destination as web or app. The app ones need tracking links. Then follow measuring a landing page that sends visitors to the app store to line the two reports up.
Questions and answers
Can I put UTM parameters on an app store link?
You can add them, but plain UTM parameters on a store link are not handed to the app, so on their own they do not tell you which campaign produced the install. Use a tracking link for any link that leads to the store.
Do I still need UTM parameters if I have an MMP?
Yes, if you send traffic to web pages. Your web analytics reads UTM parameters, and a web SDK can use them to label the click that goes on to the app.
Continue reading
Guide
How web-to-app attribution worksWeb-to-app attribution connects a web visit to the app install that follows. What the web page adds, where the match can fail, and what to check first.
Guide
Measuring a landing page that sends visitors to the app storeMeasure a landing page built to drive app installs: the four counts to collect, which tool holds each one, and how to read the drop between them.
Guide
Recognising one person across the website and the appA website and an app identify people differently. Which identifiers join the two, what a shared user ID does, and what will stay unjoined.
Guide
Why teams run web campaigns to grow an appWhy app teams send ad traffic to a web page before the app store, what the extra step costs, and how to decide whether to try it.
Guide
What the web SDK does and what the app SDK doesAn attribution platform has an SDK for your app and another for your website. What each records, how they connect, and which one you need first.
Web and app
Best attribution platform when the journey starts on the webHow seven attribution platforms handle journeys that start on the web and end in an app, and which plan you need for it.
Sources
- Airbridge: https://www.airbridge.io/en/pricing Checked 2026-11-10.
Cite this page
Airbridge. “UTM parameters versus tracking links.” bestattributionplatform.com. Reviewed 2026-11-10. https://bestattributionplatform.com/utm-parameters-vs-tracking-links