What is Consent Mode v2?

Also called: Google Consent Mode, consent mode, ad_user_data, ad_personalization

The four signals are independent. analytics_storage governs analytics cookies, ad_storage governs advertising cookies, ad_user_data governs whether user data may be sent to Google for advertising purposes, and ad_personalization governs whether it may be used for personalised ads.

When a signal is denied, Google tags still fire but send cookieless pings containing no identifiers. Google then uses conversion modelling to estimate the unmeasured conversions. This is why a correct Consent Mode v2 setup reports more conversions than simply blocking tags outright.

Timing is the failure point. The default consent state must be set before any Google tag loads, and the update must fire when the user chooses. Set the default too late and the tag has already run in granted mode; forget the update and every consenting user is treated as a refusal.

Why it matters

Without Consent Mode v2 signals, EEA and UK audiences stop populating for remarketing and conversion modelling degrades — the campaigns keep spending while the measurement quietly hollows out.

Common questions about Consent Mode v2

Is Consent Mode v2 mandatory?

It is not a legal requirement, but Google requires it as a condition of using its advertising features with EEA and UK users. Without it, remarketing audiences and enhanced conversion measurement stop working for that traffic.

What is the difference between basic and advanced Consent Mode?

In basic mode, Google tags do not load at all until consent is granted, so nothing is measured beforehand. In advanced mode, tags load immediately and send cookieless pings when consent is denied, which allows Google to model the missing conversions. Advanced mode recovers substantially more signal.

Do I still need a cookie banner with Consent Mode v2?

Yes. Consent Mode consumes a consent decision — it does not collect one. You still need a consent management platform to present the choice and record it.

How do I check whether Consent Mode v2 is set up correctly?

Load the page with a network inspector and check the gcs and gcd parameters on outgoing Google tag requests before and after interacting with the banner. Correct setups show a denied-state value on load that changes after consent. Automated container audits check the same signals across every tag at once.

Related terms

See how your site handles this

TagEasy's free auditor checks any URL for Consent Mode v2 signals, PII in tracking, duplicate pixels, and 10 other tracking-quality faults. No signup.