A LinkedIn post published yesterday by Jerry Bierenbroodspot, CTO and co-founder of Voxxy Creative Lab and a former Google Ads Implementation Specialist, cuts through what he describes as overstated coverage of a specific privacy change arriving on June 15, 2026. The change is narrow in scope but meaningful in consequence for a specific subset of sites. For the majority running a compliant consent management platform, almost nothing changes. For a smaller group that has been relying on a backend toggle as a substitute for proper consent infrastructure, June 15 closes that workaround.

What is actually changing

At its core, the June 15 update narrows a single control in Google Analytics. Right now, sites that have linked a Google Analytics property to a Google Ads account have two independent mechanisms that can block advertising data collection. The first is the user-facing cookie banner - specifically, the Consent Mode signal transmitted when a user declines ad tracking. The second is an admin-level toggle inside Google Analytics: the Google Signals setting. An administrator who turns Google Signals off has, until now, been able to prevent ad data collection at the backend, regardless of how the CMP was configured.

According to Bierenbroodspot's post, "from 15 June, only the cookie banner does that job. Google Signals will only govern what shows up in GA reports." That is the entirety of the functional change. One administrative lever narrows its scope. It does not disappear - it simply loses authority over advertising data collection and retains only its role in controlling whether Google Analytics data gets associated with signed-in user information for behavioral reporting purposes.

PPC Land covered the full technical restructuring in detail when Google published the announcement in its Help Center. According to that coverage, the change affects any organization with a linked Google Analytics and Google Ads account - which is standard practice across digital advertising. After June 15, the ad_storage parameter inside Consent Mode becomes the sole authority over whether advertising cookies and device identifiers are collected from a website or app. The Google Signals setting in the admin panel, and the Google Signals API, will control only one thing: whether Google Analytics-sourced data is associated with signed-in user information for behavioral reporting.

Who is - and is not - affected

Bierenbroodspot is direct about the affected population: "Almost nobody who already runs a real CMP." Every certified CMP listed in his post - Cookiebot, OneTrust, Iubenda, Usercentrics, Termly, and Klaro - already routes the Marketing consent category to ad_storage and the Statistics consent category to analytics_storage. These platforms have been operating this way since Consent Mode v2 became mandatory in March 2024. Sites using any of those platforms are already in the end state that June 15 formalizes.

The sites that will see actual behavioral change are those running Google Analytics linked to Google Ads, with no CMP, and with "Google Signals OFF" configured as a deliberate privacy gesture at the backend. From June 15, those sites will emit ad cookies they were not previously emitting. For organizations operating in the EU or EEA, that is a concrete GDPR exposure - not a theoretical one.

The distinction matters technically. A site without a CMP has no mechanism for collecting or transmitting user consent signals. If Google Signals was the only thing preventing ad cookie collection, removing that protection means the site defaults to emitting those cookies in the absence of any contrary signal. The Consent Mode framework interprets the absence of a denied signal as permission to proceed, depending on how the default consent state is configured. Sites that never configured a default denial - or never configured Consent Mode at all - face the sharpest exposure.

A previous PPC Land investigation documented the concrete consequences of Consent Mode misconfiguration, including a case where a client's Google Ads conversions collapsed 90% overnight after Google's July 2025 EU enforcement because the consent banner was collecting user choices but failing to transmit them to Google's tag layer. Recovery was only partial: roughly 40% of the lost attribution data was recoverable once the configuration was corrected. The remaining 60% was permanently absent from the historical record.

Consent Mode operates through parameters that flow from the consent management platform to Google tags in real time. Version 2, which Google updated in December 2023, introduced two additional parameters beyond the original pair. The full set of four parameters in play is: ad_storage, which controls whether advertising cookies are enabled; analytics_storage, which governs behavioral measurement; ad_user_data, which controls whether personal data is sent to Google for advertising purposes; and ad_personalization, which controls whether that data can be used for personalized advertising.

All four parameters must be transmitted correctly and in the correct sequence - before Google's tags activate - for the system to register consent properly. A banner that appears to work, presents choices visibly, and logs user decisions can still fail silently if it does not pass these signals to the Google tag layer. According to PPC Land's reporting on the consent monitoring tools Google added to Analytics in June 2025, the diagnostic system that monitors consent signal status operates with a 48- to 72-hour detection latency. That means a configuration error can persist for up to three days before Google's diagnostic tools flag it - a lag that becomes more consequential when ad_storage is the single authority over advertising data collection.

The gap between a banner that appears to work and one that actually passes correct signals was documented extensively in the ex-Google analyst debate that emerged after the June 15 announcement was circulated. Krista Seiden, a former Google Analytics product manager who worked at Google between 2014 and 2019, drew more than 650 reactions and 69 comments on LinkedIn by framing the change differently from Google's own description. According to that coverage, Seiden called the update "quietly removing one of the most important privacy controls advertisers had in Google Analytics" while Google described it as "simplifying controls and streamlining the consent process." She also questioned why Google offered a 90-day grace period for updating privacy disclosures if nothing meaningful were changing about user data handling - noting that a 90-day window implies current privacy policies will be inaccurate after June 15 for organizations that described Signals as controlling ad data flows.

The broader trajectory Bierenbroodspot identifies

The practitioner perspective in the LinkedIn post does not stop at June 15. Bierenbroodspot frames the change as one step in a visible sequence: Consent Mode v2 in 2023, Enhanced Conversions in 2024, the _gcl_aw cookie changes in 2025, EC4L in 2025-26, and this update in 2026. According to his post, "every step is consistent with one trajectory: away from cookie-and-click measurement, toward measurement keyed to hashed personally-identifying information."

That trajectory has a direct parallel in the measurement infrastructure changes Google has been making in parallel. Google in April 2026 unified enhanced conversions for web and leads into a single toggle, accepting data from tags, Data Manager, and APIs simultaneously. The Data Manager API, launched December 9, 2025, established a centralized ingestion point for first-party data across Google Ads, Google Analytics, and Display and Video 360. Customer Match uploads through the Google Ads API ceased functioning entirely on April 1, 2026, with all new implementations pushed to the Data Manager API. Each of these moves consolidates measurement into pipelines based on hashed user identity rather than third-party cookie signals.

Bierenbroodspot's conclusion is pointed: "Watch the trajectory. The next 18 months will matter more than 15 June."

Context from the regulatory environment

The June 15 change arrives against a backdrop of escalating enforcement. Google disabled conversion tracking for non-compliant EU advertisers in July 2025, making Consent Mode v2 functionally mandatory for EEA-facing accounts with real campaign consequences. A German court ruling - the Verwaltungsgericht Hannover case - determined that Google Tag Manager itself cannot activate before explicit user consent is obtained, finding that Tag Manager transmitted user device data including IP addresses to US servers before any consent interaction occurred. That ruling has prompted some marketing technology teams to reconsider the sequencing of their tag management infrastructure entirely.

France's CNIL has maintained that Google Analytics does not qualify for consent-derogated analytics use - the exemption that allows some analytics tools to operate without consent because they serve analytics only and do not join to user-identified data. Adobe Analytics has made that list. Google Analytics has not. The June 15 change, which folds Google Signals' advertising data function entirely into the advertising consent layer, reinforces that classification rather than challenging it.

One technical detail that has received limited public attention is the allow_google_signals parameter - a gtag setting described in limited documentation as a way to disable advertising features based on third-party identifiers when set to false. Whether this parameter retains functional relevance after June 15, when the Signals toggle loses its advertising data authority, has not been addressed in Google's announcement.

Google also announced in May 2026 that granular Google Ads reporting data will be accessible for a maximum of 37 months starting June 1, 2026 - a separate but parallel contraction of data accessibility arriving in the same window. That change affects the Google Ads API, Google Ads scripts, the Google Analytics Data API, and the BigQuery Data Transfer Service. Together, June 2026 represents a cluster of measurement infrastructure changes arriving in close succession.

What Bierenbroodspot's background adds to the reading

The post carries weight partly because of its source. According to his LinkedIn profile, Bierenbroodspot worked as a Google Ads Implementation Specialist at Google in Lisbon from November 2021 to September 2024 - nearly three years in a hybrid role working with Google Analytics 4 and Google Tag Manager. He subsequently worked as a freelance Tracking Specialist between September 2024 and February 2025. He now serves as CTO and co-founder at Voxxy Creative Lab, described as focused on helping DTC brands fix broken tracking and recover lost ROAS using GA4, GTM, and server-side analytics.

That background places him in a category of practitioner who has worked on implementation inside Google and then moved to the client and agency side - a vantage point that gives his "almost nobody is affected if you have a real CMP" reading particular credibility. His framing of the June 15 change as less important than the trajectory it represents reflects a reading that the operational significance lies in the 18 months ahead, not in the administrative toggle change itself.

For marketing practitioners whose organizations have already invested in proper consent management infrastructure - certified CMPs, correctly sequenced tag loading, verified ad_storage and ad_user_data signal transmission - June 15 changes nothing in practice. The systems they run have been operating in the post-June-15 state since early 2024. The date is a formalization, not a disruption.

For organizations that have not made that investment, the change removes a backstop that was already an incomplete substitute for proper compliance. The exposure was always present; June 15 makes it visible.

Timeline

  • December 2023 - Google introduces two new Consent Mode v2 parameters: ad_user_data and ad_personalization, expanding the framework beyond the original ad_storage and analytics_storage pair
  • March 2024 - Consent Mode v2 becomes mandatory; certified CMPs including Cookiebot, OneTrust, Iubenda, Usercentrics, Termly, and Klaro align their signal routing to the v2 parameter structure
  • June 2025 - Google adds Tag Diagnostics to the Analytics consent settings hub, giving website operators consolidated consent signal monitoring; system operates with 48- to 72-hour detection latency
  • July 2025 - Google disables conversion tracking, remarketing, and personalized ad functionality for non-compliant EU and UK advertisers, making Consent Mode v2 functionally mandatory for EEA-facing accounts
  • April 15, 2026 - Google publishes announcement in the Help Center and sends email notifications to customers with linked Google Analytics and Google Ads accounts; PPC Land covers the full technical restructuring
  • April 21, 2026 - Former Google Analytics product manager Krista Seiden publishes LinkedIn post challenging Google's "simplification" framing; post draws over 650 reactions and 69 comments
  • April 2026 - Google announces unified enhanced conversions toggle for web and leads, merging two separate products into a single on/off feature starting June 2026
  • May 1, 2026 - Google publishes documentation confirming granular Google Ads reporting data will be limited to a 37-month retention window starting June 1, 2026
  • May 6, 2026 - Jerry Bierenbroodspot, CTO of Voxxy Creative Lab and former Google Ads Implementation Specialist, publishes practitioner analysis on LinkedIn clarifying who is and is not affected by the June 15 change
  • June 15, 2026 - Google Signals ceases to govern advertising data collection; ad_storage in Consent Mode becomes the sole authority for all linked Google Analytics and Google Ads accounts

Summary

Who: Jerry Bierenbroodspot, CTO and co-founder of Voxxy Creative Lab and a former Google Ads Implementation Specialist at Google (November 2021 to September 2024), published a practitioner analysis on LinkedIn today explaining the practical scope of the June 15, 2026 Google Analytics change.

What: On June 15, 2026, Google removes the Google Signals setting as a co-controller of advertising data collection for linked Google Analytics and Google Ads accounts. From that date, the ad_storage parameter inside Consent Mode becomes the sole authority over whether advertising cookies and device identifiers are collected. Google Signals retains one narrower function: controlling the association of Google Analytics data with signed-in user information for behavioral reporting. Sites already running a certified CMP with correctly routed consent signals are already in the end state and see no functional change.

When: The LinkedIn post was published today, May 6, 2026. The underlying Google change takes effect on June 15, 2026. Google published its original Help Center announcement and sent email notifications to affected customers on April 15, 2026.

Where: The change affects every Google Analytics property linked to a Google Ads account globally. The most acute legal exposure sits in the EU and EEA, where GDPR requires a lawful basis for advertising data collection and where regulators have taken enforcement action against Google Analytics implementations. Bierenbroodspot's analysis was published on LinkedIn.

Why: The June 15 change reflects a structural shift Google has been making across its measurement infrastructure - consolidating advertising data governance into Consent Mode while reducing the number of separate admin controls. For organizations without a CMP that used the Google Signals toggle as a backend privacy measure, the change removes a workaround that was never a sufficient substitute for proper consent infrastructure. The broader trajectory, as Bierenbroodspot frames it, moves measurement away from cookie-and-click models toward systems keyed to hashed personally-identifying information - a direction visible across Consent Mode v2, Enhanced Conversions, and the Data Manager API changes of 2024 through 2026.

Share this article
The link has been copied!