Consent Mode v2: Why GA4 Suddenly Shows Fewer Conversions and Where They Went

Revenue in the shop is steady, but GA4 has been showing noticeably fewer conversions for three or four weeks. Smart Bidding campaigns are swinging wildly, even though nothing changed about the product or the price. The first instinct is to look at marketing: swap creatives, shift budget.

In most cases the fault sits somewhere else, between the cookie banner and the tag setup. This article covers what Consent Mode v2 actually does, the wiring mistake behind most of these drops, how to diagnose it in 15 minutes, and how to fix it.

What is Consent Mode v2?

Consent Mode v2 is Google's mechanism for passing a visitor's consent status to Google tags. Since March 2024, it has been required in the EEA for Google Ads to populate remarketing lists and measure conversions in full.

Four signals drive this, across two generations:

• ad_storage: allows or blocks advertising cookies, from Consent Mode v1.
• analytics_storage: controls cookies for analytics tools like GA4, also from v1.
• ad_user_data: governs whether user data can be sent to Google for advertising purposes at all, new in v2.
• ad_personalization: governs whether that data can be used for personalized advertising and remarketing, new in v2.

The four flags get set either directly through a gtag consent command in your code, or through the Consent Overview in Google Tag Manager. For diagnosis purposes, remember this: without a granted status on all four signals, a Google tag stays in restricted mode, even when it technically fires.

Basic or Advanced: what your setup sends when someone declines

• Basic: no tag fires without consent. Clean, but every decline turns that visitor into a complete blind spot.
• Advanced: on decline, cookieless pings without an identifier still go to Google, and Google models conversions from them. The gap gets partly filled by calculation, not by real measurement.

Modeling needs data volume. Small accounts with a few hundred conversions a month still see the gap, because Google doesn't have enough data points for a reliable estimate. And the choice between Basic and Advanced is a privacy tradeoff, not a marketing call alone: your data protection officer needs to sign off on it.

The most common mistake: the banner and the tags aren't talking

The failure pattern is almost always the same. The banner shows up, the visitor clicks Accept, but the consent flags in the tag setup stay on denied. The cause sits in the wiring between the CMP and the Google tags: a missing or misconfigured CMP integration, a consent update event that never reaches Tag Manager, tags that fire before the default statement, or a default statement that's missing entirely.

A typical example: the team switches cookie banner vendors. The new CMP fires a different consent event than the old one, but the consent triggers set up in Google Tag Manager still listen for the old event signal. The banner itself looks unchanged, while in the background all four flags stay permanently on denied.

The result: the site measures permanently as if every visitor declined. Revenue stays flat, measurement collapses. That explains drops that line up exactly with a CMP switch, a relaunch, or a GTM rebuild. The drop starts on the deploy date, not on a market trend, and that's how you spot it.

The 15-minute diagnosis

1. Open the page with Tag Assistant in GTM preview mode: does a consent default statement fire on load, before any Google tag fires?
2. Click Accept on the banner: does a consent update event follow, and do all four signals switch to granted afterward?
3. Open DebugView in GA4: are events arriving with a consent status set?
4. Check the timeline: does the conversion drop land on a deploy, relaunch, or CMP switch date?
5. Cross-check against your shop numbers: backend orders against GA4 conversions, by week. The difference is the measurement gap, not lost revenue.

What server-side tracking fixes and what it doesn't

Server-side tracking stabilizes data transmission against ad blockers and browser restrictions, and extends cookie lifetimes. It doesn't replace consent. Without it, processing personal data is off the table, GDPR risk included. If your Consent Mode wiring is wrong, server-side tracking measures wrong too, just with more effort behind it. Technically, the tag server runs on its own subdomain and forwards events to Google through the Conversion API, which gets around browser-side blockers, not a missing consent signal. The order matters: fix the consent wiring first, then set up server-side.

More on the setup in Server-Side Tracking with the Conversion API: the guide. For where else tracking goes wrong, see 5 Reasons Your Tracking Misleads You.

Get the wiring checked

We check your banner, consent signals, and conversion measurement, and tell you where the gap sits and what the fix costs.

Book an intro call.

FAQ on Consent Mode v2

What's the difference between Consent Mode v1 and v2?

Consent Mode v2 adds two new signals, ad_user_data and ad_personalization, to the existing ad_storage and analytics_storage signals from v1. Since March 2024, v2 has been required in the EEA for Google Ads to fully populate remarketing lists and measure conversions.

Why does GA4 show fewer conversions than my shop's backend?

Three causes are likely: visitors declining tracking, ad blockers preventing tags from firing, or a wiring error between the banner and the tag setup. The difference between backend orders and GA4 conversions is a measurement gap, not lost revenue. If you can rule out all three causes and the gap is still there, Consent Mode is usually the reason, not a marketing problem.

Is Consent Mode v2 mandatory?

For Google's full advertising features in the EEA, it's mandatory in practice. It doesn't replace GDPR-compliant consent, though. The cookie banner, or CMP, is still required regardless of Consent Mode.

Does Google automatically fill in missing conversions?

Only in Advanced Consent Mode, and only with enough data volume. Small accounts with low traffic still see the gap in their reports, because Google doesn't have enough data points for a reliable model.

How we solve this in the account

Consent Mode v2 costs you conversions when the modelling has nothing to work with. We set it up together with server-side tracking whenever we take over an account as a Google ads agency or Meta ads agency.

The setup behind it is described in Server-side tracking with the Conversion API.