Consent Mode is Google's framework where the choices people make in your cookie banner adjust how your Google tags behave, passing the consent state so tags fire fully, in a limited way, or not at all.
You run a cookie banner because you have to, and you assume that once a visitor clicks reject your tracking simply stops. Consent Mode is the layer that decides what stops actually means. Instead of blocking tags outright, it sends signals to Google about whether that person agreed to analytics storage and ad storage, and your tags read those signals before they decide how much they are allowed to do.
When someone consents, your tags behave normally and record the click, the conversion, and the audience membership. When someone refuses, the tags still fire but in a stripped-down way that sends no identifiers and drops no cookies. That is the whole point of the design: you keep a compliant signal flowing rather than a silent hole in your data. The version that matters now is Consent Mode v2, and in the European Economic Area and the UK it is required if you want ad personalization and measurement to keep working with Google's advertising products at all.
Watch this closely. Without a correct Consent Mode v2 setup on your European traffic, you lose remarketing and measurement there, and Google fills part of the gap with modeled conversions. Those modeled numbers are estimates built from patterns, not counted events, so treat that portion of your reporting as an informed guess rather than a receipt.
Get consent signals wired correctly and you keep measuring Europe; skip it and you are bidding on a fog of estimates.
Sources
- Consent Mode v2 is required in the EEA and UK for Google ad personalization and measurement, with modeled conversions filling consent gaps. support.google.com · verified 9th August 2026
Last checked 9th August 2026. Next check 15th August 2026.
