Enterprise
An independent traffic baseline alongside GA4
GA4 reports the visitors who accepted your consent banner, plus whatever Consent Mode lets it model. Simple Analytics records pageviews for every page load where its script ran, without cookies or a visitor identifier. Run the two side by side and you get a second reference for traffic volume, while GA4 and your consent banner stay exactly as they are.
Free 30-day proof of concept on your own traffic, set up together.
How do I measure traffic alongside GA4 without replacing it?
You add one script and change nothing else. GA4, Google Tag Manager and your consent management platform keep running as they do today. Simple Analytics does not read the consent state and does not set cookies, so it is not gated by your consent banner and runs on every page load where the script loads. Where content blockers matter to you, the script can be served from your own domain through a proxy.
Two datasets, one page. Your existing tools keep doing what they do today.
What does GA4 answer, and what does Simple Analytics record?
They answer different questions. GA4 stays your source for behavior, attribution and anything built on a user identifier. Simple Analytics gives you an observed pageview count that does not depend on consent or on modeling, and nothing more than that.
GA4 keeps answering
- Behavior of visitors who accepted consent: events, funnels, conversions
- Modeled users and sessions where Consent Mode makes a property eligible
- Attribution, audiences and everything that depends on a user identifier
Simple Analytics records
- Observed pageviews and events for every page load where the script ran, regardless of consent state
- Session starts calculated from pageview context, not from a persistent identifier
- Referrer, UTM parameters, country from the browser time zone, device class, page path
What Simple Analytics does not do
- No visitor or user identity, no persistent session ID, no fingerprint
- Attribution stays where it is: a visitor who rejected consent is not identified afterwards
- Nothing GA4 already collected is changed or back-filled
How this works in detail: sessions without consent and what is collected.
What does a real comparison look like?
Hebban, a Dutch book community, ran Simple Analytics next to GA4. The two tools reported these pageview totals.
| Measurement | Reported pageviews |
|---|---|
| GA4 pageviews | approximately 1.6 million |
| Simple Analytics pageviews | 2,031,468 |
| Difference, using 1.6 million for GA4 | approximately 431,000 |
GA4's count is about 21% lower than Simple Analytics' count; put the other way round, Simple Analytics reports about 27% more pageviews than GA4. The denominator changes the percentage, so we always name it. These are pageviews, not people or consent decisions, and the difference alone does not say how much came from rejected consent, blocked requests, tag coverage, duplicate events or reporting settings. Working that out is what the proof of concept is for.
What does a 30-day proof of concept cover?
A defined comparison on your own traffic, with the methodology written down before the first number is read.
- 01
Agree the question, the metric and the period
Pageviews first, because they are the unit both tools report. Matching dates and time zone, the same filters, a written note of your consent banner and Consent Mode configuration.
- 02
Install the script next to GA4
One script tag. GA4 and your consent banner are not touched. A proxy or custom domain is optional and we help set it up when content blockers matter for you.
- 03
Compare weekly for 30 days
Pageview trends side by side, with the differences reviewed against their methodological causes: duplicate tags, SPA routing, bot filtering, consent configuration, reporting identity.
- 04
Receive a written comparison
What the two datasets show, why they differ, and what that means for your reporting. We do not promise an uplift.
Where the counts have limits
- The script has to load and its request has to arrive. Content blockers, disabled JavaScript and network filtering remove page loads from the count.
- Visitors with Do Not Track enabled are excluded by default.
- Bot filtering differs between tools and can explain part of the difference.
- Pageviews are comparable across tools; sessions and users are not, because each tool defines them differently.
How does the data reach my reporting stack?
The same aggregated data you see in the dashboard is available through the API and exports, so the comparison can live next to your GA4 reports in the tools you already use.
What will security and procurement ask for?
The documents most reviews need are public. Everything runs on European-owned infrastructure in the EU, and no personal data is collected. The pages below answer the questions most reviews ask.
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.
Go deeper
The consent analytics gap →
Why two tools show different pageview totals after a CMP rollout.
Analytics without consent →
What is collected, what is not, and where the limits are.
Sessions without consent →
How session starts are calculated without a visitor identifier.
GDPR compliance →
How Simple Analytics handles privacy regulations.
Security →
SOC 2 certified. Enterprise-grade infrastructure.
The Hebban comparison →
The comparison behind the numbers on this page.
Google Analytics and cookie consent →
What GA4 records when visitors say no, and what Consent Mode models.
How GA4 collects data →
Where collection and reporting can make counts differ.
Does server-side tagging fix GA4 gaps? →
What server-side tagging changes, and what it doesn't.