Google is simplifying data controls between GA4 and Google Ads. The core principle is straightforward: data controls will live where the data is used. GA4 settings will control behavioral reporting in GA4, and Google Ads settings will control data in Google Ads.1
This article covers what’s changing, what to expect in your reports, and what needs to happen before June 15, 2026.
What’s Changing?
Three separate changes are rolling out on different dates:
| Change | Date | Impact |
|---|---|---|
| Google Signals role change | June 15, 2026 | Ads cookie/ID collection control moves to Consent Mode |
| Ads personalization consolidation | Later 2026 (date TBD) | GA4 layered settings removed, ad_personalization becomes single control |
| IP address flow | Later 2026 (date TBD) | Encrypted IP flows to linked Google Ads account |
The shared logic: overlapping controls between GA4 and Google Ads are being removed. Each platform manages its own data with its own settings.1
Google Signals’ New Role
Current state: Google Signals controls both the use of signed-in user data in behavioral reporting and Google Ads cookie/ID collection. Consent Mode Ads settings also control the same data collection process. Two different settings, doing the same job.
Starting June 15, 2026:
- Google Signals will only control the association of signed-in user data in GA4’s behavioral reporting
- Consent Mode (on the Google Ads side) will be the single control point for Google Ads data collection
Practical result: turning off Google Signals will no longer stop Google Ads cookie and ID collection. That control moves entirely to Consent Mode.1
Consent Mode Parameters: Now the Single Gate
Consent Mode v2’s four core parameters (ad_storage, ad_user_data, ad_personalization, analytics_storage) become more critical with this change. Previously, there was a dual-layer control structure with Google Signals. Now Consent Mode alone manages all Google Ads data flow.
This makes CMP configuration accuracy even more important. My earlier article on consent’s impact on measurement is worth revisiting in this context. A deeper piece on Consent Mode V2’s signal architecture is coming soon in English, subscribe to the newsletter to get notified.
The fastest way to verify your CMP’s consent default and update signals: InfoTrust’s Consent Mode Inspector Chrome extension. It displays the state of all four parameters on page load without opening DevTools.
Missing parameter issues in consent features provided by e-commerce platforms like T-Soft are already common. With this change, consent implementations sending incomplete parameters will cause greater data loss, because Signals will no longer serve as a fallback.
Ads Personalization Change
Later in 2026 (exact date not yet announced), GA4’s ads personalization settings will also be consolidated.
Today, ads personalization is controlled at four different levels within GA4: account, property, Ads link, and event. This layered structure will be removed. Once data flow to Google Ads is established (GA4 property link), the ad_personalization consent parameter will be the single control point.1
Affected areas:
- Remarketing audiences
- Audience export (DV360, SA360)
- Personalized ad targeting
No urgent action is needed for this change yet, but documenting your current GA4 ads personalization settings is useful. It creates a reference point for understanding what changed during the transition.
IP Address Flow
IP addresses automatically collected by the Google Tag and SDK will flow encrypted to linked Google Ads accounts. This data will be governed by Google Ads settings and terms of service.1
Different rules apply for users outside the EEA, UK, and Switzerland. Details are on Google’s IP address usage page.
Expected Reporting Changes
The reporting impact depends on your current configuration:
Consent Mode v2 Advanced already active: Minimal change. Consent Mode was already controlling data collection, and Signals’ additional control was effectively redundant in most scenarios.
Google Signals off, Consent Mode active: No change. Signals was already off, and Consent Mode was operating as the single control.
Google Signals on, Consent Mode not set up or incomplete: The largest impact group. After June 15, Signals will no longer provide Google Ads data collection control. Without Consent Mode, there will be no user-preference-based control mechanism. This creates both legal compliance and data quality risk.
Modeling quality: Consent Mode becoming the single control point could provide more consistent signal flow to Google’s modeling engine. Improved modeling quality is expected long-term, but short-term impact is not currently predictable or measurable.
What to Do Before June 15
-
Verify Consent Mode v2 setup: Are all four parameters (
ad_storage,ad_user_data,ad_personalization,analytics_storage) active and correct? Test with Consent Mode Inspector. -
Test CMP consent signals: Is your banner sending consent default and update calls correctly? Is
gtag('consent', 'default', {...})firing on page load, andgtag('consent', 'update', {...})firing after user selection? -
Review Google Signals settings: Is signed-in user data still needed for behavioral reporting? If not, consider turning it off to prevent unnecessary thresholding in reports.
-
Check GA4-Google Ads link: Is data flow active? Is the correct property linked?
-
Document ads personalization settings: Note your current account/property/link/event level settings for the later 2026 transition.
-
Check BigQuery export: If active, review the modeled vs observed data split. Modeling behavior may change when Consent Mode becomes the single gate.
-
Establish a reporting baseline: Capture a 30-day pre-June baseline. You’ll need it for post-June comparison.
Who Is Not Affected?
- Consent Mode v2 Advanced already properly configured: Transition is largely transparent. Consent Mode was already operating as the single control.
- Not using Google Ads: The Signals change concerns GA4-Google Ads data flow. No Ads link means no direct impact.
- GA4-only (no Ads link): IP address flow and ads personalization changes don’t apply.
Footnotes
- 01 Starting June 15, 2026, Google Signals will no longer control Google Ads cookie and ID collection; it will only manage signed-in user data and behavioral reporting
- 02 Consent Mode (ad_storage, ad_user_data) becomes the single control point for Google Ads data collection
- 03 Later in 2026, GA4's layered ads personalization settings will be removed, with the ad_personalization consent parameter becoming the single control
- 04 IP addresses will flow encrypted to linked Google Ads accounts, governed by Google Ads settings
- 05 For those with Consent Mode v2 properly configured, the transition will be largely transparent
- 06 Accounts without Consent Mode will be most affected: Signals will no longer serve as a fallback
+ Is Google Signals being removed entirely?
No. Google Signals will continue to exist but with a narrowed role. Starting June 15, 2026, it will only control the use of signed-in user data in behavioral reporting. Google Ads cookie and ID collection control moves to Consent Mode.
+ Do I need to take action if Consent Mode v2 is already set up?
If Consent Mode v2 Advanced is properly configured and all four parameters (ad_storage, ad_user_data, ad_personalization, analytics_storage) are active, the transition will be largely transparent. Still, verifying that your CMP sends correct signals and establishing a pre-June reporting baseline is good practice.
+ What happens if Consent Mode is not set up?
After June 15, 2026, Google Signals will no longer provide Google Ads data collection control. Without Consent Mode, there will be no user-preference-based control mechanism for data flowing to Google Ads. This creates risk for both legal compliance and data quality.
+ Am I affected if I use GA4 but not Google Ads?
Not directly. The Google Signals change concerns data flowing through the GA4-Google Ads link. Without an Ads link, IP address flow and ads personalization changes don't apply. However, reviewing Google Signals' role in your behavioral reporting is still worthwhile.
+ Does this change affect GDPR compliance?
Not directly. GDPR already requires explicit consent for personal data processing. Google moving the control to Consent Mode technically simplifies compliance: sending the correct consent signal at a single point is sufficient. However, verify that your CMP configuration correctly communicates all four consent parameters.