How can we measure visitors who reject cookies or consent?

Run a cookieless analytics tool alongside GA4. Simple Analytics records pageviews and events without cookies or a visitor identifier, and does not read your banner's consent state, so wherever its script loads it counts the page load, whatever the visitor chose. Content blockers can still stop it. You get aggregate counts, not profiles: it does not identify the people who rejected consent or reconstruct their journeys.

The consent analytics gap

Is website traffic falling, or is GA4 measuring less of it? Simple Analytics gives you an independent, cookieless pageview count to compare with GA4, so you can investigate what changed.

Book a demo

Plan a free 30-day proof of concept on your own website.

Consent can change what GA4 observes

A consent gap is a measurement limitation associated with visitors declining analytics consent. Its effect depends on how your tags are configured. Simple Analytics does not read the consent state, so it records pageviews wherever its script loads and gives you a second count to compare.

Basic Consent Mode

Google tags remain blocked when consent is denied. Those visits do not send analytics data through the blocked tags.

Advanced Consent Mode

Google tags can send cookieless pings while analytics_storage is denied. GA4 can use behavioral modeling to estimate users and sessions when the property qualifies.

In GA4 reports, behavioral modeling does not model page_view event counts. Modeling eligibility can nevertheless affect whether denied-consent events are reportable. Check the reporting surface as well as the requests.

Google’s Consent Mode documentation · Behavioral modeling and reporting

Investigate the difference

If Simple Analytics reports more pageviews than GA4, consent may explain part of the difference. Missing tags, blocked requests, duplicate events, filters and report settings can also contribute.

Initial customer POC results

A global industrial technology company compared LinkedIn campaign reporting with Simple Analytics and GA4 over the same period.

LinkedIn reported clicks

1,000

Simple Analytics page loads

640

GA4 reported sessions

270

Normalized to 1,000 LinkedIn clicks. The initial POC covered a few hundred clicks; the proportions shown come from that comparison. These are three different metrics, not interchangeable visitor counts.

The setup has since improved.

The extended POC tests whether an improved setup narrows the difference between recorded campaign traffic and the reported click count. Subsequent setup improvements have increased the traffic recorded by Simple Analytics. The figures above remain the initial result; the updated comparison is not yet available.

LinkedIn clicks are not a count of website arrivals.

A reported click does not establish that the landing page loaded or that an analytics request completed. The difference can include both clicks that never became recorded page loads and collection limitations. It does not, by itself, prove that LinkedIn counted clicks incorrectly.

Likewise, the difference between 640 page loads and 270 sessions is not a count of visits lost to consent. The metrics have different definitions. The POC gives the team evidence to investigate those differences, rather than treating any one total as the definitive count.

Check these before interpreting the gap

Match the metric

Start with GA4 page_view event counts and Simple Analytics pageviews. Sessions, users, ad clicks and pageviews are not interchangeable.

Match the scope

Use the same dates, timezone, hostnames and pages. Check internal-traffic filters, bot handling and exclusions in both tools.

Check collection

Test a fresh browser state before consent, after rejection and after acceptance. Inspect requests and consent updates. Check for missing tags and duplicate pageviews, including SPA navigation.

Check the report

Record the GA4 reporting identity, modeling status and report used. Allow for processing time. Receiving an event does not guarantee that it appears in the report you are comparing.

A missing event in DebugView is not proof that no request was sent. Inspect the network request and consent state too. Keep a record of CMP, tag and reporting changes so you can compare them with changes in the totals.

What a second count from Simple Analytics helps you investigate

Campaign clicks versus recorded traffic

For example, LinkedIn reports 200 clicks and GA4 reports 30 sessions. Those figures count different things. Compare tagged landing-page traffic in both analytics tools, then investigate redirects, lost campaign parameters, tag loading and consent behavior. Simple Analytics adds evidence; it does not turn clicks and sessions into the same metric.

Traffic decline versus measurement change

If GA4 pageviews fall after a CMP change while Simple Analytics pageviews remain stable, that is a reason to inspect consent and tag behavior. It is not proof that the CMP caused the drop. Compare affected pages, channels and dates, and check whether either implementation changed.

A baseline for reporting

Use the pageviews and events Simple Analytics records as another reference for traffic trends. If you extrapolate from GA4’s consenting traffic, label the result as an estimate: a larger denominator alone does not establish how non-consenting visitors behave.

Run Simple Analytics alongside GA4

Simple Analytics records pageviews and events without creating persistent visitor identities. Its session starts are calculated from pageview context, so they are not equivalent to GA4 sessions.

Keep GA4 for the user-level analysis it supports. Use Simple Analytics for an independent traffic comparison. It does not reconstruct cross-visit attribution or guarantee that every visit is captured.

Keep your CMP and review the implementation with your privacy team. Our measurement method and legal explanation covers what we collect, how we calculate sessions and the trade-offs.

Test the difference on your own website

Start with a free 30-day proof of concept. We’ll help you establish a comparison you can explain to your team.

Define the question

Choose the domain, pages and campaign segments to compare. Agree on metrics and record the current GA4 and CMP configuration.

Run both for 30 days

Keep GA4 and your CMP in place. We help implement Simple Analytics and optimize collection with a proxy or custom domain where appropriate.

Review the evidence

Compare the agreed metrics, investigate discrepancies and decide whether the additional dataset meets your reporting needs.

Book a demo

Questions about the comparison

How much traffic is GA4 missing on our website?

There is no reliable universal percentage. It depends on consent choices, tag behavior, report settings and implementation. A parallel comparison can establish the difference between two measurements. Further checks are needed to explain it.

Does Simple Analytics put the missing data back into GA4?

No. It provides a separate dataset. You can compare the tools in your reporting workflow, but this does not restore GA4 visitor identities or reconstruct historical journeys.

Can we subtract GA4 sessions from Simple Analytics sessions?

You can calculate the numerical difference, but it is not a count of missing visitors. The tools define sessions differently. Start with comparable pageview counts, then examine session trends with the definitions documented.

Can we use Simple Analytics to scale up GA4 conversions?

A traffic baseline can support an estimate, but it does not prove that people who accept and reject consent behave alike. State that assumption explicitly and validate it where possible. Do not present a scaled estimate as an observed conversion count.