Google Signals Lost Ad Data Control on June 15

On June 15, 2026, Google removed Google Signals as a control over advertising cookies that flow from Analytics into linked Ads accounts. The only remaining switch is Consent Mode’s ad_storage parameter. Sites that had flipped Signals off as a privacy brake lost that brake the same day.

The change did not delete Google Signals, and accounts that already kept it on did not get a new Ads data path. The reckoning sits with the other group: properties that treated an admin toggle as a GDPR firewall, and banners that never actually set the signal Google now obeys.

Google Split Ads Data From the Signals Toggle

Google’s own Help Center framed the move as housekeeping. Linked Analytics and Ads properties had two places that could say no to the same cookies, so the company said it would split control by destination. Ads settings would govern Ads data, including data Analytics shares. Analytics settings would govern reporting inside Analytics.

An April 13, 2026 email from Google Analytics to property owners put the same split in product language. Starting June 15, tags and SDKs would apply destination-specific controls: the Signals setting and API would govern usage inside Analytics, and Ads Consent Mode would exclusively govern data used in Google Ads, including data shared from Analytics.

That is now live. Google’s Analytics data controls update says the Signals setting in the Analytics admin, and the Signals API, only control whether Analytics-sourced data is tied to signed-in user information for behavioral reporting. User privacy choices managed through Ads Consent Mode “will exclusively govern how data is collected and used.”

BEFORE THE JUNE 15 SPLIT

If Signals was already on, Google said Ads collection would not change. If Signals was off, Ads can now use advertising cookies whenever a user grants ad_storage. The old off switch does not veto that grant.

The Privacy Firewall Legal Teams Relied On

Jerry Bierenbroodspot, CTO of Voxxy Creative Lab and a former Google Ads Implementation Specialist (November 2021 to September 2024), argued before the deadline that the functional change was narrow. “From 15 June, only the cookie banner does that job. Google Signals will only govern what shows up in GA reports,” he wrote. He added that “almost nobody who already runs a real CMP” would see a working difference, because certified banners had routed marketing consent to ad_storage since Consent Mode v2 landed.

That reading is right for a banner that actually sets defaults to denied, then updates all four signals before any Google tag fires. It is wrong as a blanket comfort. Cookiebot, a Google-certified consent platform, split the live risk into three setups, and only one of them is clean.

THREE SETUPS AFTER THE CUTOVER

• No Consent Mode: Google tags run in their default active state, ad_storage is treated as granted, and advertising data is processed whether or not a visitor agreed. Cookiebot calls this the highest-risk position for EEA and UK traffic.
• Consent Mode with a granted default: Advertising data can reach Ads before anyone touches the banner. Cookiebot says this is the setting most often wired wrong, especially on older installs that were never reviewed.
• Denied defaults, live updates: No new compliance hole from the June 15 split, though a Signals setting that was never revisited can still starve reporting of signed-in demographic detail that would have been lawful to collect.

The population that used Signals-off as a second lock sits across the first two rows. Legal teams liked the lock because it cut the Ads path even when the banner leaked. Marketing teams accepted thinner audiences. Since mid-June that lock has been ornamental.

Nearly Half of Top Sites Still Fire the Wrong Signal

Privado AI, a New York privacy platform, published its State of Google Consent Mode findings on June 25, 2026, after a scan of 250 high-traffic websites across the United States and Europe, with tests in California, France and the United Kingdom. The firm said it ran sessions that included Consent Mode parameters, Global Privacy Control opt-outs, and reject-all clicks. The headline is not that those sites lacked a banner. It is that the banner’s choice often never reached Google.

WHAT THE 250-SITE SCAN FOUND

• 48% miswired: At least one Google Consent Mode error, with personal data still sent to Google Ads after an opt-out.
• 40% in California: Consent Mode stayed granted after a Global Privacy Control opt-out, which Privado flags against the CCPA.
• 28% in Europe: Consent Mode started in a granted state before the visitor chose anything, which Privado flags against the GDPR.
• 19% in Europe: A reject-all click did not move Consent Mode to denied.

The same study said 90% of the sites failed at least one privacy compliance test, and 87% failed at least one CCPA check. Those wider rates mix Consent Mode with other tracking failures, so they are not a second reading of the 48% figure. They do show how little slack the June 15 backstop removal left.

Collecting consent and enforcing it are two different things. The banner records the choice, and the data reaches Google Ads anyway.

Vaibhav Antil, Co-Founder and CEO, Privado AI

Daniel Goldberg, chair of data strategy and privacy at Frankfurt Kurnit Klein + Selz, said many companies still ship cookie approaches built for GDPR and then miss U.S. state rules, which is one reason California lagged in the scan. A CMP records a choice. It does not, by itself, prove every tag on the page obeyed it, and marketing stacks change week to week.

Remarketing Lists Empty With No Alert

The other failure mode is not extra data. It is missing data, with no alert in Google Ads. Alex Grieskamp, a senior digital analyst at Datascale, published DACH audit notes on July 14, 2026, after June and July project work, and updated them on September 8, 2026.

For years, Grieskamp wrote, German and Austrian setups that did not trust their Consent Mode wiring switched Google Signals off in GA4. That cut the Ads path no matter what the CMP passed. Since June 15, Signals only governs behavioral reporting inside GA4. A setup that still leans on the disabled toggle has either been sending Ads data it meant to hold back, or blocking data it is allowed to send. Neither state announces itself.

The pattern Datascale saw most often was a correct denied default and a broken update. The gtag('consent', 'update') call after Accept does not fire on every browser, or a CMP version change breaks the event map. Consent rates in Germany and Austria typically sit between 30 and 40%, Grieskamp wrote, so a missed update is the difference between a living remarketing pool and an empty one. Google does not raise a loud error when ad_user_data or ad_personalization is missing. Lists shrink. Smart Bidding sees fewer signals. Teams notice it in media results, not in Tag Manager.

Usercentrics still documents the practical fix for a Signals-off property that does not want Ads cookies: keep the Consent Mode mapping for Google Ads on a denied ad_storage default until a visitor grants it. A certified CMP does not finish that job unless the default event loads before gtag or GTM, and the update event lands on the same page view.

Setups in the months after June 15 still talk as if the old toggle were live. It is not. If the banner says granted, Ads can collect. If the update never arrives, Ads never sees the grant, and the campaign starves.

What Google Signals Still Controls in Analytics

Google Signals is still a product. It is just no longer an Ads valve. Turned on, it can associate Analytics hits with signed-in Google users who have ads personalization enabled, which feeds demographic and interest reporting inside GA4. Turned off, that signed-in join stops. Cross-device storytelling inside Analytics gets thinner. Ads no longer cares about that toggle.

Consent Mode remains a separate layer. It is not a banner and it does not collect consent. It tells Google tags what the banner decided. Google’s developer documentation on Consent Mode storage types and tag behavior still lists ad_storage as the switch for advertising cookies on the web and device identifiers in apps. When ad_storage is denied, no new advertising cookies are written, existing ones are not read, and requests leave through a different domain so old third-party cookies are not attached. Analytics will not read or write Google Ads cookies, and Signals features will not accumulate data for that traffic.

Google Ads Help describes how denied ad_storage changes pings: tags keep sending cookieless consent-state and conversion pings so Google can model gaps, but they do not store identifiers. Advanced Consent Mode is the version that loads tags in that denied state from the first hit. Basic mode holds the tags back until someone clicks. Either mode only works if the default is set before the first Google tag, which is the race Datascale keeps failing in audits.

Encrypted IPs and the Next Consent Gate

June 15 was the first cut in a stated plan to put Ads data under Ads settings. The Help Center still lists two follow-on moves without dates. Ads personalization, now spread across account, property, link, and event controls in Analytics, is supposed to collapse so that Consent Mode’s ad_personalization parameter exclusively decides whether shared Analytics data is used for personalization in a linked Ads account. IP addresses the Google tag and SDK already collect are supposed to be encrypted and handed to the linked Ads account, then used under Ads settings and terms. Google said more detail on both would come later in 2026. As of the current Help Center text, it has not.

THE CONSENT STACK GOOGLE HAS BEEN NARROWING

1. March 2024: Consent Mode v2, with ad_user_data and ad_personalization on top of ad_storage and analytics_storage, is required for remarketing and conversion measurement in the EEA, the UK, and Switzerland.
2. April 13, 2026: Google Analytics emails property owners that tags and SDKs will apply destination-specific controls from June 15.
3. June 15, 2026: Google Signals loses authority over Ads cookies and IDs; ad_storage becomes the sole Ads gate for linked accounts.
4. Later in 2026, undated: Google says ad_personalization will become the exclusive personalization control for linked Ads accounts, and encrypted IPs will flow to Ads under Ads rules.

The direction is consistent. Advertiser-side brakes inside Analytics are being retired so that a visitor’s Consent Mode flags, and Google’s own Ads settings, are the remaining gates. Cookie-era privacy theater, a Signals toggle flipped off in an admin panel that legal had signed, does not survive that design.

For EEA and UK sites, the live rule is already blunt. If ad_storage is granted, advertising cookies can flow, including association with a signed-in Google account when Google can make that join. If it is denied, they cannot. The Signals toggle cannot break that grant, and it cannot repair a banner that never sent the denial.

Frequently Asked Questions

Does Turning Off Google Signals Still Block Ads Cookies?

No. Since June 15, 2026, the Signals toggle has no effect on advertising cookies reaching a linked Google Ads account. Google’s in-product notice warned that setting Consent Mode ad_storage to denied “prevents the collection and usage of all advertising cookies and device identifiers from your website or app,” and that the change “applies to all data collected by Google Ads,” with a direct hit on measurement, conversion tracking, and campaign performance. That is the remaining lever, and it is binary.

What Does Google Signals Still Control in GA4?

It still controls whether Analytics data is associated with signed-in Google users for behavioral reporting. Cookiebot notes that this still feeds richer demographic and interest reports inside Analytics for signed-in users who have Ads Personalization enabled. It does not govern remarketing lists, Smart Bidding identifiers, or Ads cookies.

What Happens if a Site Has No Consent Mode?

Google tags then run in their default active state and treat ad_storage as granted, so advertising data is processed whether or not a visitor agreed. Cookiebot calls that the highest-risk position for any site with EEA or UK visitors, because no banner choice is communicated to Google’s tags at all.

When Did Consent Mode v2 Become Required in Europe?

Google has required the v2 signals, including ad_user_data and ad_personalization, for remarketing and conversion measurement in the EEA, the United Kingdom, and Switzerland since March 2024. The June 15, 2026 change did not add those two parameters. It changed which Google product setting can override the Ads path those parameters already described.

Is Ads Personalization Already on the Same Exclusive Gate?

No. Google said the exclusive ad_personalization control for linked Ads accounts comes later in 2026, and the Analytics Help Center page still has not published a date. Until that lands, personalization can still be shaped by the older stack of Analytics account, property, link, and event settings, on top of the Consent Mode flag.

Disclaimer: This article is news reporting and technical analysis of a completed Google product change. It is informational only and is not legal advice, privacy counsel, or a compliance audit of any website, app, or advertising account. Consent rules under the GDPR, UK GDPR, CCPA, and other laws depend on your traffic mix, legal basis, and how tags are actually wired, so you should consult a qualified privacy lawyer or data protection officer before changing banners, Consent Mode defaults, or Google Signals. Figures and product statuses reflect the Google Help Center, vendor documentation, and published scans cited here as of the dates on those documents, and Google can still change remaining 2026 controls without a new public date.