We run a small villa holiday business and launched Google Search and Meta ads on 11 November. We then noticed high new-user numbers, lots of Direct traffic and very little engagement. We’re not analytics experts, so I’d appreciate a sanity check before changing anything.
The day before launch, our implementation changed to allow GA4 and Clarity measurement before someone made a cookie choice. Later checks also found advertising tracking enabled before a choice. Those were separate settings—not just cookieless measurement with consent denied.
We’re reviewing the consent setup separately. My question is whether we started measuring automated visits that were already happening, rather than suddenly attracting more bots. Cloudflare’s HTML request volumes didn’t show a matching jump.
The clearest suspicious group we found was Android + screen resolution 375×812. At the snapshot we reviewed, across 12–13 November:
78 of 344 GA4 sessions matched that combination.
77 were Direct; one had no source set.
None were engaged sessions or recorded key events.
None were attributed to advertising, search or social.
They landed across different deep pages, not just the homepage.
Cloudflare evidence was available for only 36 of them. Those showed hosting/proxy networks, no referrer and one page each.
We know that isn’t definitive bot proof. Screen dimensions can be misleading, the network evidence is incomplete, and genuine visitors can leave without engaging.
We’ve already ruled out using broader shortcuts. The same screen size appeared on genuine iPhones. Older Android browser signatures appeared on Google-ad landings and real enquiries. Meta’s network carried both suspected review/preview activity and apparent Facebook in-app visitors. We don’t want to block customers or break ad review.
Our proposed first step is simply a saved GA4 reporting segment for that Android/screen combination, labelled “suspected automated traffic,” so we can compare reports with and without it. Nothing has been excluded, blocked or deleted, and the segment hasn’t been created yet.
For people who have investigated something similar:
What would you check first to distinguish newly visible automation from duplicate tags, client-ID resets, repeated first_visit events, attribution loss or fabricated analytics hits?
Is that reporting segment a sensible starting point? What legitimate traffic could it accidentally include?
What evidence would you require before moving from a reporting segment to any collection exclusion?
How do you compare GA4, Clarity and Cloudflare when their coverage and bot classifications differ?
For a small UK advertiser below consent-modelling thresholds, how do you keep campaign reporting useful while implementing appropriate consent?
We’re happy to report uncertainty and unattributed enquiries. We don’t want to make engagement numbers look better by removing anyone who doesn’t convert. What would you do first, and what would you deliberately leave alone?