GA4 Tells You reddit.com Sent Traffic. It Won't Tell You Which Thread.

Someone linked to you and it sent real traffic. GA4 will happily tell you it came from reddit.com.

Which subreddit? Which thread? Which comment? GA4’s standard reports have no opinion. You get the hostname and a session count, and if you want to know what people were actually reacting to, you go and search Reddit by hand.

The full URL is not missing. It is in a dimension the standard reports do not use.

The short version

Explore → Free form, then:

• Row dimension: Page referrer
• Value: Sessions
• Filter: Session medium exactly matches referral

You now have the full referring URLs, path and all.

Why the default reports do this

It is not an oversight. Session source is built for channel grouping, and channel grouping needs aggregation. If every distinct Reddit thread produced its own row, “Referral” as a channel would be thousands of rows of noise and you could never answer “how much traffic does Reddit send us.”

So GA4 normalises to the hostname on purpose. The trade-off is that the question “which page linked to us” falls out of the default reporting entirely, even though the data is right there.

	sessionSource	pageReferrer
Example value	reddit.com	https://www.reddit.com/r/analytics/comments/1abc.../
Built for	channel grouping	raw attribution
In standard reports	yes	no
In the Data API	yes	yes
Aggregates cleanly	yes	no, and that is the point

The filter is not optional

Without the sessionMedium = referral filter your table fills with:

• your own domain, from internal page-to-page navigation
• (not set) rows, where no referrer arrived
• search engines, which you probably want counted as organic rather than referral
• campaign traffic, where UTM parameters already told you the answer

Filtering to referral leaves you with the actual question: other people’s pages, pointing at yours.

Where the referrer honestly is not there

This dimension has real gaps and it is better to know them up front than to conclude your data is broken:

• Stripped by referrer policy. A site sending Referrer-Policy: no-referrer or strict-origin gives you either nothing or the bare origin. This is increasingly common and entirely the linking site’s choice.
• In-app browsers. Links opened inside social and messaging apps frequently drop the referrer on the first hop.
• HTTPS to HTTP. Browsers do not send a referrer when downgrading the connection. Rare now, but it happens.
• Redirect chains. Each hop can rewrite or lose the header, so you may see the redirector rather than the origin.

The result is a floor, not a census. Treat a missing referrer as unknown rather than as direct traffic — they are different things and conflating them will mislead you.

What it is genuinely useful for

Three jobs where the hostname alone is useless:

Finding out what people said about you. A traffic spike from news.ycombinator.com is interesting. The specific thread URL is actionable, because you can go read it and find out whether the conversation was positive.

Backlink verification. You believe an outreach placement went live. pageReferrer shows the exact URL that is actually sending humans, which is a stronger signal than a backlink tool reporting the link exists.

Finding the page you did not know about. Documentation, a forum answer, an internal wiki at a large company — steady referral traffic from a URL nobody on the team knew existed is one of the more valuable things sitting in this dimension.

The pattern worth noticing: hostname data answers how much. Full-URL data answers why. Almost every interesting referral question is a why question.

Why we put it in the product

We kept rebuilding this exploration, so GA4 Simple View has a Referral Details panel that runs exactly the query above — pageReferrer, filtered to sessionMedium = referral, ordered by sessions — and shows the full URLs alongside sessions and users. No exploration to construct, and it is there every time you open the tab.

Two honest limits: the panel shows the top 15 referring URLs, because past that it becomes a log file rather than a report, and it cannot recover referrers the browser never sent. Nothing can.

If you only need this occasionally, the exploration above is genuinely all you need — it takes about a minute to build and costs nothing.