If your measurement stack still relies on Google Signals to keep advertising data flowing when consent is ambiguous, that dependency broke on June 15, 2026. Google updated its Analytics Data Controls, and the change is structural: Consent Mode’s ad_storage parameter is now the sole authority over whether Google Ads can collect cookies and user identifiers from your site.
The stakes are direct. Any site running conversion campaigns, maintaining remarketing audiences, or using GA4 as a data source for Google Ads is operating under different rules than it was two weeks ago, whether its team knows it or not.
Here is what changed. Before June 15, two settings had to permit tracking for the full advertising signal to flow. The Google Signals setting inside the GA4 admin, and ad_storage in Consent Mode, both needed to be on. If either blocked collection, Ads received a degraded signal. That two-key system is gone.
Google Signals now does exactly one thing: it controls whether Analytics associates behavioral data with signed-in Google user information, for reporting purposes inside GA4. It has no influence on what Google Ads collects or uses. The ad_storage parameter in Consent Mode handles that entirely, on its own.
If ad_storage is granted, full tracking is allowed. If ad_storage is denied, only anonymous pings are sent. Anonymous pings sharply limit conversion modeling, Smart Bidding signal quality, and remarketing audience refresh rates.
The failure mode that will quietly break measurement for many teams is this: sites running strict EU consent banners commonly deploy Consent Mode in a default-denied state, meaning ad_storage is denied until the user accepts. Some of those teams knew this and accepted the tradeoff, banking on Google Signals to provide some associative data as a partial backfill. That backfill path does not exist anymore. A default-denied ad_storage now starves remarketing and conversion data completely, with no secondary signal to soften the loss.
This is not hypothetical. Search Console and GA4 both show clean traffic numbers while the Ads measurement layer runs on degraded input, and the gap between reported sessions and attributable conversions widens silently. Teams discover this weeks later when Smart Bidding starts optimizing against noise.
The audit your measurement team should run this week is specific. Pull your Consent Mode implementation and check the default state of ad_storage before any user interaction. If it defaults to denied, identify what percentage of your sessions never upgrade to granted, because those sessions are now entirely invisible to Google Ads. Cross-reference that against your remarketing audience size in Google Ads over the past two weeks: a shrinking audience with stable GA4 traffic is a signal the change is already costing you reach. Then verify that your Consent Mode wiring actually passes the granted state correctly when users accept, because a misconfigured consent trigger can silently default-deny even users who opted in.
For teams outside the EU with no consent banner, this change may feel irrelevant. It is not. If Google Signals was ever used to diagnose gaps between GA4 and Ads attribution, those signals now mean something different. Signals data and Ads data are now reported through separate pipelines with no shared gate. Treating them as correlated can mislead attribution analysis.
The practical implication for the next ninety days is triage by campaign type. Remarketing campaigns are most exposed because their audience lists depend on identifier continuity. Performance Max campaigns that use GA4 audience signals are second. Conversion tracking via gtag or the GA4 linked conversion import is less affected if the conversion events themselves are firing correctly, but modeling quality still degrades when ad_storage is denied for a large share of sessions.
Review your Consent Mode implementation against Google’s updated documentation before your next campaign launch. The signal you thought you had may no longer exist.
Per Google’s Analytics Help documentation (“Updates to Google Analytics Data Controls,” support.google.com/analytics/answer/17016975), effective June 15, 2026.
