Google unifies data controls across Analytics and Ads: what changes in 2026
Google announced an update to how privacy controls are managed across Google Analytics and Google Ads. The idea is simple: remove duplicate controls and let each platform govern only its own data. In practice, this makes Consent Mode the central control — so it's worth reviewing your setup before the key dates.
Official source: Updates to Google Analytics data controls (Google Analytics Help Center).
What changes, in one sentence
Until now, some settings overlapped: you could control the same thing from Analytics and from Ads. Google is separating them. After the change, Google Ads settings exclusively control Ads data (including what Analytics shares with Ads), and Analytics settings control only what happens inside Analytics. The bridge between the two becomes user consent, expressed through Consent Mode.
The three concrete changes
1. Google Signals stops controlling Ads cookies and IDs
The Google Signals setting will no longer govern Google Ads cookies or
identifiers. Starting June 15, 2026, that decision is made exclusively by
Consent Mode (the ad_user_data signal). Fewer switches, a single source of
truth.
2. Ad personalization consolidates into ad_personalization
The multiple personalization configuration layers that existed in Analytics are being
unified. Consent Mode's ad_personalization signal will be the one — exclusively
— that decides whether data is used to personalize ads in Ads.
3. IPs get encrypted and controlled from Ads
IP addresses will be encrypted and flow to Google Ads, where they'll be governed by Ads settings instead of a dedicated Analytics setting.
Dates to mark
| Date | What happens |
|---|---|
| June 15, 2026 | Google Signals starts relying on Consent Mode as the single control |
| Later in 2026 | Changes to ad personalization and IPs (dates to be confirmed) |
Why this helps you (if you're set up right)
If you already send correct Consent Mode v2 signals, this change works in your favor: redundant settings disappear and user preferences run consistently across Analytics and Ads. One signal, sent correctly, rules both platforms.
The risk is the opposite case: if you relied on an Analytics setting or Google Signals to "patch over" an incomplete consent setup, that patch stops working. Once Consent Mode becomes the single control, what truly matters is the signal your site sends.
What to check so nothing breaks
- Confirm you send Consent Mode v2 in advanced mode with all seven parameters,
including
ad_user_dataandad_personalization. If any is missing or malformed, behavior will change after June 15, 2026. - Verify the links between your Analytics properties and your Google Ads accounts: the consolidated data flow depends on them being properly linked.
- Review the
gcsparameter to make sure the consent state travels as expected (we explain it in this guide). - Don't lean on settings that are going away. If your compliance relied on Google Signals or an Analytics toggle, move it now to a correct Consent Mode signal.
- Document the change with your analytics and marketing teams, so nobody mistakes a shift in the reports for a business problem.
The bottom line
Google is simplifying, not tightening. But simplification shifts all the weight onto a single piece: your site's consent signal. If that signal is correct, you have nothing to do but confirm it. If it isn't, the patches that compensated for it are about to disappear.
Conma configures Consent Mode v2 in advanced mode and ensures ad_user_data and
ad_personalization arrive in the right order and format — so this transition won't
touch your data or your campaigns.