Traffic source attribution breaks when visitors

Traffic source attribution breaks when visitors block referrers

Browsers and privacy tools strip referrer headers, making it impossible to track where visitors came from—here’s what you’re missing and how to work around it.

The dashboard says ‘direct’ for forty percent of your traffic. Not because people typed your URL by hand, but because their browser quietly removed the referrer header before the request left their machine.

Safari blocks it by default. Firefox gives users a toggle. Privacy extensions strip it wholesale. By the time the visitor lands on your page, you have no idea whether they came from a newsletter link, a social post, or a search result—everything arrives looking like a blank direct visit.

Tomorrow’s premium edition walks through exactly which browsers block what, how referrer policies break attribution across platforms, and the workarounds that still function when tracking headers vanish. You’ll see the gap between what your analytics report and what’s actually happening, which UTM parameters survive stripping, and when server-side tracking can fill the void.

If your conversion reporting relies on knowing where traffic originates, this is the breakdown you’ve been missing—and the fix list that closes the attribution gap without asking visitors to disable privacy tools.

Read the full edition

Tomorrow’s premium edition breaks down which browsers strip referrers by default, how privacy extensions kill attribution wholesale, and the tracking methods that still work when headers disappear.

Hope this helps you see what’s missing,
The One Two Three Send Team

PS: Knowing which traffic sources vanish in your reports helps you stop optimizing for phantom channels that never existed.