Why a redirect can lose your source
A redirect is a link that sends someone from one address to another. They click example.com/promo, and their browser is quietly bounced onward to your real page. Shorteners, link-in-bio pages, affiliate links, and campaign links all work this way. It is useful, and it is also the single most common place tracking silently breaks, which is why "how do I redirect track properly" comes up so often.
Two things get lost in the bounce, and it helps to know exactly which.
The first is the referrer. Browsers pass along a hint about where a visit came from, but modern browsers deliberately trim it. The default policy, strict-origin-when-cross-origin, sends only the origin and not the full path when a visit crosses to another site (MDN). So after a hop between domains, your analytics may see "came from somewhere on twitter.com" instead of the exact post, and across some redirects it can vanish to nothing.
The second is the query string, the ?utm_source=... part. If the redirect is set up to send people to a clean destination URL and does not carry those parameters forward, they are simply dropped on the way through, and the tags you carefully added never arrive.
| What a redirect can lose | Why | The fix |
|---|---|---|
| The referrer detail | browsers send only the origin across sites by default | put tags on the final destination URL |
| The query string (UTMs) | a redirect may not carry ?utm_... forward | use a redirect that passes the query string, and test once |
How to keep the source through a redirect
The fix for both is the same principle: make sure the information survives the hop, rather than trusting it to.
The most reliable move is to put your tracking parameters on the final destination URL, the one the visitor actually lands on, not only on the link they clicked. If the tags live on the page they end up at, no earlier bounce can strip them. When you are setting up a track redirect url flow, that is the habit that saves you: tag the end of the journey, not just the start.
If the parameters have to ride along from the clicked link, then use a redirect that explicitly carries the query string through to the destination. Most purpose-built redirect and campaign tools do this by default. The one non-negotiable step is to test it: click your own real link once, land on the page, and check that the ?utm_... parameters are still sitting in the address bar. Thirty seconds of checking beats a launch reported as "direct."
Do shorteners and redirects break UTM tracking?
This is the myth worth correcting, because the honest answer is "usually not, but check." Most reputable link shorteners redirect straight to your full tagged destination, so the UTM parameters arrive intact, the same point covered in UTM parameters for email. A short link is a redirect, and a good one is a transparent one.
The trouble comes from two specific cases. Some cheap or misconfigured redirects strip the query string, which is exactly the failure above. And a link-in-bio page like Linktree is a redirect that, by design, only tracks up to the click and does not carry your on-site tracking any further. So when you are trying to track url redirects, the rule is not "avoid redirects," it is "use ones that pass everything through, and confirm the final URL once."
The honest limit
Even a redirect that preserves the source perfectly only tells you the channel a click came from. It does not tell you which person clicked or what they did after landing. Preserving the UTM tags keeps your channel data honest; it does not answer the per-person question.
That gap is the one an early-stage founder usually feels most, and it needs a different tool from a redirect.
A redirect that preserves the source still only tells you the channel, never which person clicked or what they did next. ScoutVibe uses tracked links that carry the source through and then show you what each visitor did on your site. The free tier covers your next launch.
Try ScoutVibeFAQ
Why does a redirect sometimes lose where my traffic came from?
Two reasons. Browsers trim the referrer by default (the strict-origin-when-cross-origin policy sends only the origin, not the full path, across sites), so after a hop your analytics may see only a rough source or none. And if the redirect sends people to a clean URL without carrying the ?utm_... query string forward, those tags are dropped entirely. Either way the origin detail goes missing in the bounce.
How do I keep the source through a redirect?
Put your tracking parameters on the final destination URL, the page the visitor actually lands on, so no earlier redirect can strip them. If the parameters have to travel from the clicked link, use a redirect that carries the query string all the way through, and always test once by clicking your real link and confirming the ?utm_... parameters are still in the address bar when you land.
Do link shorteners and redirects break my UTM tracking?
Usually not. Most reputable shorteners redirect straight to your full tagged URL, so the parameters arrive fine. The exceptions are misconfigured redirects that drop the query string, and link-in-bio pages that only track up to the click. So the rule is to use redirects that pass everything through and to confirm the final landed URL once, not to avoid redirects altogether.