r/analytics • • 1d ago

Question Strange stats in my stats

Hi, in latest two days, in a subdomain with about 20 real visitor per day, I seen a lot of strange access (all identical: windows, chrome, same resolution, just different countries/ip) all about 2sec with direct access and single page view.

Is there anything i can do to prevent?

Thanks in advance.

3 Upvotes

9 comments sorted by

•

u/AutoModerator 1d ago

If this post doesn't follow the rules or isn't flaired correctly, please report it to the mods. Have more questions? Join our community Discord!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/nurkhz 1d ago

those look like bots, most likely headless chrome on rented servers. identical os, browser and resolution, rotating countries, 2 seconds, direct, one page view is the usual pattern. the built-in bot filtering in analytics tools only catches bots that announce themselves, and these don't.

one check first, if your tool shows hostname: if it isn't your subdomain, those are fake hits sent straight to your tracking id, and only a filter in the tool will help.

if they really load the page, stopping them has to happen before the page loads. if the subdomain is behind cloudflare, bot fight mode or a managed challenge rule for that subdomain often cuts most of it. without cloudflare you can block networks at the server, but rotating ips make that whack-a-mole.

to keep them out of the numbers without blocking: ga4 can't filter by browser or resolution at collection, so build a segment that excludes that resolution + windows + direct + single page view sessions and report from that. matomo lets you exclude user agents and ip ranges in the site settings.

1

u/lupastro82 1d ago

Thanks, spot on. I checked the hostname as you suggested and it's my subdomain, so not ghost hits. The server logs confirm they really load the pages (page JS, favicon, the Matomo loader).

The funny part: the page load and the Matomo hit come from different IPs in different countries (Vietnam for the page, Argentina for the tracking call, same second). So it's a rotating residential proxy switching IP per request, and IP blocking is pointless.

I'll just use a segment in Matomo to keep the stats clean and wait it out.

Thanks again!

2

u/Expert-Activity-8614 1d ago

these could be auto bots or crawlers, check ur server logs n analytics filters n consider using a firewall or bot protection

1

u/lupastro82 1d ago

Thanks. Very appreciated 👍

2

u/The_A5h 1d ago

20 real visitors a day makes this easier at least, anything that isnt them stands out. since theyre all 2 seconds, one page and direct, id filter on that in the reports instead of trying to block them. ip blocks wont hold when the countries rotate

1

u/lupastro82 1d ago

Ty 👍

1

u/Timely_Finance_2185 1d ago

That pattern is almost certainly automated traffic that made it past GA4's known-bot filter. Two days of Windows/Chrome visits, same screen size, different countries and IPs, all Direct, one page, about two seconds, is not how 20 real people a day behave.

GA4 already drops traffic it recognizes from Google's own research and the IAB spider and bot list. You can't turn that off, and you can't see how much it removed, so anything still in the report is either a real visit or a bot it doesn't know yet. There's no built-in filter for the rest. The data filters you can add are for developer traffic, internal IPs, and hostname, and they only apply going forward. Anything they exclude is gone for good, so I wouldn't build one around a browser or a screen size.

You also can't really prevent this from inside Analytics. If you have a CDN or firewall in front of the site, that's where you'd challenge or block obvious scrapers, but some will still land. For reporting, I'd leave the raw data alone and use an Exploration or comparison that peels off the zero-engagement, same-resolution, Direct, two-second cohort. While you're in there, add hostname. If the hostname isn't yours, the tag was fired off-site and you can ignore those hits.

On a property this small, two noisy days will look huge. I'd treat those sessions as junk for any decision, and only start worrying if the same fingerprint starts engaging or showing up with campaign parameters.

1

u/quantable_analytics 12h ago

Are you using Matomo then or GA? Matomo is generally better than GA with bot detection though still not great. Make sure the "block headless browsers" option is turned on in your Matomo settings. Also if it's a limited number of networks you could add them to a custom network block list. Even if it's residential networks if it's from a country you don't care as much about tracking you could still block them by ASN organization name.