Consent Mode Basic vs Advanced: The Measurement Trade-Off

Consent Mode v2 can be deployed two ways, and the choice has significant consequences for your data. Basic mode blocks all Google tags until a visitor grants consent. Advanced mode loads the tags immediately, in a restricted state, and sends cookieless pings before consent is granted. The names are misleading. The actual difference is whether Google tags load before consent, and what Google learns from the visitors who say no.

The four signals, and what each one controls

Consent Mode v2 defines four mandatory parameters. The two carried over from v1 govern on-page storage: ad_storage, which governs advertising cookies, and analytics_storage, which governs analytics storage. The two added in v2 are downstream instructions to Google services about how user data may be processed: ad_user_data, which governs whether advertising-related user data can be sent to Google, and ad_personalization, which governs whether personalised advertising is allowed. The dependency that teams miss most often is that ad_user_data and ad_personalization must both be granted for any personalised advertising to work.

Consent Mode v2 has been mandatory for EEA and UK advertisers since March 6, 2024, and the direct legal driver is the EU Digital Markets Act, not GDPR. That matters, because the obligation to implement it is separate from the obligation to collect consent, and a site can be compliant with one and not the other. The banner is not the consent signal. The banner captures a choice in the browser, and Consent Mode is the separate signal layer that communicates that choice to Google's tags.

Basic mode: nothing leaves until yes

In basic mode, Google tags do not load until the user accepts. If the user denies, the tags never fire. No data flows to Google for that user: no measurement, no advertising, no modelling. The cookie banner becomes the gatekeeper for the entire Google measurement stack, and for websites with low consent rates, that can mean substantial blind spots in reporting. Basic mode is the most conservative option, and the simplest to explain to a privacy officer, because no data leaves the browser before consent.

The cost is that Google has no signals to model from for visitors who decline. Conversion modelling needs cookieless pings from denied users to calibrate against, and basic mode provides none. Google publishes no general recovery rate for either mode, so be wary of any single percentage, but the direction is clear: basic mode gives Google less to work with, and the modelled column stays emptier for longer.

Advanced mode: pings before consent, modelling after

In advanced mode, Google tags load with a default state of denied for all four parameters. When the user grants consent, the state updates to granted and the tags begin recording fully. When the user denies, the tags continue to fire, but in a restricted state, sending what Google calls cookieless pings: anonymous signals about page views and conversion events, with no identifiers that link back to an individual. Those pings are what feed Google's conversion modelling, and without them the model has nothing to calibrate against.

The legal caveat is real. Advanced mode sends cookieless pings before consent is granted, and whether those pings constitute personal data processing under Article 5(3) of the ePrivacy Directive is still debated. France's CNIL has issued mixed guidance, Italy's Garante has been more permissive, and Germany's regulators vary by region. The practical answer for most sites is to run advanced mode unless a legal team specifically requires basic, but that answer assumes a legal team has looked at it, and many have not.

The thresholds nobody meets

Modelling does not activate automatically, and most small advertisers never meet the thresholds. Google Analytics 4 requires 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 analytics_storage denied for seven days. Google Ads conversion modelling activates once an advertiser meets a daily ad click threshold of 700 ad clicks over a seven-day period, per country and domain grouping. Below that volume, the implementation is correct and the modelled column stays empty.

That is the honest ceiling. Advanced mode is the right choice for advertisers who want more complete measurement within the rules, and basic mode is the right choice for a strict privacy stance, but neither one recovers conversions for a site that does not have the volume to model from. The implementation order is the same either way: the CMP loads first, the default consent state is declared before any Google tag, the tags fire in a restricted state, and the user's choice updates the state. Get the order wrong, and neither mode works.

Frequently asked questions

What is the difference between basic and advanced Consent Mode?

Basic blocks all Google tags from firing until a visitor grants consent. If someone clicks Reject All, nothing is sent to Google: no cookies, no pings, no signals. Advanced loads Google tags immediately, but in a restricted state, and before consent is granted the tags send cookieless pings, which contain no personal identifiers and no cookies, but do transmit contextual signals such as the timestamp, user agent, and whether a conversion occurred.

Does advanced mode automatically recover my lost conversions?

No. Modelling does not activate automatically. Google Analytics 4 requires 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 analytics_storage denied for seven days. Below that volume, the implementation is correct and the modelled column stays empty.

Is advanced mode legal under GDPR?

It is still debated among data protection professionals. Advanced mode sends cookieless pings before consent is granted, and whether those pings constitute personal data processing under Article 5(3) of the ePrivacy Directive is not settled. France's CNIL has flagged the cookieless ping as a data transfer that requires consent or legitimate interest justification. Run advanced mode only after a legal review.

Is Consent Mode a replacement for a consent banner?

Consent Mode v2 is the mechanism that tells Google's tags whether a user agreed to be tracked. It is not a compliance solution, it is a signalling layer that sits between a separately required consent management platform and Google's advertising and measurement stack. A banner captures the choice, and Consent Mode carries it into the tags. If your banner records a preference but never fires the consent update, the tags never learn what the user decided.