If you run Google Ads or Google Analytics and you have visitors in Europe, Consent Mode v2 isn't optional housekeeping: it's the thing standing between your consent banner and your marketing data. Get it wrong and your remarketing audiences quietly shrink, your conversion tracking gets patchy, and your reports stop reflecting reality. Here's what Consent Mode v2 is, why it exists, and how to set it up properly.
Note: this article is practical guidance, not legal advice. Consent requirements depend on your specific setup and jurisdiction. Confirm your approach with a qualified data-protection professional before you rely on it.
What Consent Mode v2 actually is
Consent Mode is Google's way of adjusting how its tags behave based on whether a visitor has agreed to cookies. Rather than firing fully or not at all, Google's tags read the consent state and act accordingly. Version 2, enforced from 2024, added two new signals to the original pair:
- ad_storage: whether advertising cookies can be stored.
- analytics_storage: whether analytics cookies can be stored.
- ad_user_data: whether user data may be sent to Google for advertising.
- ad_personalization: whether that data may be used for personalized ads and remarketing.
Those last two are the v2 additions, and they're the reason a working v1 setup had to be updated. They tell Google not just whether a cookie can be set, but whether data may be used for advertising at all.
Why it's effectively mandatory for EU traffic
Google requires these signals for advertisers whose sites reach users in the EU and EEA. The practical enforcement is simple: without valid Consent Mode v2 signals, Google's audience and measurement features are restricted. Remarketing lists stop growing, conversion features are limited, and Google Analytics loses data on your European visitors. You don't get fined by Google. You just lose the functionality you're paying for. For any business advertising to European customers, that makes it a hard requirement in practice.
The legal backdrop matters too. Alongside Google's own rules, the GDPR requires genuine, granular consent before tracking, and consent management is one of the foundations of a compliant EU site. Consent Mode is how you make Google's tools respect the choice your visitor made.
Consent Mode does not replace your cookie banner
A common and costly misunderstanding: Consent Mode v2 does not collect consent. It only reacts to it. You still need a consent banner to ask the question and record the answer. Consent Mode simply relays that answer to Google's tags. In 2026 Google increasingly expects that banner to come from a certified consent management platform (CMP), so the signal it receives is trustworthy and properly logged.
The setup that breaks silently: a banner that looks fine but never passes the consent state into Consent Mode. Tags then default to the most restrictive behaviour, your data collapses, and nothing visibly errors. Always verify the banner is actually wired to the four consent signals. Don't assume that installing a CMP is enough on its own.
Basic vs advanced implementation
There are two ways to run Consent Mode, and the difference affects your data:
- Basic Consent Mode blocks Google tags entirely until the user consents. Simpler, but you lose all signal from people who decline.
- Advanced Consent Mode loads tags in a limited state before consent and sends anonymous, cookieless pings when a user declines. Google then uses modelling to fill some of the gap, so you keep more measurement while still respecting the "no."
Advanced generally preserves more useful data, which is why most advertisers prefer it, but it must be implemented carefully so the cookieless behaviour genuinely honours a declined choice.
How to set it up correctly
- Install a certified CMP and configure your banner with clear accept, reject and granular options.
- Connect the banner to Consent Mode so all four signals update the moment a visitor chooses.
- Choose basic or advanced deliberately, based on how much you rely on measurement and remarketing.
- Deploy via Google Tag Manager where possible, so consent logic sits in one place instead of scattered across tags.
- Test before trusting it. Use Tag Manager's preview and Google's diagnostics to confirm signals fire correctly for both accept and reject.
Consent Mode is closely tied to how your analytics is built, so it's worth getting both right together. Our guide to GA4 setup for small business covers the measurement side. And if you sell across borders, consent handling is part of the wider tracking picture in international SEO for European expansion. Treat consent as a permanent part of your measurement stack, not a one-off task: banners, CMPs and Google's own requirements keep evolving, so what passes today should be re-checked whenever you change tags, add a tool, or launch in a new market.
Not sure your tracking is compliant and complete? Neurova AI sets up consent, analytics and tags correctly as part of our SEO & marketing work, so your data holds up and your campaigns keep running. Book a call for a quick audit.
Frequently asked questions
What is Google Consent Mode v2? Consent Mode v2 is Google's framework for adjusting how its tags behave based on a visitor's cookie consent. It adds two signals, ad_user_data and ad_personalization, on top of the earlier analytics and ad-storage signals, so Google knows whether a user's data may be sent for advertising and personalization.
Is Consent Mode v2 mandatory for EU websites? If you use Google Ads or Google Analytics and serve users in the EU or EEA, Google requires Consent Mode v2 signals to keep using audience and measurement features. Without them, remarketing and conversion features are limited and your analytics loses EU/EEA data. It is effectively required to run Google advertising to European users.
Do I still need a cookie banner with Consent Mode v2? Yes. Consent Mode v2 does not collect consent; it reacts to it. You still need a consent banner, ideally from a certified consent management platform, to capture the user's choice. Consent Mode then relays that choice to Google's tags so they behave accordingly.