Google Ads Consent Signals Update and What Changes Now
Google changed how Google Ads consent signals interact with Google Analytics 4 (GA4) on 15 June 2026.
Google Ads settings now exclusively control Google Ads data for linked properties, including data shared from Google Analytics.
Google Signals in GA4 plays a narrower role, linking GA4-sourced data to signed-in users for behavioural reporting only.
Australian and New Zealand advertisers running linked GA4 and Google Ads accounts should give this update a proper review before it causes a reporting surprise.
Google says consented users are usually 2-5 times more likely to convert than users who do not consent.
That difference shows why getting the underlying consent signals right carries real commercial weight, well beyond a compliance requirement.
It also requires 700 ad clicks over a seven-day period for each country and domain grouping before Consent Mode conversion modelling becomes eligible.
For advertisers, agencies and data teams, testing comes before changing.
Understand which Google Ads consent signals control each part of the data flow, then verify the path from the consent banner through Google Tag Manager, GA4 and Google Ads.
Google Ads Consent Signals Update and New GA4 Controls
This section breaks down exactly what changed on 15 June 2026, and which platform now controls each Google Ads consent signal.
What changed in Google Ads and GA4 consent controls
From 15 June 2026, Google Ads settings exclusively control Google Ads data, including data shared by Google Analytics, while Google Analytics settings control data used within GA4 for behavioural reporting.
Before that date, the Google Signals setting in GA4 could also influence Google Ads cookies and IDs whenever a GA4 property was linked to Google Ads, creating an overlap between the two sets of controls.
Google has now removed that overlap, so each platform governs only its own data.
A company can disable Google Signals in GA4 while Google Ads keeps processing advertising data through its own Consent Mode configuration.
The two settings now serve separate purposes.
Older tracking documentation that tells an analyst to check Google Signals when investigating a Google Ads consent issue is no longer sufficient.
Google frames the split as simplification. Each control now follows where the data is used.
A reporting issue inside GA4 points teams towards GA4 settings, while a Google Ads conversion issue points them towards the relevant Google Ads consent signals.
What Google Signals now controls in GA4
Google Signals now has one job. It associates GA4-sourced data with signed-in users for behavioural reporting, nothing else.
It still exists in GA4, but its role has narrowed considerably, and it no longer controls Google Ads cookies and IDs the way it once did.
It remains useful for GA4 reporting, but it can no longer stand in for Google Ads Consent Mode.
Google has also flagged a second change coming later in 2026.
The ad_personalization settings currently spread across account, property, Ads link and event levels in GA4 will move exclusively to Google Ads consent controls once Google confirms a date.
How the GA4 and Google Ads Separation Changes Each Signal
Each Consent Mode signal now needs to be understood on its own terms.
Google defines ad_storage, the signal driving most of this change, as the consent type that enables storage related to advertising, such as cookies or device identifiers.
It’s one of four Consent Mode signals, each set out below.
| Consent signal | What it controls |
| ad_storage | Advertising-related storage, including cookies and device identifiers |
| ad_user_data | Sending user data to Google for advertising purposes |
| ad_personalization | Personalised advertising |
| analytics_storage | Analytics-related storage, including cookies and device identifiers |
How the four consent signals differ
The four signals split into two jobs.
Two control whether Google can use storage at all, covering ad_storage and analytics_storage, and two control what Google does with the data once it has consent, covering ad_user_data and ad_personalization.
A properly configured setup keeps all four choices separate rather than treating consent as one switch:
- Advertising storage (ad_storage) and analytics storage (analytics_storage) can be granted or denied independently, so a visitor can accept analytics while declining advertising.
- When storage consent is denied, Google can still use cookieless pings to support measurement and modelling, avoiding a total loss of signal.
- User-data consent (ad_user_data) covers measurement uses such as enhanced conversions and tag-based conversion tracking.
- Personalisation consent (ad_personalization) covers features such as remarketing, which stop receiving data once it’s denied.
How to trace a consent issue across GA4 and Google Ads
Trace a tracking problem to the platform where it actually shows up.
A drop in GA4 behavioural reporting does not automatically point to Google Ads, and a change in Google Ads conversions does not automatically point to Google Signals.
Tracing the data from the user’s choice through to reporting shows where each control applies:
User choice → consent management platform → Google Consent Mode → Google tags → GA4 and Google Ads → reporting
Google Ads Consent Signals and Advertising Data
Consent settings affect what Google can store, receive and use, directly shaping campaign measurement and data quality.
When ad_storage is denied, Google restricts advertising-related storage.
It can still receive certain information through Consent Mode, but the resulting data path differs from a fully consented journey.
A missing cookie does not necessarily mean a missing measurement signal, since some information can still contribute to Google’s modelling systems even when other identifiers and storage are unavailable.
How consent choices affect conversions and remarketing
Consent choices reshape what Google Ads can measure for both conversions and remarketing, though in different ways.
On the conversion side, consent restrictions affect how much conversion data Google Ads can directly observe.
When ad_user_data consent is denied, affected data flows may be restricted, though Consent Mode modelling can help account for part of what direct tracking misses.
Eligibility requires a correctly implemented Consent Mode, or the qualifying IAB Transparency & Consent Framework, on top of the click threshold covered earlier.
Below that threshold, some journeys stay unobserved, which is worth remembering when comparing Google Ads reporting against CRM or revenue data.
Remarketing depends on personalised advertising consent, so audience behaviour should be tested separately from conversion tracking.
A campaign can still record measurable conversions while personalised audience activity becomes more restricted, and those outcomes should not be treated as the same technical problem.
What advertisers should review
The review should cover the full tracking stack, well beyond the consent banner.
A thorough data and ad campaign audit checks the consent management platform, Google Tag Manager, GA4, Google Ads, conversion actions, enhanced conversions, remarketing audiences, the GA4-to-Google Ads link, and reporting.
The key question is whether the data path matches the consent decision at every stage. Treating any one of these systems in isolation risks missing where the mismatch actually is.
Auditing Your Google Consent Mode Changes
A useful audit follows the real data path and tests different consent choices. A single green tick in Tag Assistant is a starting point, not proof the setup works end to end.
Verify your Google Consent Mode implementation
Google recommends using Tag Assistant to check Consent Mode, confirming ad_storage, ad_personalization, ad_user_data and analytics_storage across four checks:
- The default consent state loads at the correct time.
- The user’s selection reaches Google.
- A later consent change updates the signals.
- Tags respond correctly to the resulting state.
Confirm ad_storage reflects user consent
Test both accepted and denied advertising consent, confirming storage is restricted when ad_storage is denied, then test preference changes and returning visitors.
The question is whether the consent platform and Google tagging stay aligned throughout the journey.
Review each Consent Mode signal separately
For GA4, check analytics storage, behavioural reporting and Google Signals. For Google Ads, check advertising storage, user-data consent, personalisation, conversions and audiences.
A complete Google consent mode changes audit verifies all four core signals, not just ad_storage. Map your CMP’s consent categories deliberately to these four parameters:
- ad_storage matches advertising storage consent
- analytics_storage matches analytics storage consent
- ad_user_data reflects permission for advertising-related user data
- ad_personalization reflects permission for personalised advertising
Test conversion tracking and audience behaviour
Test real journeys across different consent states, then compare the outcomes in GA4 and Google Ads:
- Granted consent: verify expected conversion and audience behaviour.
- Denied consent: verify that storage, data use and personalisation are restricted as expected.
- Changed consent: verify the updated state reaches Google and tags respond correctly.
Document your consent configuration
Once the implementation passes testing, document it, listing the CMP settings, Consent Mode defaults, Google Tag Manager, GA4 and Google Ads configuration, and testing results.
This becomes useful when a website is redeveloped, an agency changes or someone edits the tracking container months later.
Google Ads Consent Signals Checklist for Advertisers
Use this checklist to confirm your consent implementation and downstream advertising data stay aligned:
Google Ads consent signals audit:
☑ ad_storage reflects the user’s advertising consent
☑ analytics_storage reflects analytics consent
☑ ad_user_data reflects the relevant advertising data consent
☑ ad_personalization reflects the user’s personalisation choice
☑ Google Signals is reviewed separately within GA4
☑ GA4 and Google Ads have been tested independently
☑ Conversion tracking has been tested across consent states
☑ Remarketing behaviour has been tested
☑ Consent updates reach Google correctly
☑ Configuration and test results are documented
Treat Consent Signals as Part of Your Measurement Stack
The June 2026 Google Ads consent signals update is about understanding the new separation between GA4 and Google Ads, then verifying that your consent configuration reflects it.
Most tracking implementations will not need a full rebuild.
Google Signals still shapes GA4 behavioural reporting. Google Ads Consent Mode now governs the Google Ads data flow from linked properties.
For organisations using Google Ads data to allocate budgets, measure acquisition, and assess campaign performance, consent belongs within the measurement system, right alongside the metrics it shapes.
Report quality depends on the data flow behind it, which means testing consent signals, checking destination-specific behaviour and documenting the configuration.
Tell No Lies is a data and analytics consultancy that helps agencies and businesses manage GA4, Google Tag Manager, data engineering and campaign data audits.
The objective is simple. Know what data you collect, know what each Google Ads consent signal permits, and verify that the numbers used to make decisions reflect the underlying data.
Trustworthy Google Ads reporting starts with trustworthy consent data.
Contact us today for a full audit of your consent and tracking setup.