You spend twenty minutes building a campaign URL with source, medium, campaign, term, and content tags. You paste it into a social scheduler, send it through a link shortener, and watch the clicks roll in. Then you open your analytics dashboard and see half the traffic attributed to “direct” or a generic referrer that has nothing to do with your campaign.
The problem isn’t your tracking setup—it’s the redirect chain between your tagged link and the final destination. Every hop is an opportunity for parameters to get stripped, overwritten, or malformed.
Where parameters disappear in the chain
Most link shorteners preserve query parameters by default. Bit.ly, TinyURL, and Rebrandly all append your UTM tags to the destination URL when someone clicks. But not all redirects behave the same way.
If your destination URL is itself a redirect—say, a landing-page builder that forwards to a Stripe checkout, or a ConvertKit form that redirects to a thank-you page—each step in that chain can rewrite the URL. Some platforms strip all query parameters on redirect. Others preserve them but only if the destination field includes a placeholder like ?original_params or {query}.
CDN-level redirects are another common failure point. If you’ve set up a redirect rule in Cloudflare, Fastly, or your WordPress host’s edge config, check whether it’s configured to forward query strings. Most dashboards default to “no” unless you explicitly enable passthrough.
Which tools rewrite tags and which preserve them
Social media platforms handle UTM parameters inconsistently. LinkedIn’s link wrapper preserves them. Facebook’s l.facebook.com redirect usually does too, but if your link triggers a security interstitial or a “leaving Facebook” warning, parameters can get lost in the process.
Email service providers are generally safe. MailerLite, Brevo, and Postmark all preserve query parameters in click-tracking redirects, though you should confirm that your click-tracking domain is configured correctly—mismatched SSL or DNS can cause the ESP to fall back to a generic redirect that doesn’t pass parameters.
Landing-page builders vary. Carrd preserves parameters by default. Unbounce does too, but only if you’ve mapped the destination URL as a dynamic field. Webflow’s form-redirect action strips them unless you add a query-string rule in the redirect settings (checked November 2026, per Webflow’s redirect documentation).
How to test your redirect chain before you publish
Paste your full tagged URL into a browser’s private window. Before you hit enter, open the browser’s network inspector (right-click, “Inspect,” then click the “Network” tab). Load the URL and watch the waterfall. Each redirect will appear as a separate request. Click into each one and check the “Headers” section for the Location: field. If your parameters are missing from any step, that’s where the chain breaks.
If you’re using a link shortener, check whether it offers redirect preview. Bit.ly’s /info endpoint shows the full destination URL, including any appended parameters. Rebrandly’s dashboard shows the same under “Link Details.”
For landing-page redirects, create a test page with a known UTM string and fire it through the funnel. If the final thank-you page or checkout URL is missing the tags, check the platform’s redirect or form-action settings. Most builders document parameter passthrough in their knowledge base, but the setting is rarely enabled by default.
When to skip UTM tags entirely
If your funnel includes more than two redirects, or if you’re driving traffic through a third-party platform you don’t control (app stores, marketplaces, affiliate networks), UTM tagging becomes fragile. In those cases, use a dedicated campaign parameter that your analytics tool can parse separately—like ref= or via=—and append it only to the final destination URL, not the intermediary links.
Some operators skip URL tagging altogether and rely on referrer headers. That works for organic social and direct website links, but referrer data gets stripped when users click from HTTPS to HTTP, or when browsers enforce referrer policies like no-referrer or strict-origin. It’s not a replacement for explicit campaign tagging.
Want more breakdowns like this? Subscribe to One Two Three Send and get operator-focused guides like this one every week—no fluff, just the mechanics that matter.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.