Consent Mode v2 is Google’s framework for adjusting how its tags (Analytics, Ads) behave based on a visitor’s consent choice, using two additional signals — ad_user_data and ad_personalization — on top of the original analytics_storage and ad_storage parameters, and it has been effectively required for advertising and remarketing features in the EEA since March 2024.
Consent Mode v1 covered whether analytics and advertising storage (cookies) could be used. Version 2 adds ad_user_data, controlling whether user data can be sent to Google for advertising purposes, and ad_personalization, controlling whether that data can be used for personalised advertising. Both need to be wired to your actual consent banner categories.
Google Ads features like remarketing and conversion modelling for EEA traffic depend on Consent Mode v2 being correctly implemented; without it, those features degrade or stop working, independent of the legal question. This is a case where compliance and functionality point the same direction.
Default consent state set to denied before any tag fires, signals updated the moment a visitor makes a choice, and the whole thing tested to confirm behaviour actually changes on decline, not just on the surface. See GA4 and consent mode for how we implement and verify this specifically.
No, it is a technical implementation that adjusts how tags behave based on a visitor’s consent choice; it supports GDPR-based advertising but does not itself constitute compliance. Broader GDPR compliance is a legal question for your data protection officer. See GDPR and consent for how the two fit together.
Less urgently, but Google Analytics 4 still benefits from correctly configured consent mode, since it lets GA4 use modelled conversions to estimate behaviour from visitors who decline tracking cookies rather than losing that data entirely. Without it, analytics reporting can understate real traffic and conversion volume.
By testing directly whether declining consent stops the relevant tags from firing, rather than assuming the configuration is correct because it was set up once. Browser developer tools or a tag debugging tool can confirm this in a few minutes and should be checked again after any tag manager change.
The technical mechanism works the same everywhere, but what counts as valid consent and which categories require an opt-in can vary by national implementation of the ePrivacy rules. Your data protection officer should confirm country-specific requirements, particularly for a multi-affiliate site serving several EU markets from one build.
Tell us what you have and we will tell you whether it is actually gating data collection correctly.