Consent banners hide part of your clients' traffic from GA4
When visitors reject the consent banner, GA4 can't measure them in the usual way. With basic Consent Mode it receives nothing from them. With advanced Consent Mode it gets cookieless pings, and eligible properties can model users and sessions.
In the EU, most websites operate behind a consent banner. When a visitor clicks "Reject", GA4 doesn't report their pageviews, and the rest is at best modeled:
- Pageviews
- Sessions
- Attribution
Ad blockers also stop GA4 from loading for some visitors.
The result: part of your traffic doesn't show up in GA4.
Those missing visits can skew dashboards, attribution models and performance reviews.
The fix isn't replacing GA4. Add a cookieless traffic baseline alongside it, so you have a second count to compare.
Case Study
GA4
≈1.6M
Simple Analytics
2.03M
Difference
≈431K
(+27% vs GA4)
Hebban, a Dutch book community, counted about 431,000 more pageviews in Simple Analytics than GA4 reported.
Free 30-day proof of concept on your own traffic, set up together.
A real example
We ran this side by side with Hebban, a Dutch book community. GA4 kept its behavioural data for visitors who consented, while Simple Analytics counted pageviews in parallel, without depending on the consent choice.
Case study
Hebban.nl: about 431,000 more pageviews
GA4
≈1.6M
Simple Analytics
2.03M
Difference
≈431K
(+27% vs GA4)
Simple Analytics counted about 431,000 more pageviews than GA4 reported. The comparison shows the size of the gap, not its exact cause.
Read the Hebban comparison →Agency example: how VertoDigital plans a conversion check alongside GA4 →
How the additional layer works
Simple Analytics is a privacy-first analytics tool that does not use cookies, trackers, or personal data. Because no personal data is processed, consent is not required to measure pageviews while remaining GDPR-compliant.
GA4 remains responsible for behavioural depth and attribution. Simple Analytics provides an independent traffic baseline.
Together, you get a second count to compare with GA4.
Why this matters for agencies
If you manage clients:
- GA4 underreports total traffic
- Campaign performance may be inaccurate
- Attribution may lack full context
A difference like Hebban's (27% more than GA4) changes how results are interpreted.
Running a parallel baseline gives you:
- A second count to compare with what GA4 reports
- More defensible reporting
- Fewer "traffic dropped after CMP change" conversations
Complement, don't replace.
Run it on one client
- 01
Install Simple Analytics next to GA4.
- 02
Run both for 30 days.
- 03
Compare totals.
There is no migration required. No CMP changes. GA4 stays in place.
Setup takes minutes, and the script loads asynchronously.
Go deeper
Why Simple Analytics and GA4 show different numbers →
What to check when a client's two counts disagree.
Google Analytics and cookie consent →
What GA4 records when visitors say no, and what Consent Mode models.
Does server-side tagging fix GA4 gaps? →
What server-side tagging changes, and what it doesn't.
Compare the counts on your own website
Tell us what you want to compare. We agree on the scope of the proof of concept together.
Smaller website, no procurement? Start for free.