What does Consent Mode v2 actually change for cookie banners?
Since March 2024, Google requires sites targeting the EEA to send two extra consent signals, ad_user_data and ad_personalization, alongside ad_storage and analytics_storage. The banner also has to offer a genuine reject option, not just an accept button. Without the new signals, Google's ad platforms lose measurement and remarketing data for your EEA traffic.
The two new parameters
ad_user_data covers consent to send user data to Google for advertising purposes. ad_personalization covers consent to personalized advertising. They ride on the same accept or reject choice as the existing storage parameters, so the visitor does not manage six toggles. Your banner collects one decision; your implementation translates it into all six signals.
Basic vs advanced implementation
Basic mode is all or nothing: Google tags stay blocked until the visitor consents, then load. Simple, but you lose every non-consented session from measurement. Advanced mode lets tags fire in a denied state and send cookieless pings, then upgrades to full measurement when consent is granted. Advanced preserves modeled conversions, but only if the consent state is wired correctly. A half-configured advanced setup is worse than basic, because it looks like it works while sending garbage.
What to check on your banner today
First, reject must be as easy as accept. A banner with a bright accept button and a reject link buried in a second layer fails the requirement and the spirit. Second, verify the consent state actually gates your tags: open a fresh profile, reject, and confirm in the network tab that ad and analytics requests carry denied signals. Third, confirm the two new parameters appear in the consent update call, not just the old four. Fourth, log every consent choice with a timestamp. When someone asks for proof, the log is the proof.
What breaks if you ignore it
In the EEA, missing signals mean no new audience building, no remarketing lists, and degraded conversion modeling. Your campaigns keep spending against thinner data. Separately, the DMA put consent requirements on large platforms with real enforcement behind them, and regulators have shown they will follow the trail down to the sites feeding those platforms. The fix is a day of work for most sites. The cost of skipping it compounds every week.
Frequently asked questions
What does Consent Mode v2 change for a cookie banner?
It adds more specific consent signals that the banner must collect and pass on, particularly around advertising data uses. The banner choices need to map to those signals accurately, not just store a general accept or reject.
Does Consent Mode replace the need for a banner?
No. Consent Mode communicates choices to tags. The banner is still how the visitor makes and changes those choices, and blocking and record keeping duties remain with your setup.
What should be checked after enabling Consent Mode v2?
That each banner choice produces the correct signal states, that tags behave accordingly before and after choices, and that records match the signals sent. Test reject and partial choices, not only accept all.