Does Google Consent Mode v2 Replace Adblock Recovery?
Consent Mode v2 and adblock recovery solve completely different problems. One handles what you're allowed to track. The other handles what you're able to track.
1. The Misconception
Consent Mode v2 became mandatory for EEA advertisers in early 2024, and modeled conversions were the headline feature: Google's machine learning fills in estimated conversion data for users who declined consent. Teams who'd been losing sleep over GDPR-related data gaps understandably treated it as a fix.
CMP integrations got shipped, consent signals got wired up, and most teams moved on assuming the gap was closed. It wasn't. Modeled conversions only cover people who reached your banner and clicked no. Anyone whose analytics scripts never loaded in the first place gets nothing from this mechanism.
The core confusion
Consent Mode addresses data gaps caused by user choice — people who said no to tracking. Adblock recovery addresses data gaps caused by technical blocking — requests that never left the browser. Different users, different mechanisms, different fix.
2. What Consent Mode v2 Actually Does
Strip away the marketing and it's a signaling protocol. The CMP reads what a user picked on the cookie banner and passes that choice along to Google's tags through four parameters:
ad_user_dataWhether the user consents to their data being used for Google advertising purposes.
ad_personalizationWhether the user consents to personalised advertising (remarketing).
analytics_storageWhether GA4 can set and read analytics cookies for this user.
ad_storageWhether Google Ads can set and read advertising cookies.
Decline consent and the GA4 and Google Ads tags still fire, just stripped down — a "cookieless ping" instead of a full event with identifiers attached. Google pools those pings with aggregate patterns from consenting users and models what conversions probably happened among everyone who said no.
The tags have to execute for any of this to work. The whole mechanism assumes the GA4 script loaded, ran, and sent something — even a minimal ping counts. An adblock stops the script before it loads at all, and that's the whole chain broken: no script, no ping, nothing for the model to use.
3. What Adblockers Actually Do
uBlock Origin, Brave's built-in Shields, Firefox Enhanced Tracking Protection — different tools, same mechanism underneath. A list of blocked domains gets checked against every outgoing request. googletagmanager.com is on it. So is google-analytics.com. Match found, request dropped, and it never leaves the device.
What that visitor actually generates:
- ✕The GA4 script (gtag.js / gtm.js) never downloads
- ✕No GA4 events fire — not even a cookieless ping
- ✕Google receives zero signal from this visitor
- ✕There is nothing to model from
It doesn't matter whether this person would have clicked "Accept all." Consent was never in the picture — the script got blocked before your banner had a chance to render. This visitor is invisible to GA4, invisible to Google Ads, and there's no signal left for anything to model.
4. Why They Operate at Different Layers
There are three separate points where analytics data can vanish, and none of them share a fix:
Network layer
Problem
Adblock blocks the request — script never loads
Solution
First-party proxy (adblock recovery)
Consent layer
Problem
User denies consent — personal data cannot be collected
Solution
Consent Mode v2 (modeled conversions)
Attribution layer
Problem
Safari ITP / cookie expiry — cross-session identity lost
Solution
Server-side first-party cookies
Layer two is where Consent Mode v2 operates. Layer one is where adblock recovery does. Fixing one tells you nothing about the other.
5. The Combination Problem
People rarely sort into one clean box. Plenty of visitors run an adblock and still click "Accept all." Plenty decline consent with no adblock in sight. Combine the two variables and you get four groups actually landing on your site:
| Visitor type | Consent | Adblock | Data received |
|---|---|---|---|
| Standard visitor | Accepted | None | Full signal |
| Privacy-conscious | Denied | None | Cookieless ping → modelled by Consent Mode |
| Adblock user | Accepted | Active | Blocked — zero signal |
| Both | Denied | Active | Blocked — zero signal |
Row 2 is Consent Mode's job. Rows 3 and 4 are on you, and without adblock recovery you're simply not handling them. Row 3 stings the most: these people said yes, they were fine being tracked, and you lost them anyway because the script never made it to the page.
6. What You Actually Need
Short version: EU traffic means you need both, and they're not competing for the same job:
Consent Mode v2
Why: Legal compliance — required for EEA advertisers using Google Ads and GA4 to maintain measurement and remarketing capabilities under GDPR.
Covers: Users who declined consent on your banner
Does not cover: Users whose analytics requests were blocked at the network level
Adblock recovery
Why: Data completeness — recovers analytics signals from the roughly 29.5% of users globally (32.5% in the US) whose browsers block GA4, GTM, and other tracking scripts before they execute.
Covers: Users with browser extensions (uBlock Origin, AdBlock Plus) and browser-native blocking (Brave, Firefox ETP)
Does not cover: Consent preferences — does not affect what data you're legally allowed to collect
Neither steps on the other's territory. Adblock recovery reroutes a blocked signal through your first-party domain and leaves consent logic untouched — your GA4 and Google Ads tags keep handling consent signals exactly as before. Deny consent and run an adblock, and the recovered signal still carries the denied-consent flags. It's a transport fix, not a rules change.
Configure Consent Mode v2 through your CMP because compliance requires it. Add adblock recovery because it plugs a hole Consent Mode was never built to touch.
Summary
Consent Mode v2 does its actual job well — a compliant way to estimate conversions from users who opted out. Adblockers were just never part of its design brief, and no amount of tuning changes that. That gap sits at the network layer, not the consent layer.
29.5% of your visitors globally (32.5% in the US) run something that blocks the request itself. Consent Mode can't see them. Your reports can't either. Adblock recovery is the only piece that closes that particular gap.
Close the Network-Layer Gap
Consent Mode v2 covers users who said no. Introtrace covers the ones whose analytics got blocked no matter what they chose. One script tag, free to start.
Start FreeFrequently Asked Questions
Does Google Consent Mode v2 recover data blocked by adblockers?
It can't reach them. Modeled conversions rely on a cookieless ping firing when a user declines consent, and an active adblock stops the script before it can send anything at all — no ping, nothing for the model to work with.
Do I need both Consent Mode v2 and adblock recovery?
If you're running Google Ads in the EEA, Consent Mode is a compliance requirement, full stop. Adblock recovery is a separate, optional fix for data quality. One governs what you're legally allowed to collect; the other governs what actually shows up in your analytics.
Does adblock recovery conflict with Consent Mode or GDPR?
No — it only changes transport, routing the signal through your first-party domain instead of Google's. Whatever your CMP already decided about consent gets forwarded untouched. A visitor who denied consent still has that denial honored; you just recover a bit more of the data you were already entitled to collect.
Does Consent Mode v2 modeled data include adblocked users?
There's nothing to include. Modeling needs at least some observable signal, even a minimal ping, and adblocked users produce none. They're absent from the modeled numbers and the reported numbers alike — which is precisely the hole adblock recovery is built to fill.
What percentage of my analytics gap comes from adblockers vs consent denials?
It varies a lot by audience. Adblockers account for around 29.5% of visitors globally, 32.5% in the US (Backlinko). Consent denial rates in EEA markets swing anywhere from 20–60% depending on how the banner's worded. The two groups overlap too — some visitors both block and decline. Tech-heavy sites with European traffic can easily be missing over half their sessions once you add both up.