Google's Consent Enforcement Silently Ate Nine Months of EU Conversion Data
Mike Teasdale, a Google Ads consultant, shared a case on LinkedIn last week that should make every advertiser running EU traffic uncomfortable. A client called him in August 2025 because their numbers were "soft." They figured it was the market. It wasn't.
Conversions had dropped 90% overnight. Campaigns were still running. Clicks arrived normally. The consent banner was live and collecting user preferences just fine. Everything looked right from the outside.
The problem turned out to be almost comically specific: the banner was collecting consent choices but not actually transmitting those signals to Google's tags. When Google's Consent Mode V2 enforcement went live on July 21, 2025, this account's conversion tracking, remarketing, and demographic reporting quietly stopped working. Took two days to even diagnose. After fixing the implementation, roughly 40% of the attribution data was recoverable through behavioral modeling. The other 60% is just gone.
That was nine months ago. And based on what I'm seeing across industry coverage and practitioner communities, a lot of accounts are still running with this exact problem.
Having a banner is not the same as being compliant
This is the part that keeps tripping people up. Most advertisers did what they were told to do. They installed a consent management platform. They deployed a cookie banner. Users click accept or reject. Box checked.
Except it isn't.
Consent Mode V2 requires four specific parameters to flow from your CMP to Google's tags based on the user's consent choice: ad_storage, ad_user_data, ad_personalization, and analytics_storage. The two newer parameters, ad_user_data and ad_personalization, were added in December 2023. Google gave advertisers until March 2024 to implement them, then started enforcing in earnest last July.
Think of it like installing a smoke detector that isn't wired to the building's alarm system. It beeps in the room. Nobody at the front desk hears anything. Your CMP collects the user's consent choice. Google's tags never receive the signal.
If those parameters don't reach Google's tags, or if the integration between your CMP and Google Tag Manager is misconfigured (common with manual setups), Google treats 100% of your EEA and UK traffic as non-consented.
The notification Google sent to affected advertisers was characteristically blunt: "We have reviewed your account and found that the attached site(s)/app(s) do not comply with Google's EU User Consent Policy... we will now take action including disabling personalised and non-personalised ads, remarketing and conversion tracking functionality."
Personalized and non-personalized. Remarketing and conversion tracking. They turned off basically everything.
What a 90% conversion drop looks like when nothing else breaks
The frustrating part about this failure mode is how it presents. Your campaigns don't pause. Ads keep serving. Clicks still show up in the interface. Spend looks normal.
But conversions drop to near-zero for all EEA and UK traffic. And because Google Tag Diagnostics has a 48-72 hour detection latency, the decline looks gradual in your dashboards. It doesn't set off the kind of alarms a campaign error would. It just looks like the market got worse. Or seasonality. Or increased competition.
Teasdale's summary is the line that stuck with me:
"Their numbers have been soft for months. They assume it's the market. It's their data infrastructure."
If your EEA conversion rate took a hit sometime between July and October 2025 and you chalked it up to market conditions, probably worth checking whether you have a consent signal problem instead.
Google's modeling safety net has a minimum occupancy requirement
One recovery mechanism that comes up often in this context: Google's behavioral modeling, which reconstructs conversion data from patterns in consented-user traffic. It exists. It works. But it has activation thresholds that most mid-size accounts don't meet.
You need 1,000+ daily events from users who denied cookies for seven consecutive days, AND 1,000+ daily events from users who granted consent over the same window. Both conditions. Seven straight days.
Large e-commerce sites with heavy EU traffic will clear that bar. A mid-size B2B account or a smaller DTC brand pulling a few hundred daily European visitors probably won't. And if you don't hit the minimums, you don't get partial modeling. You get zero.
That surprised me, honestly. I assumed modeling was more of a sliding scale, where smaller accounts would get rougher estimates and bigger accounts would get more refined ones. It's more of a cliff. Below the threshold you're flying completely blind on your EU conversion data.
A quick audit before you do anything else today
If you're running any Google Ads traffic to EEA or UK users, I'd do this before lunch:
- Open Google Tag Assistant (tagassistant.google.com) and load your site
- Look for the consent state initialization. You should see
ad_storage,ad_user_data,ad_personalization, andanalytics_storagesignals firing with either "granted" or "denied" values - If any of those four parameters are missing, your CMP is not communicating with Google's tags correctly
- Verify your CMP is on Google's certified partner list (search "Google CMP partner list" for the current directory). If it's not certified, the consent signals won't be accepted even if they're technically transmitting
The most common failure point, based on what practitioners have been reporting: the CMP is installed and working correctly for collecting preferences, but the integration with Google Tag Manager is broken or incomplete. Banner shows up. User clicks accept. The consent signal never reaches the Google tag. Everyone on both sides thinks everything is fine.
The recovery math depends on how much plumbing you're willing to redo
Implementing Advanced Consent Mode (where tags load immediately but adjust behavior based on consent state, sending cookieless pings when consent is denied) plus automatic Enhanced Conversions recovers roughly 10-20% of lost attribution. Free. Fastest option.
Adding manual Enhanced Conversions pushes recovery to 20-30%. More configuration work, no additional cost.
Full server-side tagging, where consent signals and conversion data route through your own server before reaching Google, recovers 30-50%. Expensive, requires developer time, but gives you the most control over what data flows where.
None of these fix the past. Data from non-compliant months is permanently gone. Google didn't store signals you never sent. If you've been non-compliant since last July, that's nine months of EU conversion data that no implementation change will bring back. Nine months of Smart Bidding making optimization decisions on incomplete information.
The compounding cost of letting this sit through Q2
This problem is expanding, not shrinking. Microsoft Clarity enforced similar consent requirements across EEA, UK, and Switzerland in October 2025. Multiple U.S. state privacy laws take effect through 2026 and 2027. The consent infrastructure Google built for Europe will almost certainly become the global default within the next 18 months.
I'd estimate that by the end of this year, at least 40% of all paid search accounts globally will need consent mode implementations that currently don't exist. That number isn't a prediction about regulation. It's a prediction about platform enforcement. Google and Microsoft are making these signals mandatory regardless of what your local privacy law technically requires.
The advertisers who sorted their consent plumbing out last summer have nine months of clean EU data feeding their bidding algorithms right now. The ones who didn't have nine months of progressively worse optimization decisions compounding on top of each other.
On paper, this is a compliance problem. In practice, it's a performance problem that disguises itself as a market problem. And the longer it sits unfixed, the harder it becomes to separate the signal damage from everything else going on in your account.
By Notice Me Senpai Editorial