# Consent Mode v2 Basic vs Advanced: The Choice That Decides Your GA4 Numbers

Source: https://cookiecitadel.com/blog/2026-11-15-consent-mode-basic-vs-advanced-ga4.html

[Home](../index.md) / [Blog](index.md) / Consent Mode v2 Basic vs Advanced: The Choice That Decides Your GA4 Numbers


Published 2026-11-15

Most sites running Google Consent Mode v2 never chose between Basic and Advanced. The CMP picked one, or the developer copied a snippet, and the site has run that way since March 2024. The choice decides how much of your traffic GA4 can model and how much of your conversion data survives a rejection, and it is worth making on purpose instead of inheriting it.

Consent Mode v2 has been required since March 6, 2024 for sites running Google Ads or GA4 with traffic from the European Economic Area, and the enforcement around personalization tightened further in July 2025. The framework translates a visitor's banner choice into four signals Google understands: ad\_storage, analytics\_storage, ad\_user\_data, and ad\_personalization. Version 1 handled two signals. Version 2 added the two that separate data collection from data activation, and that split is what the Basic versus Advanced decision is about.

## What each mode actually does

Basic mode blocks Google tags entirely until a visitor grants consent. Nothing fires, nothing pings, nothing reaches Google in any form until the CMP records an explicit granted state. It is the simpler and stricter option, and it is the right one for a team that would rather keep the setup minimal than recover modeled conversion data.

Advanced mode loads Google tags immediately but sends cookieless pings when consent is denied. Google uses those pings, alongside granted first-party data, to build conversion models that estimate what would have been measured if consent had been granted. The data quality is higher and the legal risk profile is higher too, because data leaves the browser before consent. Whether those pings count as personal data processing under Article 5(3) of the ePrivacy Directive is still debated among data protection professionals, and that debate is the reason Advanced mode should get legal sign-off before going live.

## The thresholds that decide whether modeling works at all

Modeling 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. Google Ads needs at least 700 ad clicks over seven days per country and domain grouping. A small site that picks Advanced mode for the modeling benefit may never clear the thresholds, which means it took the legal exposure and got none of the measurement back. Check the thresholds before choosing the mode, not after.

The sequencing matters as much as the mode. Set default consent states to denied for EEA and UK visitors until they actively accept, and add a wait\_for\_update of roughly 500 milliseconds so the CMP has time to push a stored choice before tags fire. Use Consent Initialization for the defaults, never Page View, to avoid timing failures. The single biggest factor separating working implementations from broken ones is the order the tags fire in, not the mode selected.

## The cost of getting it wrong

Sites still not on Consent Mode v2 have been silently losing remarketing audiences, conversion modeling, and personalized advertising eligibility since the deadline. GA4 reports drop 15 to 40 percent of conversions in countries with high reject rates, with Germany typically above 50 percent, France at 35 to 45 percent, and Italy at 25 to 35 percent. The certified-CMP requirement took effect January 16, 2024 for the EEA and UK and July 31, 2024 for Switzerland. Both dates have passed, and the requirement is not going away.

Pick the mode on purpose. Choose Advanced if preserving conversion measurement matters more than implementation simplicity and your traffic clears the modeling thresholds. Choose Basic if you would rather keep the setup minimal and do not rely heavily on Google's modeled conversion data. Either way, write the choice down with the reason, and check the tag firing order the same week. A mode chosen by accident is a compliance position you cannot defend.

Keep reading: [The Banner Fires Again on app.yoursite.com: Subdomain Consent, Fixed](https://cookiecitadel.com/blog/2026-11-14-subdomain-consent-banner-again.md), [Your Cookie Policy Page: What Regulators Expect It to Actually List](https://cookiecitadel.com/blog/2026-11-14-cookie-policy-what-it-must-list.md), [GPC Is Not a Banner Setting: What the Global Privacy Control Signal Actually Does](https://cookiecitadel.com/blog/2026-11-13-gpc-global-privacy-control-signal.md) cover the nearby cases in this series.

## Frequently asked questions

### What is the difference between Basic and Advanced Consent Mode v2?

Basic mode blocks Google tags entirely until a visitor grants consent, so no data of any kind reaches Google before that point. Advanced mode loads tags immediately and sends cookieless pings when consent is denied, which Google uses for conversion modeling. Basic is simpler and stricter; Advanced recovers more measurement.

### How many signals does Consent Mode v2 require?

Four for EEA and UK traffic: ad\_storage, analytics\_storage, ad\_user\_data, and ad\_personalization. Version 1 handled only the first two. The two new signals separate data collection from data activation, which is why Google now requires all four for personalized ads.

### When did Consent Mode v2 become mandatory?

Google required its signals for EEA traffic under its EU User Consent Policy from March 2024. The certified-CMP requirement took effect January 16, 2024 for the EEA and UK, and July 31, 2024 for Switzerland.

### Why is my GA4 data still low after implementing Consent Mode v2?

Modeling has thresholds: GA4 needs at least 1,000 daily users with analytics\_storage granted for seven of the last 28 days, plus at least 1,000 daily denied events for seven days. Below those thresholds there is no modeling. Also check tag sequencing: defaults must fire on Consent Initialization with a wait\_for\_update of about 500 milliseconds.