June 15, 2026 passed without much fanfare in most marketing teams. No announcement email, no urgent dashboard alert. But for every advertiser running Google Ads with a linked Analytics account, something important changed — and whether it affected your data depends entirely on how your consent setup was configured.

Google restructured how advertising data flows between Analytics and Ads. The result: ad_storage is now the sole parameter that determines what ad data gets collected and passed to your Ads account. The GA4 Google Signals setting — which millions of accounts had been relying on, often without realising it — was stripped of any authority over advertising data.

Did Jun 15 break your tracking?Before Jun 15GA4 Signals quietly recovered denied-consent conversions.After Jun 15ad_storage denied = the conversion isn't recorded.Audit consent + tracking before it skews your bids
What Google's June 15 consent change broke

What actually changed

Before June 15, two things jointly determined whether Google Ads received advertising cookies and user IDs from your site: the Google Signals setting inside GA4, and the ad_storage parameter in Consent Mode. Both had to permit tracking for the full signal to flow.

After June 15, that model ended. ad_storage in Consent Mode became the sole control. Google Signals no longer acts as a backstop or a secondary check — it simply doesn't touch advertising data anymore.

In isolation, that sounds tidy. In practice, it removed a safety net that privacy and legal teams had quietly relied on for years. If a CMP misconfiguration occurred — or if a business had used Signals as an intentional secondary layer of control — that protection is now gone. The only gate left is ad_storage.

What breaks silently

The accounts most affected are those that either haven't completed Consent Mode v2 implementation or were relying on Google Signals as a fallback.

  • Conversion cookies stop firing. When ad_storage is denied or misconfigured, Google Ads tags enter a stripped-down state: no advertising cookies, no _gcl_au conversion cookie, no proper conversion signal. The campaign keeps spending. The reporting keeps populating. But the data behind it is incomplete.
  • Remarketing lists shrink. Lists that previously drew from Signals data are now built only from users who explicitly granted ad_storage. In markets with meaningful consent decline rates, list sizes may have already dropped noticeably since mid-June.
  • Smart Bidding trains on a biased sample. Smart Bidding learns from conversion signals. When those signals degrade quietly — not in a single visible drop, but in a slow erosion — bidding strategies start optimising toward an incomplete picture of your actual converters. Campaigns don't break. They just get gradually less efficient in ways that are easy to attribute to seasonality or competition rather than a tracking problem upstream.

None of these failures announce themselves. There is nothing in the Ads interface that flags “your consent mode is misfiring.” Without actively checking the underlying signal health, there is nothing to indicate a problem until performance starts to drift.

Three things to audit right now

If you haven't checked your setup since June 15, three areas deserve immediate attention.

Confirm your CMP is sending the right signals. Use Google's Tag Assistant or the Consent Mode report in GA4 to verify that consenting users are sending ad_storage: granted and non-consenting users are sending ad_storage: denied. Don't assume the implementation set up in 2024 is still firing correctly after platform updates on both ends.

Check your conversion tag health. If _gcl_au is absent from sessions where it should be present, or if you're seeing a jump in modelled versus observed conversions, ad_storage is likely being denied more broadly than intended.

Look at remarketing audience size trends. A decline in list size since mid-June is the clearest signal that Signals data has dropped out of the pool and your ad_storage consent rate is lower than assumed. Compare 30-day audience sizes against your pre-June-15 baseline.

What we found for one client

For one of our clients in a regulated sector, a tracking audit ahead of a seasonal campaign revealed that their consent setup had a misconfigured condition silently denying ad_storage to roughly 30% of EU visitors — visitors who had, in fact, consented. The conversion data flowing to Google Ads was significantly thinner than it should have been, and Smart Bidding was undervaluing that traffic segment as a result. The fix was a CMP configuration change, not a campaign change — but the campaign was the thing that had been blamed.

Find your gaps before they cost you

AdAudit Pro audits your Google and Meta accounts for exactly these kinds of structural gaps — conversion tracking health, audience configuration, and data signal issues that don't surface in standard campaign reporting.

If you haven't verified your consent mode and conversion setup since June 15, request a free audit from the AdAudit Pro page.