Google Analytics and cookie consent: what happens when visitors say no?

When visitors reject analytics consent, GA4 may stop collecting data or continue sending cookieless pings. Which happens depends on your Consent Mode implementation.

That matters when you need to explain a change in reported traffic. Did fewer visits happen, or did the way you collect and report them change?

Running Simple Analytics alongside GA4 gives you another count to compare: observed pageviews and session starts calculated without visitor identifiers. To use that comparison properly, you need to understand how each tool produces its numbers.

What does GA4 collect when analytics consent is denied?

Advanced Consent Mode pings can contain a timestamp, User-Agent, referrer, consent state and a random number generated on each page load. They do not associate events with Google's normal persistent user identifier.

A CMP collects the visitor's choice. Consent Mode communicates that choice to Google tags and changes their behavior. It does not replace the CMP or establish legal compliance. See Google's Consent Mode documentation.

How does GA4 turn cookieless events into users and sessions?

Without a persistent identifier, collected events do not establish which belong to the same person. GA4's behavioral model estimates user and session behavior using consenting traffic from the same property.

That requires Advanced Consent Mode and sufficient training data. Meeting Google's published thresholds does not guarantee eligibility.

For an eligible property, Blended reporting identity allows modeled data in supported reports. The report's data-quality indicator shows whether estimated user data is included. Check it before treating a session total as entirely observed.

Event counts need a separate distinction. In reports, behavioral modeling does not model counts such as page_view, first_visit or session_start, although enabling modeling can make denied-consent events reportable. In path and funnel explorations, Google applies modeling to first_visit and session_start differently.

Behaviorally modeled data is not included in the BigQuery export. A session total calculated from that export therefore should not be assumed to reproduce a modeled total in the interface.

See Google's behavioral modeling documentation for eligibility, reporting support and these event-count distinctions.

How does Simple Analytics calculate sessions?

Simple Analytics collects pageviews and events. It classifies each pageview as unique or non-unique using its context. A unique pageview counts as a session start.

It does not create a visitor ID, hash IP addresses into identifiers, or store a persistent session ID.

The calculation answers: does this pageview start a visit? It does not identify the visitor or reconstruct their journey.

Simple Analytics calculates session starts from observed pageviews, without Consent Mode modeling. Given the same records and calculation, you get the same count.

That makes the method reproducible, but it does not make an SA session equivalent to a GA4 session. Read how we measure sessions without consent for the full method and trade-offs.

What can the comparison tell you?

The useful question is why the counts differ. A higher total alone does not answer it.

Are both tools recording the same pageviews?

Start with pageviews for the same pages and period, using the same timezone. This avoids mixing in the tools' different session definitions.

If the counts differ, look at collection first. Is each script installed on those pages? Does either wait for consent? Does internal navigation fire a pageview once, twice, or not at all? Filters and blocked requests can also affect the comparison.

Also check the reporting surface, filters and modeling eligibility: a report may not include every event received. The difference is a count of additional or fewer reported pageviews. It is not automatically the number of visitors who rejected consent.

Why don't campaign clicks match GA4 sessions?

An ad platform counts clicks; your analytics measures activity on the website. Simple Analytics adds recorded landing-page views and their referrer or UTM context to that comparison.

Compare the same campaign, landing pages and period, and name each metric. Ad clicks, landing-page views and sessions are different units. Their difference does not establish how many people failed to arrive, or how many clicks were wasted.

There is also an attribution boundary. Simple Analytics cannot link a purchase on Friday to an ad click on Monday. That requires identifying a visitor across visits, which we deliberately do not do.

Is traffic down, or has measurement changed?

Compare pageview trends for the same pages, dates and timezone. If GA4 pageviews fall while SA pageviews stay stable, check what changed around that date: consent acceptance, the CMP, tag deployment, filters or reporting settings. Review session trends separately using each tool's definition.

That gives you a specific discrepancy to investigate. It does not prove consent caused the decline. The comparison also depends on SA continuing to collect consistently.

What does running both tools give you?

GA4 remains in place for user journeys and attribution, with the appropriate consent. Simple Analytics adds pageviews, events and calculated session starts without a visitor identity.

For the analyst, this means a traffic count whose calculation does not depend on a behavioral model. You can use SA's APIs and exports to bring it into your reporting tools and compare it with GA4.

You are comparing two measurement methods. The aim is to explain the difference and understand which number answers the business question.

Does cookieless mean consent is unnecessary?

Not automatically. The assessment depends on what information is accessed or stored, how it is used, and whether an applicable exemption covers that use.

Simple Analytics avoids visitor identifiers and drops IP addresses rather than storing or hashing them. Our technical article explains the architecture, legal reasoning and remaining uncertainty.

Adding SA does not change the consent requirements of your GA4 implementation.