Consent Mode v2: Why Your Google Ads Conversions Are Being Throttled (UK Guide)
If your reported Google Ads conversions dropped without your campaigns changing, Consent Mode v2 is the most likely culprit. Since it became mandatory for businesses serving UK and EEA users, cookie-consent choices now directly gate how much conversion data Google receives. Set up wrong, it quietly starves your account of data. Set up right, Google models the gap back. This guide explains how to get it right.
What is Consent Mode v2?
Consent Mode v2 is Google’s framework that adjusts how its tags behave based on whether a visitor accepts or rejects cookies. Instead of simply firing or not firing, your tags send anonymous consent signals to Google, which then models the conversions it can no longer observe directly.
It introduced two new parameters — ad_user_data and ad_personalization — on top of the original analytics and ad-storage signals. For any business advertising to UK or EEA users, these signals are now required for Google Ads remarketing and full conversion measurement.
Why is it throttling my conversions?
When a user rejects cookies and Consent Mode isn’t configured for modelling, the conversion simply never reaches Google — so your reported numbers fall even though the sales still happened. With consent rates often 50–70% in the UK, that can mean a third or more of your conversions vanishing from the platform.
Google’s Smart Bidding optimises against the data it can see. Feed it 60% of your conversions and it bids as if the other 40% never converted — so it under-bids on exactly the audiences that do convert. The damage isn’t just reporting; it’s wasted spend.
How do you set up Consent Mode v2 properly?
Pair a Google-certified consent management platform (CMP) with Consent Mode v2 in basic or advanced mode, then verify the consent signals are actually reaching Google. Advanced mode plus server-side tagging recovers the most data because Google can model declined-consent conversions.
The reliable setup is: certified CMP → Consent Mode v2 in advanced mode → server-side tracking with first-party enrichment. This combination lets Google model the conversions it can’t directly measure, which is why accounts on advanced mode typically report meaningfully more conversions than those left on basic.
Is Consent Mode v2 a way around GDPR?
No. Consent Mode v2 changes how Google responds to consent choices — it does not remove the need for valid consent. Used properly it is more privacy-respecting than old-style tags, because it stops sending identifiers when a user declines.
This is the same principle as server-side tracking: it changes how data flows, not whether you need permission. You still need a compliant CMP and a lawful basis.
Frequently asked questions
Yes. GA4 uses the same consent signals and applies behavioural modelling for users who decline cookies, provided you have enough traffic and Consent Mode is configured correctly. Without it, GA4 simply loses that data.
It varies by consent rate and traffic, but accounts moving from no/basic consent handling to advanced mode with server-side tagging commonly see reported conversions rise materially — the conversions were always happening, Google just couldn’t see them.
Not strictly, but advanced mode combined with server-side tagging recovers the most data. Client-side advanced mode helps; the server-side combination is what closes most of the gap.
We set up Consent Mode v2 with a certified CMP and server-side tagging — so Google models the conversions cookie rejections would otherwise hide. No pitch: we'll check your current setup and tell you what it's costing you.
Get Consent Mode v2 done right →