Back to the tool

Why Are My UTM Parameters Being Stripped? The 5 Usual Suspects

Your campaign link is perfect. You click it, the page loads, and the address bar shows a clean URL with no UTM parameters anywhere. GA4 records the visit as Direct, your paid traffic vanishes from the reports, and you spend the afternoon wondering if you built the link wrong.

You built it fine. Something between the click and the landing page ate your parameters. Here are the 5 places they go missing, in the order I would check them.

The first suspect is the redirect chain

This is the most common cause. Your link says http:// but the site forces https://. Your link points at /pricing but the server prefers /pricing/. Each of those is a redirect, and a redirect only carries the query string forward if it was configured to. Most default redirect rules carry only the path. The fix is boring and effective: build your UTM links with https:// from the start, match the site's trailing-slash convention exactly, and run the finished link through a redirect checker (the Redirect Path browser extension shows every hop) before the campaign launches. If the parameters survive every hop, the chain is clean.

Next, the URL shortener

Some shorteners and click-tracking tools drop query strings on redirect. The short link resolves to the right page, so everything looks fine, but the UTMs never make the trip. Test the shortened link in an incognito window and watch the address bar after the page loads. If the UTMs are gone, the shortener is the problem. The fix is a different shortener, or your own redirect that you control.

Third, the server config

If you control the hosting, the fix is one flag. On Apache, redirect rules need the QSA (Query String Append) flag, as in RewriteRule ^old-page$ /new-page [R=301,L,QSA]. Without it, the rule redirects the path and discards the query string, UTMs included. On Nginx the equivalent is preserving $is_args and $args through the redirect. Back up the config before touching it. One typo in a server config file takes down more than your tracking.

Fourth, the single-page app

Sites built with React, Vue, and similar frameworks handle routing in JavaScript, and client-side routing sometimes "cleans" the URL after the page loads, wiping the UTMs. The cruel version of this bug: GA4 reads the URL after the cleanup, so the parameters existed when the tag could have read them and were gone by the time it did. This one needs a developer, not a marketer. The analytics tag has to capture the parameters before the router rewrites the URL, or the router has to be told to leave query strings alone.

And the last one: the in-app browser

Links opened inside the Facebook, Instagram, or LINE app run in embedded browsers that handle referrers and URLs their own way. Some drop the UTMs or mangle the referrer before your analytics ever sees them. You cannot fix someone else's app. What you can do is keep the UTMs on the link anyway, because the ones that survive are the only attribution you get, and treat in-app traffic as a known-approximate channel in your reports.

The 30-second test

One diagnostic habit ties all of this together. Before launch, paste the finished UTM link into an incognito window, let the page load fully, and look at the address bar. If the parameters are still there, your chain is intact. Then check GA4's real-time report: if the visit shows up with the right source and medium, the whole path works. That 30-second test catches 4 of these 5 suspects before they cost you a campaign's worth of data. The fifth, the in-app browser, you will never fully control, and the honest move is to say so in the report instead of pretending the numbers are exact.

Frequently asked questions

Why do my UTM parameters disappear after the page loads?

Something between the click and the landing page strips them: a redirect chain that does not preserve query strings, a URL shortener that drops them, a server rule without the QSA flag, client-side routing in a single-page app, or an in-app browser. Test the finished link in an incognito window and watch the address bar.

Do redirects always strip UTM parameters?

No, but default redirect rules often carry only the path. A redirect preserves the query string only if configured to: the QSA flag on Apache, $is_args and $args on Nginx. Check each hop in the redirect chain.

Can a URL shortener remove my UTM parameters?

Yes. Some shorteners and click-tracking tools drop query strings on redirect. Test every shortened link in an incognito window and confirm the UTMs survive before using it in a campaign.

Why does GA4 show my paid traffic as Direct?

Because by the time the GA4 tag read the URL, the UTM parameters were gone. The visit is real; the attribution is lost. Fix the stripping point and the traffic will attribute correctly going forward. Lost attribution cannot be recovered retroactively.

How do I test that my UTMs survive the redirect chain?

Paste the tagged URL into an incognito window, let the page fully load, and check the address bar. Use the Redirect Path browser extension to see every redirect hop. Then verify in GA4's real-time report that the visit arrives with the correct source and medium.

Related reading: How to Test UTM Parameters Before Launching a Campaign · UTMs Not Showing in GA4? The Checklist · UTM Parameters and Case Sensitivity · QR Code UTM Tracking · UTM Naming Conventions That Survive Growth

Try the tool

Build the tagged links cleanly in the first place. 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? I publish one practical guide per new tool. Subscribe to the free newsletter on Substack. No spam, unsubscribe anytime.