You check your analytics and see a spike in traffic labeled “direct” or “(none).” But you didn’t send a newsletter. You didn’t post anywhere. Someone linked to you—probably from a newsletter, a Slack community, or a private Discord—but the referrer header never made it to your server.
Privacy-focused browsers, browser extensions, and network-level tools strip referrer information by default. When someone clicks a link from a context that blocks referrers, your analytics can’t see where they came from. You lose attribution, and “direct” traffic becomes a junk drawer.
What gets stripped and when
Referrer headers disappear in three common scenarios. First, when a user browses with referrer blocking enabled—Safari’s default privacy settings, Firefox’s Enhanced Tracking Protection in strict mode, or extensions like uBlock Origin and Privacy Badger all strip or limit referrers.
Second, when the source is HTTPS and your site is HTTP. Browsers won’t send an HTTPS referrer to a non-secure page. If you’re still running mixed content or haven’t forced HTTPS sitewide, every secure referrer vanishes.
Third, when the link comes from a native app, email client, or messaging tool that doesn’t pass referrer headers by default. Slack’s desktop app, Apple Mail, and some Reddit mobile clients all fall into this category.
The result: your analytics tool records the session as “direct / none,” even though the visitor arrived from a specific, trackable source.
What shows up instead
When the referrer header is missing, most analytics platforms—Google Analytics 4, Plausible, Fathom, Matomo—classify the session as direct traffic. But if you’re using UTM parameters in your links, those still work. UTM tags are appended to the URL itself, so they survive referrer blocking.
If you shared a link as https://yoursite.com/post?utm_source=slack&utm_medium=community, analytics will attribute the session to “slack / community” even if the referrer header is blank. The UTM parameters override the missing referrer.
That’s the fix for traffic you control. If you’re posting links yourself—in newsletters, on social media, in communities—always append UTM tags. Tools like Beehiiv and MailerLite add them automatically to email links, but you need to add them manually for Slack posts, Reddit comments, and anywhere else you share URLs.
Tracking sources you don’t control
The harder problem: someone else links to you, and you can’t ask them to add UTM tags. A reader shares your post in a private Telegram group. A subscriber forwards your email. A member of a paid community drops your link in a thread. You see the traffic, but you don’t know where it came from.
One partial solution: use a URL shortener or redirect service that logs clicks before sending visitors to your site. Services like Bitly, Rebrandly, or a self-hosted YOURLS instance record the click event on their server, then forward the user. You lose the referrer, but you gain a log of when and where the short link was clicked—assuming you created the short link in the first place.
For inbound links you didn’t create, the only reliable signal is landing page data. If you see a surge of visitors landing on a specific post—not your homepage—and the source is labeled “direct,” they probably came from a link someone shared. You can sometimes reverse-engineer the source by checking where that post was recently mentioned: search Twitter, Reddit, Hacker News, or use a backlink tool like Ahrefs or Ubersuggest to see if a new inbound link appeared in the last 48 hours.
When to stop worrying about it
Referrer loss matters most when you’re testing traffic sources or trying to justify ad spend. If you’re running a paid campaign on Twitter and half the clicks show up as “direct” because users have referrer blocking enabled, your cost-per-click math breaks.
But for organic, word-of-mouth growth, referrer loss is mostly cosmetic. You still get the traffic. You still get the reader. You just don’t get a tidy label in your analytics dashboard. If your goal is to grow—not to perfectly attribute every session—treat “direct” traffic as a proxy for sharing activity you can’t track. When it spikes, something worked. You just don’t know exactly what.
If attribution matters—if you’re spending money or testing channels—use UTM parameters on every link you control. If you’re tracking organic growth, accept that some traffic will always be unattributable, and focus on the trend instead of the source.
Got a traffic attribution question? Reply to this email—we read everything and answer the best ones in future issues.
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.