# Consent Mode and Analytics: What Breaks When Users Say No

Source: https://cookierampart.com/blog/2026-11-06-consent-mode-analytics-denied.html

[Home](../index.md) / [Blog](index.md) / Consent Mode and Analytics: What Breaks When Users Say No


Published 2026-11-06

A visitor clicks Reject All, and your analytics setup faces a question it was never designed to answer: what do you still get to know about someone who said no. In Consent Mode v2 the answer is specific. With analytics\_storage denied, Google Analytics 4 stops setting cookies and stops collecting identifiers, but in advanced mode it still sends cookieless pings: the page, the timestamp, the conversion event, no identity attached. In basic mode it sends nothing at all. The difference between those two sentences is the difference between a reporting gap and a reporting hole.

Consent Mode v2 has been mandatory for EEA and UK advertisers since March 2024, and it runs on four signals: ad\_storage, analytics\_storage, ad\_user\_data, and ad\_personalization. The analytics question is about one of them, and it is the one most sites misunderstand.

## What you lose, precisely

When analytics\_storage is denied in basic mode, GA4 collects nothing from that visit. No pageview, no session, no event. The visitor is invisible, and any report built on that data understates traffic by the share of visitors who decline. Only about 31 percent of users accept tracking cookies on average, according to vendor analyses, which means a basic-mode site can be reporting on less than a third of its traffic and calling it the whole picture.

In advanced mode, the tags load with the signals denied and send cookieless pings. Google uses those pings to model behaviour and conversions it cannot observe directly, comparing the anonymous cohort against consented users on the same site. The modeled numbers appear in GA4 as modeled data, not observed data, and they only appear at all above a threshold: at least 1,000 daily users with analytics\_storage granted for seven of the last 28 days, plus at least 1,000 daily events with it denied for seven days.

## The threshold is the whole decision

Do the arithmetic for your own site before choosing a mode. A site with 400 visitors a day and a 30 percent consent rate has 120 consented users a day, far below the 1,000 needed for behavioral modeling, and its denied-event count is 280 a day, also below threshold. Advanced mode buys that site nothing on the analytics side. Its reports will show the same gap as basic mode, with extra complexity and a privacy position to defend.

A site with 5,000 visitors a day clears the threshold easily, and the choice reverses. Advanced mode recovers modeled behaviour for the 70 percent who decline, and the reports get closer to reality. The decision is a volume test, not a values test, and the honest answer for a small site is basic mode, chosen deliberately, with the gap stated plainly in every report that uses the data.

## How to report honestly with a gap

Label every GA4 number with its consent coverage. A report that says 12,000 sessions without saying those are consented sessions is overstating its confidence. The modeled numbers, where they exist, should be labeled modeled, not merged silently into observed counts. Google shows modeling uplift for four weeks after modeling starts, with observed and modeled conversions listed separately, and that separation is worth preserving in your own reporting.

And check the implementation, not just the mode. The four signals must default to denied before any tag loads, and the update to granted must fire only on accept. A site that loads the analytics library before the defaults are set has already collected the data the visitor was about to refuse. The mode choice is irrelevant if the load order is wrong, and the network panel is the only honest witness.

Keep reading: [Your Banner Keeps Coming Back Because the Consent Cookie Died](2026-11-05-consent-cookie-expiry-scope.md), [Server Side Tagging Hides Cookies From Your Own Scan](2026-11-05-server-side-tagging-consent-gap.md), and [The Reject Button Audit: Placement, Wording, and Colour Traps That Fail Review](2026-11-04-reject-button-placement-audit.md) cover the nearby cases in this series.

## Frequently asked questions

### What happens to GA4 when a visitor denies analytics storage?

In basic mode, nothing is collected from that visit. In advanced mode, GA4 sends cookieless pings with no identifiers, and Google models the behaviour it cannot observe, subject to volume thresholds.

### What volume does GA4 need for behavioral modeling?

At least 1,000 daily users with analytics\_storage granted for seven of the last 28 days, plus at least 1,000 daily events with it denied for seven days. Below that, no modeling happens.

### Should a small site use basic or advanced mode?

Basic mode, in most cases. A site below the modeling thresholds gains nothing from advanced mode on the analytics side, and basic mode is simpler to explain and defend. Choose deliberately and label the reporting gap.

### How do I label GA4 numbers honestly with a consent gap?

State the consent coverage alongside the number, and keep modeled conversions labeled as modeled rather than merging them into observed counts. A report on consented sessions is not a report on all traffic.