UTM parameters lost after redirect

Knowledge base

Why this issue happens

UTM parameters are the glue between ad platforms, analytics dashboards, and finance reports. When a redirect chain removes utm_source or utm_campaign, every dashboard collapses into (direct)/(none).

Because UTMs are plain text, every smartlink, CDN rule, or CMS plugin feels free to rewrite them. You need a structured workflow to prove where the loss occurs and to enforce a fix.

This article explains why UTMs disappear after redirects, how to document the failure, and how to use Redirect Checker, Click ID Extractor, UTM Builder, Postback Tester, and Facebook CAPI Tester to keep your tracking template intact.

Diagnosis flow

Start with one question: do the UTMs disappear inside the redirect chain, on the final landing page, or later when a form, CRM, or callback rewrites the URL? That diagnosis decides who owns the fix.

In a clean setup, the ad platform sends a tagged URL, each redirect merges those parameters with its own template, and the landing page stores the final string for analytics and CRM systems. In the broken version, one hop or page rebuilds the URL without preserving the incoming query string.

Common problems

Common culprits include link shorteners that expand and instantly rewrite parameters, CMS redirect managers that drop everything after ?, and smartlinks that only allow a fixed whitelist. Internal teams are equally dangerous when they copy 'clean' URLs and paste them back into ads or email tools.

Even when redirects behave, workload balancers, CDN rules, and cookie banners may strip UTMs under the guise of security or privacy. Documenting the exact failure is the only way to resolve it with stakeholders.

• Shorteners that expand the link and replace the query string with their own tracking parameters.
• JavaScript redirects that custom-build window.location and forget to include the original UTMs.
• CMS tools that enforce canonical URLs and remove everything after the question mark.
• Consent tools that redirect users to a clean URL before scripts can capture UTMs.
• Manual edits where marketers copy a link from analytics (without UTMs) and share it with agencies.

How to check it

Replicate the journey and record the redirect chain. Run the destination through Redirect Checker, save each hop, and compare the query string against your approved template.

Then compare the final URL against the canonical link you would build in UTM Builder or decode the broken example in UTM Decoder. Once you know exactly where the mismatch starts, you can hand the evidence to the team that owns that hop or page.

1. Capture the chain

   Use Redirect Checker to log each hop and highlight where the UTMs disappeared.

2. Verify final URLs

   Paste the resolved link into Click ID Extractor to confirm that UTMs arrive alongside click IDs.

3. Publish canonical templates

   Rebuild the approved URL with UTM Builder and share it with every team and partner.

4. Check server callbacks

   Send a sample conversion through Postback Tester to ensure UTMs make it into any downstream payloads.

5. Validate server events

   Replay the fixed journey with Facebook CAPI Tester to confirm your server-side events still include the correct UTMs.

Use these tools

Use Redirect Checker to locate the lossy hop, UTM Builder to rebuild the correct template, and UTM Decoder when you need to inspect or clean up a live tagged URL.

If you already confirmed the loss, move to the practical resolution path in Fix UTM parameters lost after redirect and keep those tool outputs as evidence for the owner of the redirect or page template.

How to fix it

Fix the specific owner of the breakage: redirect rule, landing page template, smartlink allowlist, or script that rebuilds the URL. Then retest the full journey with the same tagged link until the final page preserves every required parameter.

Once the redirect path is stable again, rebuild the approved launch version in UTM Builder and redistribute that canonical link instead of letting teams relaunch an old broken variant.

After the immediate fix, publish one canonical template, keep example good/bad journeys in your docs, and rerun the check whenever redirects, domains, or partner links change.