On June 15, 2026, Google changes how Consent Mode signals work for Google Ads: from that date, ad_storage becomes the only signal Google Ads reads to determine whether it can track conversions and build audiences. If your implementation is misconfigured, your conversion data stops flowing -- and you won't see it coming until your campaign performance data looks wrong.
This article explains what changes, what breaks if you ignore it, and the exact 3-step checklist to verify your setup before June 15.
What Is Consent Mode and Why June 15 Is a Hard Deadline
Google Consent Mode is a framework that lets websites communicate user consent choices to Google tags without passing identifiable data. When a user accepts or declines cookies, your Consent Management Platform (CMP) sends signals -- like ad_storage, analytics_storage, and ad_personalization -- to Google Tag Manager. Those signals tell Google tags what they're allowed to do.
Since March 2024, Consent Mode v2 has been required for advertisers targeting users in the European Economic Area (EEA). The framework added two new signals: ad_personalization and ad_user_data. Most advertisers updated their CMPs and considered the job done.
June 15, 2026 changes that assumption. Google is now standardizing which signal controls Google Ads data collection -- and the answer is only ad_storage.
What Exactly Changes on June 15, 2026
Before June 15, Google Ads could use several signals to determine consent status:
ad_storage: direct signal for ads trackingad_personalization: used for audience building- Google Signals in GA4: cross-device data that contributed to Ads audience pools
After June 15, Google Ads reads only ad_storage. The other signals no longer independently control what Google Ads receives.
This means:
- If
ad_storage = 'denied', Google Ads gets zero consent signal -- no conversion pings, no audience membership updates - If
ad_storage = 'granted', everything works as expected - Google Signals in GA4 no longer feeds behavioral data into Google Ads independently
The practical problem: many advertisers set up Consent Mode in 2024 and assumed Google Signals would cover gaps where users declined ad tracking but accepted analytics. That fallback is being removed.
Who Is at Risk
Not every Google Ads account is equally exposed. You are at risk if any of the following is true:
You're running ads in the EEA, UK, or Switzerland. These regions have the strictest GDPR-based consent requirements, and users in these markets frequently decline ad storage.
Your CMP maps consent to multiple signals but treats ad_storage as secondary. Some implementations grant analytics_storage broadly (for analytics purposes) while keeping ad_storage conditional on a specific cookie category. If users accept analytics but not advertising cookies, your ad_storage will be denied.
You rely on Google Signals for audience building. If your remarketing audiences are built through GA4 with Google Signals enabled, and those users have ad_storage = 'denied', those audiences will shrink after June 15 because Google Signals no longer supplements the Ads signal.
You haven't touched your CMP configuration since early 2024. Consent Mode v2 implementations from 2024 may not have been designed with the June 2026 change in mind.
What Breaks If You Don't Verify
If your ad_storage signal is improperly configured, here is what happens after June 15:
Conversion tracking gaps. Google Ads conversion actions that rely on the gtag or GTM tags stop recording conversions for users who have ad_storage = 'denied'. Even with Consent Mode modeling (which estimates conversions from consented users), gaps widen when the underlying signal is misconfigured.
Remarketing audience shrinkage. Audience lists built from website visitors stop growing for non-consenting users. Campaigns that target "website visitors" or "cart abandoners" see smaller eligible audiences.
Smart bidding degrades. Google's automated bidding strategies (Target CPA, Target ROAS) use conversion data to optimize bids. Fewer conversions in the data → worse bid optimization → higher costs per acquisition.
No immediate alert. Google Ads won't send you a notification saying "your consent mode is broken." You'll see a gradual drop in reported conversions starting June 15, which looks identical to a campaign performance drop.
3-Step Checklist: What to Verify Before June 15
Step 1 -- Check Your Current Consent Mode Implementation in GTM
Open Google Tag Manager and navigate to Tags. Find your Google Ads Conversion Tracking tag. In the tag settings, look for the Consent Settings section (or "Consent Checks" depending on GTM version).
Verify:
- The tag requires
ad_storageconsent (this should already be set in Consent Mode v2) - The tag is NOT configured to fire without consent override (unless you have a legitimate legal basis)
If you're using a CMP plugin (Cookiebot, OneTrust, Usercentrics, Complianz), go to its GTM integration settings and confirm that the ad_storage signal is mapped to your "Marketing" or "Advertising" consent category -- not just analytics.
Step 2 -- Verify the Signals Firing in Google Tag Assistant
Use the Google Tag Assistant (tagassistant.google.com) to simulate a session on your site:
- Open Tag Assistant and enter your website URL
- Navigate through a consent interaction (accept all / decline all)
- Look at the Consent State panel -- it shows the current values of
ad_storage,analytics_storage,ad_personalization, andad_user_data
The correct behavior:
- When user clicks "Accept All":
ad_storage = 'granted' - When user clicks "Decline" or "Reject Non-Essential":
ad_storage = 'denied'
If ad_storage = 'denied' even when user accepts advertising cookies, your CMP mapping is broken.
Step 3 -- Check Google Ads Conversion Tag Diagnostics
In your Google Ads account, go to Tools → Measurement → Conversions. Open each active conversion action and click the "Tag details" tab. Look for any warnings related to Consent Mode.
Google Ads now shows a "Consent Mode signal coverage" metric that shows what percentage of recent conversions had a valid ad_storage signal. If this is below 60-70%, your implementation has gaps.
How Consent Mode Modeling Works After June 15
Even for users who decline tracking, Google uses Consent Mode modeling to estimate conversions. This means Google fills in gaps using statistical modeling based on the aggregate behavior of consenting users on your site.
Consent Mode modeling requires:
- At least 700 consented conversions per week (for basic modeling)
- A consistent ratio of consenting to non-consenting users
ad_storageproperly reportingdenied(not broken)
Modeling doesn't work if ad_storage never fires at all. The signal needs to fire as denied to tell Google "this user declined" -- which is the input for the model. If the signal is absent, there's nothing to model.
What to Do If You Find a Problem
If Tag Assistant shows ad_storage not responding correctly to user consent choices, the fix depends on your setup:
If you use a CMP plugin for WordPress (Cookiebot, Complianz): Go to the plugin settings → Google Tag Manager integration → verify that "Advertising" or "Marketing" category is mapped to ad_storage. Some older plugin versions need to be updated.
If you implemented Consent Mode manually in GTM: Review your gtag('consent', 'update', {...}) calls. The update call should fire after the user makes a consent choice on your cookie banner, with ad_storage: 'granted' or ad_storage: 'denied' as appropriate.
If you use a custom CMP: Contact your CMP vendor and ask specifically: "Does your solution update ad_storage signal based on user consent choices, and is this compatible with the June 15, 2026 Google Ads changes?"
For advertisers in the USA where GDPR doesn't apply: if you're not showing consent banners to US users, your ad_storage defaults to granted and this change has no effect on your domestic traffic. However, if any of your campaigns target EEA users, the check is still necessary.
Internal resource
If your site was affected by Google's May 2026 Core Update alongside these tracking changes, see our analysis of who recovered after the May 2026 Core Update -- tracking data reliability directly affects how accurately you can measure recovery.
FAQ
Q: Does the June 15 Google Consent Mode change apply to websites in the USA? A: If your website only serves US users and doesn't run ads targeting EEA visitors, the change has minimal impact -- US users don't typically see consent banners, so ad_storage defaults to granted. However, if any campaign geo-targets Europe, you need to verify your setup.
Q: Will Google Ads stop working entirely if my ad_storage signal is broken? A: No, your ads will still show and get clicks. What breaks is the downstream measurement: conversion tracking becomes unreliable, audiences built from website visitors shrink, and smart bidding has less data to optimize bids. The visible symptom is a drop in reported conversions starting June 15.
Q: I implemented Consent Mode v2 in 2024. Do I need to do anything again? A: Possibly. The June 15 change specifically affects how Google Signals in GA4 feeds data to Google Ads. If your implementation relied on Google Signals as a fallback for users who accepted analytics but not advertising cookies, that fallback is removed. Run the 3-step checklist above to confirm your ad_storage signal is mapped correctly.
Q: What is "Consent Mode modeling" and does it replace real conversion data? A: Consent Mode modeling is Google's statistical estimation of conversions that happened from non-consenting users. It supplements -- but doesn't replace -- real conversion data. Modeling requires a minimum volume of consented conversions to work accurately. For smaller accounts with fewer than 700 conversions per week, modeling is less reliable.
Q: How do I know if my Google Ads account is currently showing estimated vs real conversions? A: In Google Ads, go to Campaigns → Columns → Modify Columns. Add the "Conversions (modeling)" column. If you see significant volume there compared to regular "Conversions," a large share of your conversion data is already modeled. After June 15, this share may increase if ad_storage is misconfigured.
Bottom Line
June 15 is two days away. The change is narrow but consequential: ad_storage is now the only gate Google Ads uses. Run Tag Assistant on your site today, check the Consent State panel, and confirm the signal fires correctly for both accept and decline scenarios. Five minutes of verification now saves weeks of debugging degraded conversion data later.
