Consent Mode v2: Do You Need It in the CIS, or Is It Another Google Scare Story?

There's a lot of noise around Consent Mode v2 and very little understanding. Half the articles say "implement it now or get banned," the other half say "it's Europe-only, ignore it." The truth, as usual, sits in the middle, and it depends on where your traffic comes from.

Let's be straight about it. Consent Mode v2 is the mechanism Google uses to learn whether a user consented to cookies, and to adjust how tags behave. Four signals: two for advertising, two for analytics. No consent, and the tags run in a stripped-down mode.

Does this apply to you

If you have European traffic, then yes, it applies, and it isn't up for debate. Without consent mode Google simply stops collecting remarketing audiences and conversions across the EEA. That's no longer a "recommendation," it's a technical restriction.

If you're pure CIS without a single user from Europe, you can formally live without it. But I'd set it up anyway. First, European traffic shows up more often than you think (relocations, VPNs, business trips). Second, this isn't the kind of work you want to be rushing the day Google finally squeezes you.

Basic vs Advanced — and why almost everyone needs Advanced

Two modes. Basic blocks tags entirely until consent is given — no consent, no signals to Google at all. Advanced sends cookieless pings even without consent and then tops the data up with modeling.

For performance, Advanced is almost always better. The difference in recovered conversions can be several times over. Basic is simpler and "cleaner" from a privacy standpoint, but you pay for that with a hole in your data.

A contentious point: plenty of lawyers and privacy pedants will push Basic as the "safer" option. In data terms it's a loss. Decide by your own risk profile, but understand the price.

How to implement it without breaking your tags

Order is critical. First you set the consent default to denied — before any tags load. Then you connect the CMP (the consent banner). Then, once the user clicks "accept," the update command fires.

The main mistake is putting the default after the tags, or forgetting it entirely. Then tags fire before Google understands the consent state, and the whole setup goes sideways. The default has to be the very first thing that runs on the page.

Verification

Tag Assistant will show you the consent state on every tag. Look at it: before consent it should read denied, after the banner click, granted. If the state doesn't change, the CMP isn't wired to consent mode and the update never lands.

And don't chase perfection on the first pass. Consent mode is the kind of thing you configure, watch on real traffic for a couple of days, then tune. Almost nobody gets it right on the first attempt.