Starting 15 June 2026, Google simplifies how Consent Mode signals feed into Google Ads: ad_storage becomes the single controlling signal. Other consent signals - including Google Signals in GA4 - no longer independently supply behavioural data to Google Ads. Advertisers in the European Economic Area, UK, and any region with active consent requirements need to verify their implementation before the deadline.
This change is narrow but affects every advertiser using Google Ads with a consent management setup. Here is what changes, what breaks if ignored, and three steps to verify your configuration.
Background: Consent Mode v2 and the June 15 Update
Google introduced Consent Mode in 2020 and updated to version 2 in early 2024. The v2 update added ad_personalization and ad_user_data signals, and made the framework mandatory for advertisers targeting users in the EEA.
The UK operates under UK GDPR - which mirrors EU GDPR in most respects but is a separate framework following Brexit. UK advertisers serving UK users must comply with UK GDPR requirements for cookie consent, and Google's Consent Mode framework applies in the UK in the same way it applies in EEA countries.
The June 15 change is a further refinement: Google Ads now consolidates its signal reading to ad_storage exclusively. This streamlines the mechanism but removes the flexibility advertisers may have relied on - specifically, the ability for Google Signals in GA4 to supplement Ads data for users who accepted analytics but declined advertising cookies.
What Precisely Changes on 15 June
Before 15 June, Google Ads could draw data from:
ad_storage(primary signal)ad_personalization(audience building)- Google Signals in GA4 (cross-device behavioural data feeding Ads audience pools)
From 15 June, Google Ads uses only ad_storage.
Consequences:
ad_storage = 'denied'→ no conversion data flows to Google Ads for that user- Google Signals in GA4 no longer independently routes behavioural data to Ads
- Remarketing audiences that relied on the GA4 + Google Signals pathway will not grow from non-consenting users
Who Is Affected
High impact if you meet any of these:
- You run Google Ads targeting users in EEA countries, the United Kingdom, or regions with active consent requirements (Brazil LGPD, Canada PIPEDA)
- Your CMP maps consent categories such that users can accept analytics while declining advertising - a common configuration where
analytics_storage = 'granted'butad_storage = 'denied' - You have not reviewed your CMP configuration since implementing Consent Mode v2 in 2024
- You rely on remarketing audiences or smart bidding strategies
Lower impact if your campaigns exclusively target geographies without consent requirements and you have no active consent banner. In this case ad_storage defaults to granted and there is nothing to configure.
What Breaks Without Action
Conversion tracking gaps. Conversions from users with ad_storage = 'denied' stop being recorded. Consent Mode Modeling partially compensates this - but only when your signals fire correctly and you have sufficient consented conversion volume (700+ weekly conversions for reliable modelling).
Audience shrinkage. Remarketing lists stop growing for non-consenting users. Campaigns relying on "website visitors" or "past purchasers" audiences see eligible audience sizes decline.
Smart bidding degrades. Target CPA and Target ROAS need conversion data to calibrate bids. A data gap - especially for larger non-consenting user segments - means wider bid uncertainty and higher acquisition costs.
Silent failure. Google Ads does not alert you when Consent Mode signals are misconfigured. You see a gradual conversion count drop from 15 June, indistinguishable on the surface from a campaign performance decline.
Three Verification Steps Before 15 June
Step 1 - Inspect the Consent Tag in Google Tag Manager
Open GTM and find your Google Ads Conversion Tracking tag. In the tag's Consent Settings section, verify that ad_storage consent is required - not overridden.
Check your CMP integration settings. Confirm that the consent category labelled "Marketing," "Advertising," or "Third-party cookies" maps to ad_storage - not just analytics_storage. This distinction is where many configurations fail.
Step 2 - Verify Live Signals in Google Tag Assistant
Visit tagassistant.google.com, enter your site URL, and enter debug mode. Interact with your cookie banner - accept all cookies, then separately test declining non-essential cookies.
In the Consent State panel, you should see:
- Full acceptance →
ad_storage: granted - Decline/reject →
ad_storage: denied
If ad_storage does not respond to the consent interaction at all, your CMP is not sending the update call to GTM. If it fires denied regardless of user choice, the mapping between consent categories and signals is broken.
Step 3 - Check Conversion Tag Diagnostics in Google Ads
In Google Ads, navigate to Tools → Measurement → Conversions. Open each active conversion action and review the Tag Details tab.
The "Consent Mode signal coverage" metric shows what percentage of recent conversions had a valid ad_storage signal. Coverage below 60-70% indicates a configuration gap that needs addressing before 15 June.
Consent Mode Modelling - Limitations to Know
Consent Mode Modelling estimates conversions from non-consenting users using statistical patterns from consenting users. It is not a substitute for properly configured tracking - it is a supplement.
Modelling requirements:
- 700+ consented conversions per week (minimum for basic modelling accuracy)
- A consistent consent-to-refusal ratio
ad_storagemust correctly firedenied(not absent - the denied signal is what tells Google a user declined)
Without the denied signal, Google has no input for the model. Absence of signal is not the same as denied.
Fixing Common Issues
WordPress with CMP plugin (Cookiebot, Complianz, OneTrust): Review the plugin's GTM integration settings. Verify "Marketing" or "Advertising" consent category is mapped to ad_storage. Update the plugin - older versions may not fully support Consent Mode v2.
Manual GTM implementation: Review gtag('consent', 'update', {...}) calls. The update must fire after the user interaction on the consent banner. Verify trigger firing order in GTM: consent update tag should fire before conversion tags.
Headless or custom CMP: Ask your vendor specifically whether their solution updates ad_storage in response to user consent decisions per the June 2026 Google requirements.
Related reading
For context on how Google's recent algorithm changes interact with your broader site performance, see the analysis of who recovered after the May 2026 Core Update.
FAQ
Q: Does the June 15 change affect UK advertisers under UK GDPR? A: Yes. UK GDPR mirrors EU GDPR in consent requirements, and Google applies the same Consent Mode framework to UK-targeted advertising. UK advertisers running Google Ads to UK users should verify their ad_storage configuration in the same way as EEA advertisers.
Q: My site operates globally. Do I need a single Consent Mode setup for all regions? A: Consent Mode is implemented at the site/GTM level. The same configuration serves all users. The difference is that ad_storage defaults to granted for users in regions without active consent requirements - your configuration only actively affects users in regions where you display a consent banner.
Q: We use a consent banner but only for EU visitors. US visitors don't see it. Is that sufficient? A: For US visitors specifically, ad_storage defaults to granted since no banner fires, which means no action is needed for US-only conversion tracking. The verification is needed for the EEA/UK portion of your traffic.
Q: We implemented Consent Mode v2 in early 2024. Do we need to do anything else? A: Run the three-step verification above. The June 15 change specifically removes Google Signals as a supplementary data source for Google Ads. If your 2024 configuration assumed Google Signals would fill gaps, that assumption no longer holds after 15 June.
Q: What is the risk if we do nothing? A: If your ad_storage is correctly configured already, the risk is zero - the change is automatic. If ad_storage is misconfigured, conversion data gaps widen from 15 June. Smart bidding degrades, remarketing audiences shrink, and campaign performance data becomes unreliable. The impact is proportional to what percentage of your audience is in consent-required regions.
Summary
Two days remain before the change takes effect. The test is straightforward: open Google Tag Assistant, simulate your consent banner interaction, and confirm ad_storage changes between granted and denied correctly. If it does, no action is needed. If it does not, fix the CMP mapping before 15 June. The verification takes under ten minutes.