What Google Consent Mode is
Consent Mode is an interface between your cookie banner and the Google tags on your website. The banner – in the jargon, the CMP or consent management platform – asks the visitor. Consent Mode passes the answer on to Google Analytics, Google Ads and Tag Manager so that they act accordingly: measure when consent has been given, and hold back when it has not.
Technically, this happens via four signals. analytics_storage and ad_storage control whether cookies for analytics and advertising may be set. Version 2 added ad_user_data (may user data be sent to Google for advertising?) and ad_personalization (may personalised advertising, such as remarketing, be shown?). If the two new signals are missing, Google treats the data as if nobody had consented.
Why Google has required it since March 2024
The background is the EU’s Digital Markets Act (DMA). It obliges large platforms to obtain verifiable consent for the use of personal data for advertising purposes. Google passes this obligation on to advertisers: since March 2024, websites with visitors from the European Economic Area need Consent Mode v2 for remarketing lists, audiences and conversion measurement in Google Ads to keep working. Without the signals, the lists shrink and bidding strategies work with incomplete data.
Basic or Advanced: the two variants
Basic Consent Mode
The Google tags only load once the visitor has consented. Before that, nothing is transmitted, not even an IP address. If someone declines, the visit stays invisible. Google only roughly fills the gap with a general model.
Advanced Consent Mode
The tags load immediately, but in the “denied” state. Without consent, they send cookieless pings: no cookies, no identifier – but the IP address, time and browser details. From these, Google models the missing conversions much more accurately.
The advanced variant delivers better figures, but is disputed under data protection law: even a cookieless ping transfers the IP address to Google before anyone has consented. Which variant you use is something you decide with your legal adviser. I set up both properly and explain the difference using your own figures.
Typical implementation mistakes
- Default state set too late: the default “denied” must be in place before the first tag loads – otherwise the tags measure without consent in the first few milliseconds.
- Banner sends no update: the visitor consents, but the signal never reaches Google. The data is missing without anyone noticing.
- Only version 1 implemented: ad_user_data and ad_personalization are missing, so remarketing and audiences in Google Ads run empty.
- Duplicate implementation: one Analytics code hard-coded in the theme and a second in Tag Manager – one of them doesn’t check for consent.
- Online shops without a purchase signal: the order is measured, but transmitted without a value and without the consent status.
This is checked with Google’s Tag Assistant and the consent view in Tag Manager’s preview mode: for every page view, you can see which state applies and which tag actually sends data.