Google Ads numbers dropped in June? Check ad_storage.
On June 15, 2026, Google changed which consent setting decides whether GA4 data can be used in Google Ads. Nothing changed on your site, but for some sites, conversions and audiences in Google Ads got smaller anyway.
The short answer
Since June 15, 2026, the ad_storage consent setting alone decides whether advertising data flows from GA4 into Google Ads. Before that, Google Signals played a part too. If your consent banner leaves ad_storage denied when it should be granted, or never updates it after a visitor accepts, Google Ads now sees less. Check what your banner sends before and after a visitor makes a choice.
On this page
What changed on June 15
Consent Mode is how your cookie banner tells Google's tags what a visitor agreed to. It uses a few settings. ad_storage covers advertising cookies and identifiers. analytics_storage covers analytics.
Before June 15, the Google Signals setting in GA4 and ad_storage together controlled what advertising data reached Google Ads. Now ad_storage controls it alone. Google Signals still matters, but only for GA4's own reporting, such as cross-device journeys and demographics.
ad_storage.| What it controls | Before June 15, 2026 | Since June 15, 2026 |
|---|---|---|
| Advertising data from GA4 into Google Ads | Google Signals and ad_storage together | ad_storage only |
| GA4 reporting with signed-in user data | Google Signals | Google Signals |
| Standard GA4 analytics collection | analytics_storage | analytics_storage |
| Enhanced conversions and remarketing | ad_user_data and ad_personalization | Unchanged |
Who is likely to notice
The sites most likely to see a difference:
- Sites with visitors in the EU and UK, where the banner rightly starts with advertising denied. Fewer people accepting now means less data in Google Ads.
- Sites whose banner starts denied for everyone, including visitors in places that don't require it. US visitors may be getting the strictest setting by mistake.
- Sites where the banner never updates the setting. The visitor clicks Accept, but
ad_storagestays denied because the banner and the tags aren't connected properly.
Sites with no Consent Mode at all usually won't see a drop, because Google's tags then assume advertising storage is allowed. That's a different problem if you have visitors from places that require consent.
What it looks like in your numbers
The signs show up in Google Ads, not in your store or CRM:
- Conversions imported from GA4 fall from mid-June while orders or leads hold steady.
- Remarketing audiences built in GA4 get smaller.
- Smart Bidding has less to work with, so performance can soften without a clear cause.
The useful comparison is the gap, not the totals. Put weekly orders or leads next to Google Ads conversions for the months before and after June 15. If the gap widened in the week of June 15 and stayed wider, consent is the first place to look.
How to check your setup
- Load your site fresh in Google Tag Assistant and look at the consent state before you touch the banner. Note what
ad_storagestarts as. - Accept all cookies and check that
ad_storagechanges to granted straight away, before your advertising tags fire. - Reject all cookies in a new session and check that it stays denied.
- Check the location rules. If your banner treats regions differently, test as a visitor from each one you care about. US visitors shouldn't get EU defaults unless you chose that.
- Check Google Signals separately. Decide whether you still want it for GA4 reporting, and write that decision down.
What this isn't
This isn't a reason to set ad_storage to granted for everyone. Where consent is required, the drop is the honest number. The fix is a banner and tags that pass along the choices visitors actually make. Which regions require consent, and what your banner should say, are decisions for your organization and its counsel. I handle the technical setup and testing.
Google has said more changes are coming later in 2026, including moving GA4's ads personalization settings under the ad_personalization consent setting. It's worth checking your setup again when that happens.
