Redirects are common in short links, tracking systems, old URLs, and CMS routing. If a redirect does not preserve the query string, the destination may receive no UTM values.
What to test
- Open the complete tagged URL.
- Follow every redirect.
- Inspect the final address in the browser.
- Confirm that all expected parameters remain present.
Other causes
Canonicalization, URL rewriting, link shorteners, and JavaScript navigation can also change the final address. Test the exact link that will be published, not only the original landing page.
A successful page load is not proof that tracking survived. Use the BestUTM builder to create the source URL, then verify the live redirect chain.
Short links need special attention
Shorteners and redirect services may preserve the query string, rewrite it, or drop it. Test the exact public link rather than assuming the redirect behaves like a direct URL.
Keep a record of the expected final URL and check it again after major site, CMS, or redirect changes.
A repeatable review process
Review the link before publishing, immediately after it goes live, and again when the campaign report is first checked. These three moments catch different problems: naming errors, redirects or page issues, and unexpected reporting behavior.
Write down the correction instead of fixing one URL silently. A short record helps the whole team avoid repeating the same mistake in the next campaign.
Check canonical redirects too
A redirect from non-www to www, HTTP to HTTPS, a language route, or a trailing-slash URL can affect query handling. Test the exact version used in an ad or email, including any short link or tracking template before it.
When a redirect is fixed, re-test the public URL. Do not assume the configuration change worked until the final address proves it.
← Back to all articles