Google this week published an announcement in the Google Analytics Help Center outlining a restructuring of how data controls work between Google Analytics and Google Ads. The change, the most significant of which takes effect on June 15, 2026, removes Google Signals from its current role as a co-controller of advertising data collection and consolidates that authority under Consent Mode settings managed within Google Ads.

The announcement affects any organization that has linked a Google Analytics property to a Google Ads account - a configuration that is standard practice across digital advertising. For those setups, the rules about which system controls what are about to change materially.

What is changing and why

According to Google's Help Center document, the core rationale behind the update is deduplication of controls. Currently, when a Google Analytics property is linked to a Google Ads account, certain settings in Google Analytics continue to govern how data behaves inside Ads. That has created a situation where two separate systems - Analytics and Ads - both exercise authority over the same data flow. According to the announcement, Google intends to end that overlap: "To simplify data controls and remove redundant settings between Google Analytics and Ads, we are planning to consolidate controls based on where the data is used."

The stated principle is straightforward. Google Ads settings will govern all data used in Google Ads. Google Analytics settings will govern data used within Google Analytics for behavioral reporting. Each product controls its own domain. The stated goal is that "user preferences are enforced consistently between Google Analytics and Google Ads."

Simo Ahava, co-founder at Simmer and partner at 8-bit-sheep, described the shift in a LinkedIn post shared this week, framing it as a move toward a single source of truth. According to Ahava, "The purpose is no doubt to move towards a single source of truth for Ads consent rather than have obscure (and often hidden) GA settings affect the data flow."

Google Signals: a narrowed role from June 15

The first and most time-critical piece of this restructuring concerns Google Signals. Currently, the collection of Google Ads cookies and IDs via the Google Analytics tag and SDK is controlled jointly by the Google Signals setting in Google Analytics and the Consent Mode Ads settings. Starting June 15, 2026 - exactly two months away - that dual control ends.

According to the Help Center document, "starting June 15, 2026, Google Analytics will transition to using Consent Mode (within Google Ads) as the single control for data. This means your users' privacy selections, managed via Ads Consent Mode settings, will exclusively govern how data is collected and used."

The consequence is technical but significant. After June 15, the Google Signals setting in Google Analytics admin - and the Google Signals API - will retain only one function: controlling whether Google Analytics-sourced data is associated with signed-in user information for behavioral reporting. According to the announcement, "the Google Signals setting in Google Analytics admin and the Google Signals API will only control the association of your Google Analytics sourced data with signed in user information for behavioral reporting."

It no longer controls advertising data collection at all. That authority transfers exclusively to the ad_storage parameter within Consent Mode.

Ahava's analysis on LinkedIn clarified what this means in practice. According to his post: "As for the 'migration': if you have Google Signals currently turned ON, there's no real change in behavior. If Google Signals is OFF, then Ads may start linking user data with their Google login as long as ad_storage consent is granted."

The gap he identifies is a meaningful one. Organizations that have had Google Signals disabled as a privacy measure may not realize that, after June 15, that setting no longer prevents Google Ads from linking user data with Google sign-in information. Whether that linkage occurs will depend entirely on the ad_storage consent signal - not on the Analytics configuration.

Ahava went further in his LinkedIn post, noting the binary nature of the new arrangement: "If I'm reading this correctly, there's no middle ground here. Either grant ad_storage and Google will use all available ads signals at their disposal (including linking the user with their Google sign-in), or set it to denied and Google will not access any identifiers apart from what's available in the url (e.g. gclid)."

The practical implication for organizations relying on Google Signals being off as a privacy backstop is that this backstop disappears in 60 days, unless Consent Mode ad_storage is also set to denied where appropriate.

Blocking advertising data entirely: what ad_storage denied means

Google's announcement, and the accompanying screenshot from the in-product notification, include an explicit warning about the ad_storage denied path. According to the in-product notification: "Changing consent mode ad_storage to denied prevents the collection and usage of all advertising cookies and device identifiers from your website or app. This action applies to all data collected by Google Ads and will significantly impact advertising measurement and conversion tracking, and hinder the performance of your campaigns within your linked ads account."

That warning matters for organizations in regulated markets - particularly the European Economic Area, the UK, and Switzerland - where consent for ad_storage cannot be assumed. When users decline advertising consent, ad_storage is denied by the consent management platform, and the advertising system operates without identifiers. Consent Mode v2's modeling capabilities partially compensate for this, using aggregate data from consented users to estimate conversion patterns for non-consented traffic, but the accuracy of that modeling degrades as the proportion of non-consenting users rises.

The announcement notes that the ad_storage default state can be set regionally, which is consistent with how most Consent Mode v2 implementations already operate - setting a default-denied state for EEA traffic while allowing consent banners to grant it where users agree.

For context on the downstream effects of Consent Mode misconfiguration, PPC Land has previously documented cases where advertisers experienced dramatic drops in conversion reporting after Consent Mode V2 was not correctly implemented, with one case involving a 90% collapse in Google Ads conversions overnight.

Ads Personalization: a second change, dates still pending

Beyond the June 15 Google Signals change, Google has signaled a second, parallel update to how ads personalization is controlled. The timing here is less defined.

According to the announcement, ads personalization is currently managed through multiple layers within Google Analytics - at the account level, property level, Ads link level, and event level. That layering is set to be collapsed. According to the document: "Similar to the Google Signals change, we will simplify this to ensure the usage of this Ads data is exclusively controlled by Ads settings. When you link your Google Analytics property to your Google Ads account, you establish the flow of data to Ads. At that point, the Consent Mode ad_personalization setting will exclusively control if that data is used for personalization in your Ads account."

The exact date for this change has not been published. According to Google's announcement, "more details and the exact dates for changes to ads personalization and IP address controls will be shared later this year." That leaves a period of uncertainty for implementers who need to prepare their Consent Mode setups and verify that ad_personalization signals are being passed correctly before the change takes effect.

The ad_personalization parameter is one of the four core Consent Mode v2 parameters introduced in December 2023, alongside ad_storage, ad_user_data, and analytics_storage. It controls whether data can be used to serve personalized advertising. Its correct implementation is a prerequisite for remarketing audiences and personalized campaign targeting to function under the new framework. Previous PPC Land reporting on Consent Mode V2 updates covered the introduction of these parameters when Google first announced enforcement deadlines.

IP addresses: encrypted flow to Google Ads

The announcement also addresses IP addresses, a topic that has generated regulatory attention across European markets. According to Google's document, "IP addresses that are automatically collected by the Google Tag and SDK will be encrypted and flow to your linked Google Ads account. The encrypted IP addresses are then controlled by Google Ads and will be used in accordance with your Google Ads settings, configurations, and relevant terms of service."

The document specifies that additional guidance on IP address usage for users outside the EEA, the UK, and Switzerland is available in a separate Help Center article. As with ads personalization, exact dates for changes to IP address controls will be communicated later in 2026.

The IP address question is not new. Google's broader effort to handle IP-based identification has been part of Privacy Sandbox deliberations and drew criticism in the Q1 2025 Privacy Sandbox report for what some stakeholders considered a contradiction - masking IPs from third parties while retaining access for Google's own systems.

The June 15 change increases the operational weight placed on Consent Mode implementations, specifically the correctness of ad_storage signal updates. Until now, an organization that had Google Signals disabled in Analytics could treat that as a partial safety net against ad data collection, even with an incomplete or delayed Consent Mode setup. After June 15, that fallback is gone.

Ahava's LinkedIn post noted directly: "This does place more stress on your consent mode implementation, so make sure the update calls are done appropriately and contain the correct signals."

The comment threads on the LinkedIn post - involving practitioners from Hermès, Reprise Media, Kesko, meshcloud, and other organizations - surface additional technical questions. One practitioner raised what happens when a user deselects "Ad services" in the GA4 Consent Settings area ("Manage data use across Google services") but maintains a granted ad_storage signal. Ahava's response in the thread suggests that, under the new framework, the ad_storage signal would be the governing factor - not the Analytics-side setting.

Another commenter noted the question of whether the allow_google_signals gtag setting would continue to work. According to Ahava in the thread: "it will work for GA but it won't do anything for Ads, if I'm reading the docs correctly."

Google has been building toward this kind of consolidation for some time. PPC Land previously reported on Google's hidden data transmission controls added to Google Tag settings in late 2025, which gave advertisers independent control over advertising data, behavioral analytics, and diagnostic data collection when consent signals indicate denial. Those controls, which Ahava described at the time as "basically a Basic Consent Mode type control on top of an Advanced Consent Mode setup," represent a parallel track - putting more explicit levers in the hands of advertisers while consolidating the underlying consent authority into Consent Mode.

The addition of Tag Diagnostics to the Analytics consent settings hub in July 2025 was another preparatory step, giving website operators a consolidated view of consent signal status across data streams without needing to navigate multiple Google tools. That system maintains a 48 to 72-hour detection latency for consent signal updates, meaning implementation issues can persist for up to three days before the diagnostic tools register them - a lag that becomes more consequential when the ad_storage signal is the single authority over advertising data collection.

The move also aligns with Google's enforcement of EU User Consent Policy compliance from July 2025, when non-compliant EU and UK advertisers began losing conversion tracking, remarketing, and personalized ad functionality. That enforcement made clear that Consent Mode was no longer optional for EEA-facing accounts - it had functional consequences. The June 2026 Google Signals change extends that logic: the remaining non-Consent-Mode controls in Analytics are being retired from their advertising governance role.

Context in Google's broader data architecture shift

These changes are part of a wider set of architectural decisions Google has been making across its measurement stack. In January 2026, Google announced the end of new session attribute and IP address imports in the Google Ads API from February 2, 2026 - a change PPC Land covered in the context of Google's Data Manager API consolidation. The pattern across these moves is consistent: reduce fragmented controls, route data through fewer but more authoritative pathways, and place privacy-governance authority closer to the system where the data is ultimately used.

For marketing and analytics professionals, the practical implication is a tighter dependency between their Consent Management Platform implementation and the behavior of Google Ads. Previously, Analytics-side settings provided a second layer of control. Going forward, the CMP's output - specifically whether it grants or denies ad_storage and ad_personalization - becomes the definitive signal for what Google Ads can and cannot do with linked Analytics data.

Organizations that have had Tag Diagnostics integrated into their Analytics consent settings since mid-2025 are better positioned to identify signal gaps before June 15. Those without monitoring in place face a risk of behavior changes they may not immediately detect - particularly in the scenario where Google Signals was previously off, and the absence of that setting meant Ads was not linking user data to Google sign-ins.

The announcement does not specify whether there will be any notification or warning within Google Analytics admin when the transition occurs on June 15.

Timeline

Summary

Who: Google, affecting all organizations with Google Analytics properties linked to Google Ads accounts, along with the analytics and ad tech professionals responsible for those implementations.

What: Google is restructuring data governance between Google Analytics and Google Ads. Starting June 15, 2026, Google Signals will no longer control the collection of Google Ads cookies and IDs; the ad_storage Consent Mode parameter within Google Ads will become the sole authority. A second change - consolidating ads personalization control under the ad_personalization Consent Mode parameter - is also planned for later in 2026, with exact timing to be confirmed. IP addresses collected by the Google Tag and SDK will be encrypted and flow to linked Google Ads accounts, governed by Google Ads settings.

When: The Google Signals change takes effect June 15, 2026. The ads personalization and IP address control changes have no confirmed date yet.

Where: The change affects Google Analytics properties worldwide that are linked to Google Ads accounts. Regional defaults for ad_storage can be configured within Consent Mode settings.

Why: Google has stated the goal is to eliminate redundant controls between Analytics and Ads, ensure that data used in each product is governed exclusively by that product's settings, and streamline the consent process so that user preferences are enforced consistently across both platforms.

Share this article
The link has been copied!