Fake traffic in GA4: bots, spam and self-inflicted noise
A spike that makes no sense, a referral from a site you have never heard of, hundreds of zero-second sessions. Fake traffic does not just annoy, it skews conversion rates and poisons the audiences your ads optimise on. Here is how to spot and stop it.
The three kinds of fake traffic
- Bots and crawlers: automated hits. GA4 filters known bots automatically, but not all.
- Referral and event spam: junk sources injected to get you to visit them. Rarer in GA4 than old Analytics, but it happens.
- Self-inflicted: you, your team, your developer and your uptime monitors, all counted as users.
How to spot it
Look for implausible sources, near-100% new users with zero engagement time, traffic from unexpected countries, and spikes with no campaign behind them. Segment by landing page and source: bots cluster on odd patterns real customers never make.
How to keep data clean
- Set up internal traffic filters (Admin, Data filters) for your own IPs, and switch them from Testing to Active.
- Define developer traffic so staging hits are excluded.
- Exclude uptime monitors and known crawlers at the tag or server level.
Dirty data does not just mislead you, it trains your ad platforms on the wrong people. Cleaning it is one of the fastest wins in an audit.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · Why direct traffic is too high in GA4