A case shared publicly on LinkedIn this week by Mike Teasdale, Founder and Planning Director at Harvest Digital, has brought renewed attention to a problem that may be affecting far more Google Ads accounts than the industry currently recognizes: the silent and permanent loss of conversion data caused by incomplete Consent Mode V2 implementation.
Teasdale described receiving a call last August from a client whose Google Ads conversions had dropped 90% overnight. The campaigns were active, clicks were arriving, but conversions had collapsed. Nothing in the account had changed - no paused campaigns, no budget edits, no structural modifications.
"We spent two days diagnosing it," Teasdale wrote in his LinkedIn post. "The answer was Consent Mode V2."
What happened in July 2025
The immediate cause was a policy enforcement that took effect in July 2025. Google began disabling personalization, remarketing, and conversion tracking functionality for advertisers who had not properly implemented Consent Mode V2 for UK and European Economic Area traffic. The enforcement applied to all UK and EEA traffic, not just users in specific countries.
According to Teasdale's account, the client had a consent banner in place. Visually, it appeared to be working. The problem was technical and invisible: the banner was collecting consent choices from users but was not passing those signals back to Google's tags. From Google's perspective, without a properly connected consent signal, there was effectively no consent at all - and so it treated the traffic as non-consented.
The result was an immediate and dramatic collapse in measured conversions. And crucially, the data from those non-compliant periods is permanently lost. There is no retroactive recovery mechanism.
Google's enforcement notification, shared publicly by digital marketing specialist Adriaan Dekker in July 2025, stated directly: "as a result of this ongoing non-compliance, we will now take action including disabling personalised and non-personalised ads, remarketing and conversion tracking functionality." No grace period was offered to affected accounts at the point of enforcement.
The technical failure: a disconnect between banner and tags
The distinction Teasdale draws is technically precise and practically important. A consent banner can be fully visible, legally compliant in its design, and accepted by users - and still fail to transmit the required signals to Google's measurement infrastructure.
Consent Mode V2 operates through specific parameters that must flow from the consent management platform to Google tags in real time. The framework introduced two key parameters when Google updated Consent Mode with two new parameters in December 2023: ad_user_data, which controls whether personal data is sent to Google for advertising purposes, and ad_personalization, which controls whether that data can be used for personalized advertising. Both parameters must be transmitted correctly and in sequence before Google's tags activate, or the system registers no consent.
When the banner is not properly connected to the Google tag layer - whether through Google Tag Manager, the global site tag, or another implementation - those parameters never reach Google. The tag has no consent signal to act on. Under the enforcement rules that took effect in July 2025, this is treated identically to a site with no consent banner at all.
A German court ruling delivered in March 2025 added further complexity to the technical picture. The Verwaltungsgericht Hannover determined that Google Tag Manager itself cannot operate before explicit user consent has been obtained. The court's technical testing found that Tag Manager transmitted user device data - including IP addresses - to US servers before any consent interaction occurred. That ruling has prompted some digital marketing teams to reconsider the sequencing of their tag management infrastructure entirely, loading consent management platforms independently from tag managers to ensure the correct order of operations.
Recovering from the damage: 40%, not 100%
Once Teasdale's team identified the root cause and corrected the consent signal connection, partial recovery was possible. According to his account, the fix allowed the client to recover roughly 40% of the attribution data that had been invisible during the non-compliant period. The remaining 60% is gone.
That 40% figure reflects an important technical feature of Consent Mode V2: behavioral modeling. When users decline advertising consent but permit analytics data collection, Google's machine learning systems attempt to reconstruct estimated conversion patterns using aggregate data from users who did consent. The modeling produces probabilistic estimates rather than individual-level measurements, and the accuracy degrades as the proportion of non-consented traffic increases.
Once the consent signals were restored, Google's algorithms could see conversions again. Automated bidding systems that rely on conversion data - such as Target CPA and Target ROAS - could resume optimizing. Cost per acquisition came back down. But the weeks or months of data from the non-compliant period remain absent from the historical record, and any bidding model trained on that period will have learned from incomplete information.
The broader pattern: numbers that looked like market weakness
What makes Teasdale's account particularly notable for the marketing community is the observation he makes about the diagnostic challenge. The performance decline was gradual and soft across the accounts he subsequently reviewed. Advertisers attributed it to market conditions. Seasonality. Competition. Economic headwinds. The actual cause - a data infrastructure failure invisible to standard reporting dashboards - looked like any other performance dip.
"Their numbers have been soft for months," Teasdale wrote. "They assume it's the market. It's their data infrastructure."
This matters because Google Ads bidding systems are directly dependent on conversion signal quality. When conversion data is missing or suppressed, Smart Bidding algorithms have less to work with. The system may adjust bids downward, reduce impression share, or shift budget toward better-attributed traffic sources - all of which amplifies the original measurement problem into a real performance problem.
Google introduced Tag Diagnostics integration into the Analytics consent settings hub in June 2025, specifically to address the detection gap. The diagnostic system monitors consent signal status across multiple dimensions, tracking ad_storage, ad_user_data, and ad_personalization parameters in real time. According to Google's specifications, the system maintains a 48 to 72-hour detection latency for consent signal updates - meaning problems can persist for up to three days before the diagnostic tools register them.
The hub also calculates the percentage of website traffic and conversions attributable to EEA-based users, giving operators a quantified view of how large the compliance gap actually is. For many sites, EEA traffic represents a substantial portion of total volume, making the stakes of a consent misconfiguration significantly higher.
A problem hiding behind apparent compliance
The case illustrates a gap between legal compliance and technical compliance. A consent banner that satisfies GDPR requirements from a user-facing perspective - providing clear choices, recording preferences, logging user decisions - may still fail to transmit those decisions to Google's ad infrastructure in the correct technical format.
Google launched the original Consent Mode framework to enable conversion measurement while respecting user consent choices for ad cookies. The system was initially available as a beta for European advertisers and has since expanded into a mandatory compliance framework. The EU consent policy enforcement strengthening in March 2024 created the first formal deadline, requiring advertisers to have Consent Mode V2 implemented by that date to retain personalization and audience features.
The July 2025 enforcement represented an escalation from that earlier policy phase. Rather than issuing further warnings, Google moved directly to disabling functionality for non-compliant accounts. There was no warning email sent to affected advertisers at the point of enforcement, according to Teasdale's account.
The specific technical failure he describes - a banner collecting consent without passing it to Google - is not hypothetical or unusual. It can occur when consent management platforms are not properly integrated with the Google tag layer, when CMP updates break an existing integration, or when sites migrate to new tag management setups without verifying that consent signal transmission continues correctly. It can also occur on sites that implemented consent banners in response to GDPR without specifically configuring them for Google's consent mode parameters.
Google's hidden data controls introduced in late 2025 add yet another layer of complexity. These controls allow advertisers to configure whether tags transmit limited advertising data or block all advertising data when consent is denied - configurations that operate independently from standard consent mode settings and require separate activation.
Industry-wide context
The enforcement described by Teasdale is not isolated to Google. Microsoft Clarity enforced its own cookie consent requirements across EEA, UK, and Swiss traffic from October 31, 2025, with similar consequences for non-compliant implementations. Without explicit consent signals, Clarity session recordings fragment, funnel analysis breaks down, and source attribution defaults to direct traffic.
The Consent Management Platform landscape has grown significantly in response to these enforcement trends, with Google maintaining a certified CMP partner program. Certified platforms include automated consent mode enablement, reducing the risk of the specific technical failure Teasdale describes - but only when properly installed and configured, and only when kept current with platform updates.
Google itself launched support for consent mode in its own Consent Management Platform in March 2025. The Google Tag Manager consent mode override setting, introduced in August 2024, allows administrators to set a default denied state for chosen regions directly within the Tag Manager interface - a simplified implementation pathway intended to reduce configuration errors.
Despite these tools, the pattern Teasdale describes persists across multiple clients. The gap between a visually operational consent banner and a technically functional consent signal integration is wide enough for large-scale data loss to go unnoticed for months.
Timeline
- September 2020: Google launches original Consent Mode as a beta for European advertisers
- December 2023: Google updates Consent Mode with two new parameters -
ad_user_dataandad_personalization- creating Consent Mode V2 - January 2024: Google announces enforcement deadline for EU User Consent Policy set for March 2024
- March 2024: Google strengthens EU user consent policy enforcement, restricting EEA audience data for non-compliant accounts
- August 2024: Google Tag Manager introduces consent mode override setting, allowing default denied state for chosen regions
- March 19, 2025: German court rules that Google Tag Manager requires user consent before activation
- June 2025: Google integrates Tag Diagnostics into Analytics consent settings hub with 48 to 72-hour detection latency
- July 21, 2025: Google begins disabling personalization, remarketing, and conversion tracking for non-compliant EU and UK advertisers
- August 2025 (Teasdale's client call): Google Ads conversions drop 90% overnight due to Consent Mode V2 misconfiguration; diagnosis takes two days
- October 31, 2025: Microsoft Clarity enforces cookie consent requirements across EEA, UK, and Switzerland
- April 9, 2026: Mike Teasdale publishes LinkedIn post describing the case and warning that the same silent data loss may be affecting many other accounts
Summary
Who: Mike Teasdale, Founder and Planning Director at Harvest Digital, described a client case - and warned that similar undiscovered problems likely affect many additional Google Ads accounts across the UK and EEA.
What: A Google Ads account experienced a 90% overnight drop in measured conversions caused by a Consent Mode V2 misconfiguration. The client's consent banner was collecting user preferences but not transmitting consent signals to Google's tag infrastructure. After diagnosis and remediation, approximately 40% of attribution data was recovered through behavioral modeling; the remainder was permanently lost.
When: The enforcement that caused the breakdown took effect on July 21, 2025. The client call occurred last August. Teasdale published his account on LinkedIn on April 9, 2026.
Where: The enforcement applies to all UK and European Economic Area traffic under Google's EU User Consent Policy, regardless of where the advertiser itself is based.
Why: Google's Consent Mode V2 requires active, correctly sequenced signal transmission from a consent management platform to Google's tags. A banner that appears compliant to users and regulators can still fail to pass the technical signals Google requires. When those signals are absent, Google treats the traffic as non-consented and disables conversion tracking, remarketing, and personalization - silently and with no grace period at the point of enforcement.