Under GDPR and PECR, non-essential tracking requires consent before it fires, not after. A meaningful share of European users decline, which historically meant those conversions simply vanished from reporting.
Consent Mode fills part of that gap. When consent is denied, tags send anonymous pings containing no identifiers, and Google uses those plus observed patterns from consenting users to model the missing conversions. Version 2, required for personalized advertising and remarketing to EEA users, adds parameters covering ad-user and ad-personalization consent specifically.
The important thing it doesn't do is make consent optional. It's a measurement recovery mechanism operating within consent requirements, not a way around them.
Why Google Consent Mode matters
Consent rejection doesn't just shrink your data. It skews it. People who decline tracking aren't a random sample. Optimizing campaigns against consented conversions alone systematically over-weights one segment, and most teams never realize their audience data has a hole shaped like their most privacy-conscious customers.
Implementation that actually works
A consent banner bolted onto an existing tag setup recovers nothing. Working implementations wire the consent management platform to fire before tags load, set default denied states, update on user choice, and send the v2 parameters. Verify in Google's tag diagnostics that modeled conversions are appearing, instead of assuming the banner did the job.
Common mistakes
Treating the banner as the implementation
The banner collects the choice. Consent Mode is what the tags do with it. Many sites have the first and not the second.
Banners that block the primary action
We have seen a consent overlay cover a checkout button and stop orders outright. Compliance is mandatory; blocking the page is a self-inflicted revenue problem.
Assuming UK and EU rules are identical
UK GDPR and EU GDPR are diverging post-Brexit. Companies serving both need to track both instead of assuming one policy covers it.
Not checking modeling is active
Modeling requires sufficient traffic volume and correct implementation. Below the threshold you get the consent restrictions without the recovery.
Where we work on this