Analytics

What Is Google Consent Mode v2 and How to Implement It | Complete Guide 2026

October 23, 2026 · 10 min read

Key takeaways

Google Consent Mode v2 passes the user's cookie-banner choice to Google tags (GA4, Google Ads), which adjust their collection based on consent, through four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. For Google Ads services in the EEA and UK, Consent Mode v2 has been required since March 2024, and for publisher products a certified CMP with TCF v2.2 is needed. You can run Basic (tags don't load until the choice) or Advanced (tags run limited and send cookieless pings for conversion modeling). It doesn't replace the consent banner and it's not a way around consent: it's the correct way to respect the user's choice without needlessly losing measurement data.

Google Consent Mode v2 is a mechanism that passes the user's cookie-banner choice to Google tags, which adapt their behavior based on consent. Instead of collecting everything unconditionally, tags receive a consent state and decide what they can do: use cookies, send advertising data or personalize ads.

Version 2 added two new signals over the original version, covering sending user data to Google and ad personalization. It's the standard framework through which Google makes sure measurement and advertising respect consent, especially in the European Economic Area and the UK.

In short, because without it you're either non-compliant or left with incomplete data. Here's why it matters and what the benefits are:

Compliance: for Google Ads services in the EEA and UK, Consent Mode v2 has been required since March 2024; without it, features like audiences and remarketing no longer work properly.
Less data loss: in Advanced mode, Google recovers part of the conversions through modeling, even when the user declines cookies.
Clear control: you decide exactly which signals you send and under what conditions, respecting the user's choice.
Better measurement: campaigns get more consistent signals, which helps bidding algorithms optimize correctly.
Lower risk: a correct setup reduces exposure to fines and to Google features being blocked in regulated markets.

Your consent platform (CMP) collects the user's choice and sends the consent state to the tags before they collect data. Based on that state, each Google tag decides what it can do. If the user accepts, tags work normally; if they decline, behavior is limited, depending on the chosen mode (Basic or Advanced).

Order matters: the CMP must run first, before the other tags, because data collected before the consent signal can create compliance risk. Consent Mode doesn't collect consent itself; it only passes on and applies the choice made in the banner.

Each signal is set to granted or denied, and tags behave based on the combination:

ad_storage: allows or blocks cookies and identifiers used for advertising.
analytics_storage: allows or blocks analytics cookies (for example, those used by GA4).
ad_user_data: controls sending user data to Google for advertising purposes. (new in v2)
ad_personalization: controls personalized ads and remarketing. (new in v2)

For EEA traffic, best practice is for all four signals to start as denied and switch to granted only after a positive user action in the banner.

Both are compliant if they start from denied; they differ in how much data you lose when the user declines. The main differences:

Criterion	Basic	Advanced
Tag loading	Google tags don't load until the user responds to the banner	Tags load from the start but run limited until consent
On refusal	Nothing is sent to Google	Cookieless pings are sent
Conversion modeling	No	Yes (requires enough traffic volume)
Data recovery	Minimal	Better: recovers part of conversions via modeling
Complexity	Simpler to set up	Requires careful configuration
Best for	Low traffic or very strict requirements	Most sites with volume and media budgets

Simple rule: if you invest in Google Ads and want to lose as little measurement as possible, Advanced mode is usually the right choice, provided you have enough volume for modeling.

Consent Mode works through a consent management platform (CMP), and for regulated markets the CMP must be certified by Google. Certifications are separate: a CMP can be certified for TCF v2.2, for Consent Mode or for both. For Google publisher products (AdSense, Ad Manager, AdMob) in the EEA and UK, a certified CMP integrated with TCF v2.2 is required.

To check whether your CMP supports Consent Mode v2, look up its name in Google's certified CMP list (both for TCF v2.2 and for Consent Mode) and in IAB Europe's list. If it's not there, Google features in regulated markets may not work through that CMP. Widely used CMPs that support Consent Mode v2 include CookieYes, Cookiebot, Cookie Script, Usercentrics, OneTrust and others.

The cleanest implementation is through Google Tag Manager, together with a certified CMP. The typical steps:

Set default states before any tag — for EEA traffic, all four signals to denied, loaded on all pages, before the other tags.
Cover the v2 parameters — make sure you send both ad_user_data and ad_personalization, not just the original signals.
Enable consent settings in GTM — turn on "Consent Overview" in container settings and review the consent settings on each tag.
Connect the CMP — enable Google Consent Mode in the CMP's integrations and map Google Ads and GA4 to the right purposes.
Make the CMP run first — consent signals must be sent before any other tag fires.
Test before publishing — use GTM preview and Tag Assistant to confirm behavior across all consent states.

After implementation, verification is a must: a setup that looks right in the UI can send the wrong signals. The most useful methods:

Tag Assistant (incognito): open the site in an incognito window, start a session at tagassistant.google.com and check the default state before the banner (should be denied for EEA traffic), then confirm it flips to granted after acceptance.
The gcs parameter on hits: on network requests, gcs=G100 means denied and gcs=G111 means granted. It's the fastest spot check.
Cookieless pings in Advanced: on refusal, Advanced mode should still send cookieless pings. If nothing is sent, you're usually in Basic or the setup is broken.
All four signals: confirm that ad_storage, analytics_storage, ad_user_data and ad_personalization update correctly on acceptance and refusal.
GA4 DebugView: check live that events and the consent state reach GA4 correctly.

Note: Tag Assistant confirms Consent Mode is wired up, but can't tell Basic from Advanced apart; for that you look at the pings and the gcs parameter.

If you use server-side tracking, consent must be respected on the server too, not just in the browser. We carry Consent Mode v2 signals from the browser to the tagging server, so every tag on the server respects the user's choice. On top of that, on the server we can minimize and anonymize personal fields and set data rules per platform.

In short, server-side gives you more control over what's passed on, but it's never a way around consent. Compliance depends on the consent you collect and the data you share, not on the technical architecture.

At Data Revolt we implement Consent Mode v2 end to end and test consent the way a regulator would: we click every option and check what actually leaves the browser. We take on the full technical side, document it clearly and re-check it after every release. Here's what we cover:

Consent audit: we scan cookies, tags and outgoing requests, check what fires before and after each choice and compare it with your cookie policy, then give you a list of risks ordered by priority.
CMP setup: we choose a suitable CMP, preferably Google-certified, configure categories, texts and design together with your legal team and connect it to Google Tag Manager through its official template.
Consent Mode v2, Basic or Advanced: all four signals, default states per region (EEA, UK, Switzerland) and a clear rationale, so your legal team can decide with full information.
Tag governance in GTM: every tag tied to the consent category it needs, with consent checks and triggers, including platforms with their own mechanisms, such as Microsoft UET consent mode.
Server-side and advertising platforms: we pass the consent state to your server-side container and to your platforms (Google Ads, Meta Ads, TikTok Ads, etc.), with data minimization on the server.
Documentation and monitoring: we document what each tag collects, under which consent and for what purpose, and re-check consent behavior after site releases.

We don't provide legal advice: we implement technically what your legal team or DPO decides and give them the documentation they need. Explore our Analytics services or request a consent audit at hello@datarevolt.agency.

Conclusion

Consent Mode v2 is no longer optional in regulated markets: it's how you respect user consent without needlessly losing measurement data. With the right default states, the four signals configured, a certified CMP and serious verification, you get compliant, trustworthy measurement.

If you want to check whether your current setup is correct or build it from scratch, write to us at hello@datarevolt.agency and we'll run a consent audit together.

FAQ

Yes, it's recommended. analytics_storage governs GA4, and in Advanced mode you can recover part of the non-consented sessions through modeling. If you ever use audiences or remarketing, Consent Mode becomes required anyway.

Yes. Most certified CMPs have plugins or apps for WordPress and Shopify, and the signals are passed through Google Tag Manager or directly via gtag.

It's mandatory for the EEA and UK. Outside those markets it depends on local law; we usually apply geo rules so consent and signals apply where required.

What happens to remarketing and audience lists if I don't have Consent Mode v2?

For EEA users, without the correct consent signals audience lists and remarketing no longer populate, and ad personalization degrades.

Yes, it can be implemented directly via gtag.js, but through Google Tag Manager it's cleaner, easier to maintain and to control per tag.

Yes. There are consent settings for apps as well (Android and iOS, via Firebase and GA4), where signals are handled in the app rather than a web banner.

Do I need to reconfigure my Google Ads campaigns after implementing Consent Mode v2?

You don't rebuild the campaigns. You make sure they use data and conversions collected with consent; after implementation you verify the signals arrive correctly and modeling kicks in where relevant.

A standard setup usually takes a few days to 1-2 weeks, depending on the CMP, the number of tags and validation. Complex setups (server-side, multiple domains) take longer.

Reviewed by the Analytics team, Data Revolt.

Sources: Google (Consent Mode, Tag Assistant, certified CMP list) · IAB Europe TCF v2.2 · industry sources (iubenda, CookieYes, Cookie Script, consentmanager). Modeling thresholds and technical details may vary; verify Google's official documentation at implementation.

Key takeaways