Does Google Consent Mode v2 Replace Adblock Recovery?
We keep seeing the same question from marketing teams after they roll out Consent Mode v2: "Does this mean we don't need to worry about adblockers anymore?" It's an understandable assumption. But it's wrong, and the confusion is costing people real data.
1. The Misconception
When Google mandated Consent Mode v2 for EEA advertisers in early 2024, the headline feature was modeled conversions — Google's ML fills in estimated conversion data for users who declined consent. For teams that had been stressing about GDPR-related data gaps, this felt like a lifeline.
So teams shipped their CMP integrations, set up the new consent signals, and moved on — assuming the data gap problem was handled. It wasn't. Modeled conversions only cover users who hit your consent banner and said no. They do nothing for users who never let your analytics scripts load in the first place.
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
At its core, Consent Mode v2 is a signaling protocol. Your CMP listens to what the user chooses on the cookie banner, then passes that choice to Google's tags via 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.
When someone declines consent, the GA4 and Google Ads tags still fire — but instead of sending a full event with user identifiers, they send a stripped-down "cookieless ping." Google collects these pings and uses aggregate patterns from consenting users to model what conversions probably happened in the non-consenting group.
Notice what this requires: the tags have to execute. The entire mechanism depends on the GA4 script loading, running, and sending something — even if that something is just a minimal ping. An adblock prevents the script from loading at all. No script, no ping, no data, nothing for Google's models to use.
3. What Adblockers Actually Do
Whether it's uBlock Origin, Brave's built-in Shields, or Firefox Enhanced Tracking Protection, the mechanism is the same: a list of blocked domains, checked against every outgoing network request. googletagmanager.com is on that list. So is google-analytics.com. The browser checks the request URL, finds a match, and drops it before it ever leaves the device.
For that visitor:
- ✕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
Whether this person would have clicked "Accept all" is irrelevant. Consent never entered into it — the script was blocked before your banner even had a chance to appear. That visitor doesn't exist in GA4, doesn't exist in Google Ads, and Google has no signal to model from.
4. Why They Operate at Different Layers
Your analytics data can disappear at three different points, and each one needs a different 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
Consent Mode v2 sits at layer two. Adblock recovery sits at layer one. Patching layer two tells you nothing about what's missing at layer one.
5. The Combination Problem
Real visitors don't fit neatly into one box. Someone can have an adblock installed and still click "Accept all" on your banner. Someone can decline consent and have no adblock at all. There are really four groups 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 |
Consent Mode handles row 2. Rows 3 and 4 are yours to deal with separately — and without adblock recovery, you're not dealing with them at all. Row 3 is particularly annoying: these visitors consented, they were happy to be tracked, and you still lost them because the script never loaded.
6. What You Actually Need
Short version: if you have EU visitors, you need both. But they're solving genuinely separate problems:
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 25–40% of users 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
They don't step on each other, which is worth knowing upfront. Adblock recovery reroutes blocked signals through your first-party domain, but it doesn't touch consent logic — your GA4 and Google Ads tags still handle consent signals exactly as they normally would. If a user denied consent and has an adblock, their recovered signal goes out with the denied-consent flags intact. You're fixing the transport, not rewriting the rules.
Set up Consent Mode v2 through your CMP for compliance. Add adblock recovery to plug the network-layer hole. Done.
Summary
Consent Mode v2 is good at what it does. It handles the legal side of the data gap — giving you a compliant way to estimate conversions from users who opted out. But it was never designed to deal with adblockers, and it can't. That's a network problem, not a consent problem.
25–40% of your visitors are running something that blocks your analytics at the request level. Consent Mode doesn't see them. Your reports don't see them. Adblock recovery is the only thing that closes that gap.
Close the Network-Layer Gap
Consent Mode v2 covers users who denied consent. Introtrace covers users whose analytics were blocked regardless of consent. One script tag, free to start.
Start FreeFrequently Asked Questions
Does Google Consent Mode v2 recover data blocked by adblockers?
No. Consent Mode's modeled conversions rely on a cookieless ping that fires when a user declines consent. If an adblock is active, the script never loads — so there's no ping, and nothing for the model to work from. The two problems don't overlap.
Do I need both Consent Mode v2 and adblock recovery?
Yes. Consent Mode is a compliance requirement if you're running Google Ads in the EEA. Adblock recovery is a data quality fix. One handles what you're legally allowed to collect; the other handles what actually reaches your analytics.
Does adblock recovery conflict with Consent Mode or GDPR?
No — and this is a common concern worth addressing directly. Adblock recovery only changes how the signal is transported (via your first-party domain instead of Google's). The consent flags set by your CMP are preserved and forwarded as-is. A user who denied consent gets their denial respected; you just get slightly more of the data you were already allowed to collect.
Does Consent Mode v2 modeled data include adblocked users?
It can't. Modeling requires some observable signal — even a minimal ping. Adblocked users generate zero signal. They're not in the modeled data, not in the reported data, not anywhere. That's the gap adblock recovery exists to fill.
What percentage of my analytics gap comes from adblockers vs consent denials?
Depends heavily on your audience. Globally, adblockers account for roughly 25–40% of visitors. In EEA markets, consent denial rates can run anywhere from 20–60% depending on how your banner is designed. The populations do overlap — some users have both an adblock and deny consent. For a tech-focused site with European traffic, it's not unusual to be missing more than half your sessions between the two.