
A visitor clicks your LinkedIn ad, lands on your post, and converts three hours later. Your analytics show the source as “direct.” You’ve just lost attribution to a redirect chain you didn’t know existed.
Redirect chains—sequences of HTTP 301, 302, or JavaScript redirects between the click and the destination—rewrite referrer headers, strip query parameters, and introduce enough friction that most analytics platforms give up. The problem isn’t your tracking code. It’s the path the browser takes to reach it.
Where redirect chains appear
Link shorteners are the obvious culprit. A Bitly link issues one redirect. A branded short domain that also uses a link management platform underneath can issue two or three before the browser sees your landing page.
Social platforms add another layer. LinkedIn, Twitter, and Facebook route outbound clicks through their own tracking domains—t.co, l.facebook.com, lnkd.in—before releasing the visitor. Each redirect is an opportunity for UTM parameters to vanish or referrer headers to reset.
Then there’s your own infrastructure. If your landing page lives at example.com but you linked to www.example.com, and your server issues a redirect to the canonical version, that’s another hop. Add HTTPS enforcement, trailing-slash normalization, or a CDN that rewrites URLs on the fly, and you’ve built a four-step chain without realizing it.
What gets stripped and when
HTTP 301 and 302 redirects should preserve query parameters. In practice, some proxies and CDNs rewrite the destination URL and drop anything after the ?. JavaScript redirects—window.location or meta refresh tags—are worse: they often construct a new URL without copying the query string from the current page.
Referrer headers degrade with each hop. A redirect from HTTPS to HTTP will strip the referrer entirely, per the Referrer Policy spec (checked November 2026). Even HTTPS-to-HTTPS chains can reset the referrer if an intermediate domain sets Referrer-Policy: no-referrer or if the browser applies strict privacy defaults.
The result: your analytics platform sees no UTM parameters and no referrer. It labels the visit “direct,” and you’ve lost the thread back to the ad spend that generated it.
How to trace the loss
Start by walking the chain manually. Paste your full campaign link—UTMs intact—into a new incognito tab and watch the address bar. Each time the domain changes, you’re crossing a redirect. Note whether the query string survives.
Browser developer tools make this visible. Open the Network tab, disable caching, and load the link. Look for 301, 302, 307, or 308 status codes. Check the Location header in each response: does it include your UTM parameters? If not, you’ve found the break point.
For referrer loss, inspect the request headers on your landing page. If Referer is missing or shows an intermediate domain instead of the original source, the chain rewrote it. Cross-reference that against the Referrer-Policy headers in each redirect response.
Mitigation strategies
The cleanest fix is to shorten the chain. If you’re using a link shortener for branded links, configure it to redirect directly to your final canonical URL—HTTPS, correct subdomain, trailing slash if your CMS requires it. Avoid layering a second shortener or tracking wrapper on top.
When you control the infrastructure, audit your server and CDN rules. Eliminate redundant redirects: if your CDN already enforces HTTPS, don’t duplicate that rule in your origin server. Consolidate www and non-www, HTTP and HTTPS, and trailing-slash normalization into a single redirect when possible.
For JavaScript redirects, preserve the query string explicitly. Instead of window.location = 'https://example.com/page', append window.location.search to the destination URL. The same applies to meta refresh tags: include the full query string in the content attribute.
If you can’t eliminate the chain, move attribution upstream. Some analytics platforms let you capture UTM parameters in a first-party cookie on an intermediate page, then read that cookie on the final destination. This works as long as the intermediate and final domains share a root—.example.com—and the cookie is set with SameSite=Lax or None; Secure.
Finally, test every campaign link end-to-end before you publish it. Click it from the platform where it will appear—LinkedIn, your newsletter, a Twitter bio—and verify that your analytics dashboard captures the correct source. Don’t assume. Redirect behavior changes when platforms update their link-wrapping logic or when your hosting provider tweaks caching rules.
Want more infrastructure deep-dives like this? Subscribe to One Two Three Send for weekly operator-focused breakdowns of the tools and systems that power online businesses.
Redirect chains are silent. Your analytics won’t flag them. The only symptom is a rising “direct” count and a nagging sense that your attribution doesn’t add up. Walk the path your visitors take, and you’ll find where the trail goes cold.
