Bot Traffic IndexThe bot problem, quantified

Referral Spam in GA4: The Fake Traffic That Wants You to Visit It

Open the GA4 traffic acquisition report and there it is: a referrer you have never heard of, sending hundreds of sessions, all with zero engagement, all landing on the homepage. It is not a partner, not a customer, and not a mistake. It is referral spam, and the domain exists for one reason: to get you to visit it.

What referral spam is, and why it exists

Referral spam is fake traffic sent to your site with a referrer header set to a domain the spammer controls. In the old Universal Analytics days it worked by sending hits directly to the tracking endpoint without ever visiting the site. In GA4 it is harder, but it still happens: bots that do visit, or that send measurement protocol hits, with a referrer attached. The goal is not to hurt your site. It is to appear in your reports, because a curious analyst will click the referrer to see where the traffic came from, and that visit is the product. Some of those domains host malware, some host affiliate offers, and some are just traffic for sale.

The tell is the pattern, not the domain. Hundreds of sessions from a source you do not recognize, engagement time near zero, exactly one page per session, and only the automatic page_view and session_start events. That is the same fingerprint as most bot traffic, because referral spam is bot traffic with a marketing goal. Imperva's 2025 Bad Bot Report found automated traffic made up 51 percent of all web traffic in 2024, the first year it passed human traffic, and bad bots alone were 37 percent. Your GA4 shows much less, because GA4 filters the bots it knows about and many bots never run the tracking script at all.

How to confirm it in GA4

Open Reports, then Acquisition, then Traffic acquisition, and filter to Referral. Read the session source list. A legitimate referrer has a story you can tell: a partner, a directory, a publication. A spam referrer has a domain you cannot place, with engagement near zero and session durations under two or three seconds across hundreds of visits. Then open User attributes, Demographic details, and switch to Country: a local store with 400 sessions from a country it has never served is looking at bots. Do the same for browser and operating system under Tech details, where old browser versions and unusual screen sizes are common bot tells.

The Realtime report is the fastest check. If a spike is running right now, you will see the country, the page, and the source live, and a spike with no campaign, no press, and no email behind it is almost never human. Bot spikes usually land in Direct, Referral, or Unassigned, which is the first place to look when traffic doubles on a Tuesday for no reason. For the broader set of signs, see Headless Browsers: How They Fake a Real Browser.

Filtering it out, and why that is not the fix

GA4 removes traffic from bots on the IAB known-bots list automatically, and you cannot see it or turn that off. What gets through is the unlisted rest, and the first step is the filter GA4 does give you: confirm known-bot filtering is on, then create a filter or a comparison that excludes the spam source. That cleans the report. It does not clean the traffic. The bots are still hitting the site, loading the server, and skewing anything that is not GA4, including the server logs, the ad platform numbers, and the conversion rate.

The real fix is at the edge: bot detection that scores requests before they reach the site, and that separates traffic deserving friction from traffic that should move normally. GA4 cannot do that, because it only sees the requests that run its script, and many bots never do. A filter in GA4 is a reporting fix. The traffic is still there, and the next spam domain will be different, which is why the filter list grows and the problem does not shrink. The checkout version of the same traffic is Bot Traffic and Checkout Abandonment: The Inflated Rate.

Frequently asked questions

What is referral spam?

Fake traffic sent to your site with a referrer header set to a domain the spammer controls, hoping you will visit it out of curiosity. The domain may host malware, affiliate offers, or traffic for sale.

How do I spot referral spam in GA4?

In the Traffic acquisition report, filter to Referral and look for sources you do not recognize with near-zero engagement and sessions under two or three seconds. Check country and browser under User attributes and Tech details for patterns that do not fit your audience.

Does GA4 filter referral spam automatically?

It filters bots on the IAB known-bots list automatically. What gets through is the unlisted rest, including bots that never run the tracking script and measurement protocol spam. You need custom filters for those.

Is filtering in GA4 enough to fix bot traffic?

No. A GA4 filter cleans the report, not the traffic. The bots still load the server and skew server logs, ad platform numbers, and conversion rates. The real fix is bot detection at the edge, before requests reach the site.