What exactly changes on June 15 2026 in Google Consent Mode for GA4 and Google Ads?

On June 15 2026 Google transitions Consent Mode so that ad_storage becomes the single parameter that determines what advertising data flows from Google Analytics 4 into Google Ads. Before the change, GA4's Google Signals setting operated as a separate switch that could grant Google Ads access to GA4 audience and conversion data even when ad_storage was set to denied. From June 15 the Google Signals setting no longer overrides Consent Mode — ad_storage becomes the authoritative control. The practical consequence is significant. Advertisers who relied on Google Signals to push GA4 audiences into Google Ads while operating Consent Mode in a privacy-strict configuration will lose that data flow. Audience sizes will shrink, remarketing capability will decline, and conversion modeling will operate on a smaller signal layer. Advertisers operating under Consent Mode in a permissive configuration will see broadly stable data flow but should expect tighter alignment between consent state and downstream data movement. The change also clarifies several edge cases that previously produced inconsistent behavior. When ad_storage is denied at page load and the user does not subsequently grant consent, no advertising cookies are set and no advertising identifiers are passed to Google Ads. When ad_storage is denied and the user later grants consent, retroactive measurement applies only to events after the consent moment — events before consent remain modeled. When ad_storage is granted at page load, the full advertising data flow operates including remarketing audience membership, conversion tracking with user identifiers, and cross-device attribution. The unified control simplifies the mental model but tightens the data scope when consent is denied. The change does not affect the analytics_storage parameter which continues to control GA4's analytics data collection independently. Sites that operate analytics_storage granted with ad_storage denied — a common configuration for sites with EEA traffic and a Google Ads relationship — will see GA4 analytics continue but Google Ads measurement degrade. For automated audit of consent configuration across analytics and advertising tags, see AI Compliance Audit and the broader Consent Mode V2 framework in Google Consent Mode V2 Implementation Guide .

Why is Google making this change now and what does it mean for the EU User Consent Policy?

Google has signaled the June 15 change as part of its ongoing alignment with the EU User Consent Policy and broader European privacy enforcement direction. The EU UCP requires advertisers to collect end-user consent for use of personal data and to communicate that consent to Google through Consent Mode signals when serving European Economic Area, United Kingdom, and Switzerland traffic. The previous configuration in which Google Signals could override Consent Mode produced inconsistencies that European Data Protection Authorities had flagged as compliance gaps. The Irish DPC investigation into Google's analytics-to-advertising data flow that opened in mid-2025 was a contributing pressure. The DPC's preliminary findings identified that GA4-to-Google-Ads data pathways under the Google Signals setting did not consistently respect user consent decisions captured through Consent Mode at the publisher level. The June 15 change resolves much of the gap by making Consent Mode the authoritative control. The CJEU's evolving case law on legitimate interests as a lawful basis for advertising-related data processing also contributed. The Court has progressively narrowed legitimate interests as a basis for personalised advertising, particularly in the C-621/22 IAB Europe decision and subsequent national interpretations. Google has shifted toward explicit consent as the primary lawful basis for the EEA, and the June 15 change aligns the operational data flow with the consent-first lawful basis position. For advertisers the strategic implication is that the EU UCP is now genuinely binding on Google's downstream data systems. Non-compliance with EU UCP — operating personalised advertising in the EEA without collecting valid consent and signaling it through Consent Mode — produces operational consequences including suspended personalisation, restricted audience access, and limited remarketing functionality. Earlier UCP enforcement was primarily through Google Ads policy violations and account suspensions. The June 15 change makes UCP compliance enforceable through the data flow itself rather than only through policy enforcement. Advertisers should treat Consent Mode v2 implementation as mandatory rather than recommended for any EEA traffic. The change also positions Google for further enforcement coordination with European supervisory authorities. The Belgian DPA's investigation into IAB Europe's TCF and subsequent enforcement decisions demonstrated that supervisory authorities can dictate technical requirements for advertising ecosystems. Google's voluntary tightening of Consent Mode reduces the likelihood of imposed technical requirements from supervisory authorities. For consolidated EU advertising compliance framework, see EU DSA Compliance .

What does the technical migration plan look like for a sophisticated EEA advertiser?

The technical migration plan for an EEA advertiser should follow a five-stage sequence beginning at least eight weeks before the June 15 effective date and continuing through a post-change stabilisation window. Stage one is current state audit. Document the current Consent Mode v2 implementation including the CMP vendor and version, the Google tag (gtag.js or Google Tag Manager) configuration, the default consent state, the consent update mechanism, and the data flow from GA4 to Google Ads. Verify whether Google Signals is currently enabled in GA4 and whether consent is being respected at the GA4 collection layer. Many sites operate Google Signals enabled by default without realising that the setting overrides Consent Mode for ads data; the audit identifies these gaps. Stage two is consent layer validation. Test the CMP behavior against Consent Mode v2 requirements including default-denied configuration for EEA traffic, the consent update flow on user opt-in, the consent string format passed to Google, and the persistent consent state across pageviews and sessions. The validation should cover desktop and mobile experiences, both first-time visits and return visits, and the interaction with Google Privacy Sandbox APIs where applicable. CMP vendors have been issuing Consent Mode v2 updates throughout 2025 and 2026 — sites running older vendor versions should upgrade before June 15. Stage three is GA4 configuration adjustment. Update GA4 settings to align with the June 15 framework including verifying Google Signals state (continuing to operate but no longer overriding Consent Mode for ad data), enabling Consent Mode integration at the property level, and configuring data retention to align with the consent-first model. Conversion definitions should be reviewed for compatibility with modeled conversion reporting and enhanced conversions for leads should be configured if relevant. Stage four is Google Ads tag and conversion linker validation. Verify that Google Ads tags on landing pages are receiving the correct consent signals and that conversion linker tags are operating with consent-aware behavior. Enhanced conversions for web should be configured to maximise the value of consented data. Conversion tracking validation should test that conversions are accurately recorded in granted-consent scenarios and that modeled conversions appear in denied-consent scenarios. Stage five is post-change monitoring. Monitor key metrics in the 6-8 weeks after June 15 including audience size by source, conversion volume and modeled share, cost per acquisition trends, return on ad spend, and any anomalies in campaign delivery. Compare against pre-change baselines and identify whether any deviations exceed normal variance. The monitoring should inform whether additional remediation is needed for specific campaign types or audience segments. For comprehensive Consent Mode v2 implementation framework that supports the migration, see the Consent Mode V2 Implementation Guide .

How does the change interact with IAB TCF, server-side tagging, and the broader ad-tech ecosystem?

The June 15 change interacts with the broader ad-tech ecosystem in several specific ways that advertisers should understand. The IAB Transparency and Consent Framework operates alongside Consent Mode but at a different layer. TCF captures consent decisions in a structured string format that propagates through the supply chain including demand-side platforms, supply-side platforms, ad exchanges, and individual ad-tech vendors. Consent Mode captures the same consent decisions but signals them specifically to Google's measurement and advertising systems. The two frameworks are not redundant — TCF supports the broader supply chain while Consent Mode supports Google's first-party measurement flows. After June 15 the alignment between TCF and Consent Mode signals becomes more important because Consent Mode's authoritative role over Google data flow means that a mismatch between TCF and Consent Mode signals would produce inconsistent supply chain behavior. CMP vendors are updating their integrations to ensure that consent decisions captured in the CMP UI propagate correctly to both TCF and Consent Mode in synchronised form. Server-side tagging through Google Tag Manager Server interacts with the June 15 change because server-side measurement can still operate when client-side ad_storage is denied. The server-side flow uses the conversion API to send conversion data to Google Ads, with consent signals communicated through the conversion API's consent fields. Server-side tagging does not bypass Consent Mode — the consent signals still apply — but it provides a more reliable measurement channel when client-side cookies and identifiers are unavailable. Sites with sophisticated measurement requirements should consider server-side tagging implementation alongside the Consent Mode migration. Enhanced Conversions for Web and Enhanced Conversions for Leads operate on hashed first-party data and continue to work after June 15 with consent. The enhanced conversion flow benefits from the June 15 change because the consent-aware data flow ensures that the hashed identifiers are only used when consent supports their use. Advertisers running Enhanced Conversions should verify their consent integration in advance of June 15 to ensure that the hashed data flow respects the unified Consent Mode control. The cross-domain measurement flow including subdomain tracking and cross-site Google Ads conversion attribution interacts with Consent Mode through the linker mechanism. The June 15 change does not alter linker behavior but the consent-aware flow may produce different cross-domain conversion attribution patterns than the pre-change flow. Multi-property advertisers should validate cross-domain measurement after the change. For broader EU ad-tech compliance context, see the EDPB Pay-or-Consent Cookie Walls May 2026 guide and EU DSA Compliance .

What is the expected impact on Performance Max, Demand Gen, and Smart Bidding campaign types?

Performance Max, Demand Gen, and Smart Bidding campaign types are the most data-hungry campaign formats in Google Ads and are correspondingly the most affected by the June 15 Consent Mode change. Performance Max relies on AI-driven audience optimization across YouTube, Display, Search, Shopping, Gmail, and Discover surfaces. The optimization is heavily dependent on conversion signals and audience signals from connected first-party data sources including GA4. After June 15 the audience signals available to Performance Max will reflect only consented users in EEA traffic. The optimization continues to operate but the model has less direct signal to learn from. Advertisers should expect a recalibration period of 4-6 weeks during which performance may show variance compared to pre-change baseline. After recalibration the optimization should stabilise at the new signal layer, with conversion modeling compensating for direct signal gaps. Demand Gen campaigns operate similarly but with greater dependence on YouTube and Shorts surface optimization. The audience signals from GA4 that feed Demand Gen will reflect the consented user pool only. For EEA advertisers running Demand Gen the audience size reductions and signal density reductions may be more pronounced than for non-EEA campaigns because Demand Gen audience definitions tend to be broader and more reliant on diverse signal types. Smart Bidding strategies including Target CPA, Target ROAS, Maximize Conversions, and Maximize Conversion Value will see bid optimization recalibration after June 15. The bidding algorithms operate on conversion patterns and the conversion patterns will shift toward modeled conversions for the unconsented share. The bidding models adapt to this through ongoing learning but may take 2-4 weeks to converge against the new flow. Advertisers should avoid major bidding strategy changes immediately before or after June 15. Advertisers who use offline conversion imports for in-store, phone, or longer-cycle conversions may see relatively less impact because offline conversion data does not rely on Consent Mode in the same way. Maintaining or expanding offline conversion imports is a partial hedge against client-side measurement reductions. The connected first-party data sources including customer match lists and Customer Data Platform integrations continue to operate after June 15 with consent-aware handling. Advertisers building first-party data programs through CDP and customer match are well-positioned to navigate the change because they have direct first-party data assets that supplement third-party measurement gaps. The strategic conclusion is that the June 15 change accelerates the shift toward first-party data strategies, server-side measurement, and consented audience programs. Advertisers with mature first-party data infrastructure will see relatively muted change effects. Advertisers heavily dependent on Google Signals for unconsented audience inference will see the largest change effects and should accelerate their first-party data investments. For broader advertiser preparation, run AI Compliance Audit and reference the Google Ads Policy Guide .

Google Consent Mode June 2026: GA4-Ads ad

Google Consent Mode June 15 2026 GA4-Ads Split: ad_storage As Single Control, Migration Playbook & GDPR Implications

What Changes on June 15

On June 15 2026, Google transitions Consent Mode so that the ad_storage parameter becomes the single authoritative control over what advertising data flows from Google Analytics 4 into Google Ads. The previous configuration in which GA4's Google Signals setting could grant Google Ads access to GA4 audience and conversion data — even when ad_storage was set to denied — ends on that date.

The change is the most consequential adjustment to Google's measurement-and-advertising data architecture since the Consent Mode v2 rollout in 2024. For European Economic Area, United Kingdom, and Switzerland advertisers, the data flow becomes consent-first in operational reality rather than only in policy. Advertisers who relied on Google Signals to push GA4 audiences into Google Ads while operating Consent Mode in a privacy-strict configuration will lose that data flow.

For advertisers operating Consent Mode in a permissive default-granted configuration, the change is largely invisible because ad_storage already permitted the data flow. For advertisers with denied-default Consent Mode and Google Signals enabled — a common configuration designed to balance compliance against measurement — the change produces material reductions in audience size, signal density, and direct conversion measurement.

"After June 15 2026, if ad_storage is granted, Google Ads may use the permitted ad-related signals regardless of the Google Signals setting in GA4. When ad_storage is denied, advertising-related storage such as cookies and similar identifiers is restricted."
— Google Ads Help, Consent Mode update notice, May 2026

For consolidated Consent Mode v2 implementation context, see the Consent Mode V2 Implementation Guide and the broader Google Ads Policy Guide.

Why Google Is Making This Change

The June 15 change has three principal drivers — regulatory pressure from European supervisory authorities, evolving CJEU case law on legitimate interests as a lawful basis, and Google's own operational priorities for advertiser ecosystem credibility.

Regulatory Pressure

The Irish DPC investigation into Google's analytics-to-advertising data flow opened in mid-2025 with preliminary findings identifying gaps between user consent decisions and downstream data movement. The investigation focused on the Google Signals override pattern that could permit advertising data flow when client-side consent indicated denial. The June 15 change resolves much of the gap by making Consent Mode authoritative.

CJEU Case Law Evolution

The Court of Justice of the EU has progressively narrowed legitimate interests as a lawful basis for personalised advertising. The C-621/22 IAB Europe decision in 2024 and subsequent national supervisory authority interpretations established that explicit consent is the safer lawful basis for advertising-related data processing. Google's voluntary tightening reduces the risk of imposed technical requirements from supervisory authorities.

Operational Alignment

Google's broader ad ecosystem trajectory points toward consent-first measurement and first-party data programs. The June 15 change accelerates that trajectory for advertisers who have not yet shifted their measurement architecture. The change creates operational pressure to invest in Enhanced Conversions, customer match, server-side tagging, and Customer Data Platform integration.

For consolidated EU regulatory framework, see EU DSA Compliance.

Inside the Data Flow Split

The architectural change is best understood as a separation of analytics data flow from advertising data flow. Prior to June 15 the two flows could coexist in shared configurations through Google Signals. From June 15 they operate under independent controls.

Before and After

Scenario	Before June 15	After June 15
`ad_storage` granted + Google Signals on	Full ad data to Google Ads	Full ad data to Google Ads
`ad_storage` denied + Google Signals on	Partial ad data through Signals	No direct ad data, modeled only
`ad_storage` granted + Google Signals off	Limited ad data	Full ad data to Google Ads
`ad_storage` denied + Google Signals off	No ad data	No direct ad data, modeled only

Implications by Consent State

Granted ad_storage: Full advertising data flow operates including remarketing audience membership, conversion tracking with user identifiers, and cross-device attribution.
Denied ad_storage: No advertising cookies are set, no advertising identifiers are passed to Google Ads, and Conversion Modeling fills measurement gaps using aggregated patterns.
Mid-session grant: Retroactive measurement applies only to events after the consent moment. Events before consent remain modeled.
Mid-session denial: Existing identifiers are not retroactively deleted but no new advertising-related collection occurs after denial.

Analytics_storage Independence

The analytics_storage parameter continues to control GA4's analytics data collection independently of ad_storage. Sites operating analytics_storage granted with ad_storage denied — a common EEA configuration — will see GA4 analytics continue but Google Ads measurement degrade. The split between the two parameters allows publishers to maintain audience analytics while restricting advertising-related data flow.

For automated audit of consent tag configurations, run AI Compliance Audit.

Impact on Audiences, Conversions, Attribution

The June 15 change produces measurable effects across audience sizes, conversion measurement, attribution distribution, and downstream campaign optimization. The magnitude varies based on pre-change configuration and EEA traffic share.

Audience Size Effects

Remarketing audiences built from GA4 data — Google Signals audiences in particular — will see size reductions corresponding to the unconsented traffic share. For EEA-heavy advertisers the reduction may reach 20-40 percent of pre-change audience size depending on consent rate baseline. Lookalike audiences derived from GA4 seed audiences will reflect the smaller seed size, which propagates through Optimized Targeting in Performance Max and Demand Gen.

Conversion Measurement Effects

Direct conversions: Count drops proportionally to the unconsented share that previously was captured through Google Signals.
Modeled conversions: Share of total reported conversions rises as Conversion Modeling fills the gap.
Total reported conversions: Should remain close to pre-change levels because modeling compensates, but precision per individual conversion may decline.

Attribution Distribution

Data-driven attribution models will draw from a smaller direct measurement pool. The model continues to assign credit across touchpoints but with greater reliance on probabilistic inference. Reporting will continue to show last-click, time-decay, and data-driven attribution distributions, but expect modest shifts in the relative credit assigned across channels with different consent rates.

Frequency Capping

Frequency capping for remarketing operates on identifier pools that shrink after June 15. The smaller pools may produce frequency variance for individual users across devices and sessions because cross-device matching is constrained by the available identifiers.

For supplementary measurement reviews, see the Legal Compliance Scan and the AI Compliance Audit.

Five-Stage Migration Plan

Sophisticated EEA advertisers should execute migration in a five-stage sequence beginning at least eight weeks before June 15.

Stage 1 — Current State Audit

Document Consent Mode v2 configuration: CMP vendor and version, default consent state, consent update mechanism.
Verify Google Signals state: Identify whether currently enabled and whether overriding Consent Mode.
Map data flow: GA4 to Google Ads pathways, including Audience builder and Conversion Linker.

Stage 2 — Consent Layer Validation

Test CMP behavior: Default-denied for EEA traffic, update flow on opt-in, persistent state across sessions.
Verify consent string propagation: CMP-to-Google tag handoff, TCF + Consent Mode synchronisation.
Upgrade CMP version: Vendors with older Consent Mode v2 integrations should be brought current.

Stage 3 — GA4 Configuration Adjustment

Verify Google Signals state: Continues to operate but no longer overrides Consent Mode for ad data.
Enable Consent Mode integration: Property-level activation in GA4 admin.
Configure data retention: Align with consent-first model.

Stage 4 — Google Ads Tag and Conversion Linker Validation

Verify tags receive correct consent signals: Test with consent granted, denied, and updated mid-session scenarios.
Configure Enhanced Conversions for Web: Maximise the value of consented data.
Validate conversion linker: Consent-aware behavior across granted and denied scenarios.

Stage 5 — Post-Change Monitoring

6-8 week monitoring window: Audience size by source, conversion volume and modeled share, CPA trends, ROAS, delivery anomalies.
Baseline comparison: Identify whether deviations exceed normal variance.
Remediation triggers: Specific campaign types or audience segments needing additional configuration.

For comprehensive implementation framework, see the Consent Mode V2 Implementation Guide.

TCF, Server-Side, Performance Max

The June 15 change interacts with the broader ad-tech ecosystem in several specific ways.

IAB TCF Alignment

TCF captures consent decisions in a structured string format that propagates through the supply chain. Consent Mode signals the same consent decisions to Google's measurement and advertising systems. After June 15 the alignment between TCF and Consent Mode signals becomes more important — a mismatch between signals produces inconsistent supply chain behavior. CMP vendors are updating integrations to ensure synchronised propagation. For the EDPB guidance interacting with TCF, see the EDPB Pay-or-Consent guidance.

Server-Side Tagging

Server-side measurement through Google Tag Manager Server can still operate when client-side ad_storage is denied — but consent signals still apply through the conversion API's consent fields. Server-side tagging does not bypass Consent Mode; it provides a more reliable measurement channel within the consent envelope. Sites with sophisticated measurement requirements should consider server-side tagging implementation alongside the Consent Mode migration.

Performance Max, Demand Gen, Smart Bidding

Campaign type	Pre-change dependency	Post-change expectation
Performance Max	Heavy GA4 audience signal use	4-6 week recalibration, then stabilised at new signal layer
Demand Gen	YouTube + Shorts optimization on broad signals	Audience density reductions, conversion modeling compensation
Smart Bidding (tCPA, tROAS)	Direct conversion measurement	2-4 week bidding convergence period
Standard Search	Last-click attribution	Minimal impact, modeled conversions in reporting
Display Remarketing	Audience list memberships	20-40% size reduction for EEA-heavy lists

First-Party Data Acceleration

The June 15 change accelerates the shift toward first-party data strategies including Customer Match, Enhanced Conversions for Leads, Customer Data Platform integration, and offline conversion imports. Advertisers with mature first-party data infrastructure will see relatively muted change effects.

For broader compliance audit, run AI Compliance Audit.

June 15 Readiness Checklist

[ ] Current state audit completed at least 8 weeks before June 15
[ ] CMP vendor and version verified as Consent Mode v2 compliant
[ ] Default-denied configuration confirmed for EEA, UK, Switzerland traffic
[ ] Google Signals state documented and override pattern identified
[ ] TCF and Consent Mode signal synchronisation verified
[ ] Enhanced Conversions for Web configured to maximise consented data
[ ] Customer Match list cadence increased ahead of the change
[ ] Offline conversion import pathways validated as a measurement hedge
[ ] Server-side tagging assessed for advertisers with sophisticated measurement needs
[ ] Post-change monitoring plan defined for 6-8 week window
[ ] No major campaign structural changes scheduled June 1 to July 15
[ ] No major bidding strategy changes scheduled June 1 to July 15
[ ] Stakeholder communication plan executed for performance variance expectations
[ ] EU UCP compliance reaffirmed across all EEA-serving accounts
[ ] Account-level Consent Mode misconfigurations identified and remediated

Don't miss the next policy change.

Subscribe to the Policy Tracker — get weekly digests or instant Pro alerts across all 8 platforms. Or try our free Keyword Risk Checker first.

Subscribe Free

Report Keywords — Run AI Compliance Audit

#Google Ads#Consent Mode V2#GA4#ad_storage#GDPR#EU UCP#Conversion Modeling#Remarketing#EEA#2026 Policy#Advertisers#Compliance Guide 2026

Share This Report

Tweet Share

DSA Article 22 Trusted Flagger Q2 2026: Designations, Notice Velocity, Platform Response SLA & Advertiser Implications

Article 22 Trusted Flagger designations are reshaping platform takedown velocity across the EU. The framework requires platforms to prioritise notices from designated flaggers — with material implications for advertiser content removal risk.

EU AI Act Article 50 Ad Creative Disclosure May 2026: Deployer Obligations, Watermarking & August 2 Enforcement

Article 50 of the EU AI Act enters force on August 2 2026. Brands deploying AI-generated ad creative must disclose synthesis and preserve machine-readable watermarks or face fines up to €15M.

April 2026 Platform Enforcement Digest: 30-Day Recap Across Eight VLOPs and Sector Implications

April 2026 saw sustained enforcement volume across the eight social-media VLOPs with category share shifts that signal upcoming policy direction. Meta and TikTok lead absolute volume; LinkedIn shows category concentration; Pinterest enforcement framework is the strictest. The 30-day recap and sector implications.

Google Consent Mode June 15 2026 GA4-Ads Split: ad_storage As Single Control, Migration Playbook & GDPR Implications