Google Signals, Google Ads, and the Consent Mode Shift: What Marketers Actually Need to Understand

Quick read: Google is changing how Google Signals works with Google Ads. Starting June 15, 2026, Google Signals in GA4 will no longer serve as the control governing Google Ads cookies and IDs collected through the Google Analytics tag and SDK. For linked GA4 and Google Ads properties, use of Google Ads data will be governed by Google Ads settings and Consent Mode. In contrast, Google Signals will primarily govern how GA4-sourced data is associated with signed-in Google user information for behavioral reporting in GA4.

Your reports will still load. Your campaigns will still run. But the control logic behind measurement, audience targeting, remarketing, and ad personalization is changing in meaningful ways. For example, remarketing candidates who checked out your product on one device may not be followed by your remarketing ad when they're on another device. So the lists may shrink—deep-dive to explore more.

First, what was Google Signals supposed to do?

Quick read: Google Signals helped GA4 use data from signed-in Google users (signed in to their Google Account in Chrome, Android, YouTube, etc.) with Ads Personalization enabled. This made features like cross-device remarketing, demographics and interests, and cross-device key event export to Google Ads possible in eligible cases.

Google Signals was introduced as a bridge between website behavior and Google's signed-in ecosystem. When a user was signed in to a Google account and had Ads Personalization enabled, Google could aggregate and privacy-control session data from sites and apps for that signed-in user. Google's own documentation says Google Signals enables cross-device remarketing and cross-device key event export to Google Ads. It also supports reporting on demographics and interests within Analytics.

For a marketer, the practical meaning was simple. A person could browse a pricing page on mobile, then come back later on a laptop, and Google might sometimes infer that these two interactions belong to the same broad user journey. This won't be 100% accurate, and you may not be notified about that particular user. Still, it's enough to make GA4 and Google Ads better at remarketing, conversion attribution, and user journey reporting.

That is why Google Signals became one of those settings that performance marketers learned to check early. New GA4 property? Check the data stream. Check key events. Link Google Ads. Enable Google Signals. Check audiences. Google Signals gave access to that additional set of audiences and an opportunity to drive more sales from them.

But Signals worked only for eligible users; it was affected by region settings, ad personalization status, consent, account linking, thresholding, and Google's privacy rules.

What has happened now?

Quick read: Google is separating controls based on where data is used. GA4 settings will control the data used within GA4 behavioral reporting. Google Ads settings, especially Consent Mode signals, will control data used in Google Ads.

Google has announced an update to Google Analytics data controls. Starting June 15, 2026, the Google Signals setting in GA4 will only control how GA4-sourced data is associated with a signed-in Google user for behavioral reporting. Google Signals is being demoted from being one of the controls for Ads-related data collection and use. It still matters inside GA4. But for Google Ads, the main ad privacy controls are moving to Consent Mode and Ads Settings.

Earlier, when GA4 was linked to Google Ads, data flowed from Analytics to Ads. However, some use of that data in Ads was still affected by GA4-side controls, including Google Signals and ad personalization settings. Google now wants to remove that overlap. If the data is being used in Google Ads, Google Ads controls should govern it. If the data is being used in GA4 reporting, GA4 controls should govern it.

This is the core shift. It sounds administrative, but it has real implications. Many marketers think in terms of features, such as remarketing, conversions, audiences, and Smart Bidding. Google is thinking in terms of governance boundaries. Where is the data used? Which product owns the consent decision? Which setting should enforce user choice?

Why have Google Signals and Google Ads been disconnected?

Quick read: Google has officially announced it is reducing duplicate controls between GA4 and Google Ads by consolidating them based on where the data is used. It has also been said that the change is meant to simplify consent handling and to enforce user preferences more consistently across Google Analytics and Google Ads. A broader shift in privacy governance is a reasonable interpretation, but Google has not framed it quite that directly in the announcement.

There was a time when digital advertising was mostly about cookies, clicks, and conversions, while consent was a good-to-have feature. But today, consent and privacy rules are central to advertising needs.

Google says the change is meant "to simplify data controls and remove redundant settings between Google Analytics and Ads." It also says controls will be consolidated based on where the data is used, with Google Ads settings controlling Google Ads data, including data shared by GA4, and GA4 settings controlling data used inside GA4 behavioral reporting.

But there is a bigger context. Google's EU User Consent Policy has existed since 2015 and reflects requirements from European privacy rules, including the ePrivacy Directive and GDPR. In 2024, Google also began pushing stronger adoption of Consent Mode for advertisers targeting users in the European Economic Area. Google added two Consent Mode parameters, ad_user_data and ad_personalization, so that advertisers could send clearer consent signals for measurement and advertising use.

The industry used to rely heavily on cookies and platform identity. Then, Google introduced Consent Mode to help Google tags adapt to users' choices. The tags today are often combined with a consent management platform banner. User choices are passed to Google Tag Manager for either restricted or unrestricted data capture. Then Consent Mode v2 added more specific advertising consent signals. Now Google is aligning product controls so that Ads consent settings govern Ads use, not a mix of Ads settings and GA4 switches.

The old structure had a governance problem and a logical one as well. An analytics product governs how an ad platform uses data, and an ad platform is linked to an analytics product beyond data analysis.

Why is Google Signals getting cleaned now?

Quick read: Because the advertising ecosystem is being forced to formalize consent. Consent is no longer a banner requirement. It is now part of the measurement and bidding infrastructure.

The timing makes sense when you look at the last few years. GA4 replaced Universal Analytics as Google's main analytics platform. Consent Mode became more central to both Analytics and Ads. Regulators became more aggressive about how large platforms combine and use data. Advertisers became more dependent on modeled conversions, enhanced conversions, first-party data, and automated bidding. In short, the old messy system had to grow up.

Google Ads relies heavily on conversion for bidding and campaign optimization. Search campaigns, Performance Max, YouTube campaigns, Demand Gen, and remarketing setups perform better when measurement inputs are clean and have consent. If the consent signal is unclear, Google has to limit data use.

Consent Mode is Google's preferred answer to this problem. In basic Consent Mode, tags wait until the user interacts with the consent banner. If the user denies consent, no data is sent to Google, not even the consent status. In advanced Consent Mode, tags load with default consent states, usually denied, and send cookieless pings when consent is denied. Google says advanced Consent Mode enables more detailed, advertiser-specific conversion and key-event modeling, while basic Consent Mode relies on a more general model when users do not consent.

What about remarketing?

Quick read: Eligibility for remarketing depends on consent, first-party data setup, user-provided data collection, Google Ads settings, audience rules, and product linking. Google Signals will no longer be the central Ads side control in the same way.

GA4 audiences can still be shared with linked advertising products. Google's documentation explains that Analytics audiences can be used in Google Ads as remarketing lists or audience segments. Google also states that when GA4 is linked to Google Ads, advertisers can re-engage users based on site or app behavior.

But the important detail is eligibility. Remarketing is not just "make audience, show ad." For Analytics-based remarketing, Google's docs say at least one of the following must be active for the property: Google Signals or user-provided data collection. Google Signals documentation also says remarketing features based on consented first-party data do not require Google Signals to be activated.

This tells us the direction. The industry is moving from third-party advertising identifiers and broad platform signals to consented first-party data and explicit consent states.

Here is a realistic example. A freelance marketer runs lead generation campaigns for a training business. They create a GA4 audience for users who viewed the course page, watched 50 percent of the promo video, and did not enquire. If Consent Mode is properly implemented and personalization consent is granted, that audience can be used with greater confidence in Google Ads. If consent is denied, those users should not be used for personalized remarketing. The audience size may look smaller, but it is cleaner. Painful, yes. But cleaner.

What about Smart Bidding and conversion modeling?

Quick read: Smart Bidding depends on conversion signals. Consent Mode helps Google deal with measurement gaps through modeling, but the quality of your setup affects the quality of the inputs. Bad consent implementation can damage both reporting and optimization.

Google Ads bidding systems learn from conversion data. If your conversion tracking is incomplete, delayed, or duplicated, bidding gets weaker inputs. The consent mode adds to this conversion data. If visitors restrict your data collection by disallowing consent, this may affect conversion data.

Consent Mode changes tag behavior based on user choices. Basic Consent Mode can support general modeling when users do not consent, and tags are blocked. Advanced Consent Mode can send cookieless pings while consent is denied. It may support advertiser-specific modeling if thresholds are met.

To someone, it may seem that Google's modeling can very accurately replace missing data. It is not entirely true. It can help mitigate gaps. However, this depends on implementation quality, consent signals, and Google's own privacy thresholds.

For a small B2B SaaS account with 20 demo requests a month, the impact may be very different from an ecommerce account with thousands of purchases. The B2B account may not have enough volume for some forms of useful modeling.

Google Signal Shift: What should marketers audit?

Quick read: Audit your GA4 and Google Ads link, Consent Mode v2 setup, CMP behavior, audience exports, key event imports, privacy wording, and regional settings.

Start with the GA4 and Google Ads link. Confirm which Google Ads accounts are linked and whether personalized advertising is enabled where appropriate. Check if key events are being imported into Google Ads for bidding or reporting. Google's linking documentation says linking makes GA4 data available in Google Ads, but the action still requires creating Google Ads conversions from GA4 key events or adding audiences to campaigns.

Then inspect Consent Mode. Use Tag Assistant, GTM preview mode, browser developer tools, and your CMP debug tools. Check the default consent state before banner interaction. Check what happens when the user accepts. Check what happens when the user rejects. Check whether ad_user_data and ad_personalization are actually updating.

Next, review GA4 audiences that are shared with Google Ads. Identify which campaigns use them for targeting, observation, exclusions, or remarketing. Some audiences may rely solely on behavioral rules. Others may rely on demographics, interests, or personalization settings. Make a list because you will not remember which one was used in that old YouTube campaign from six months ago.

Finally, review your privacy policy and cookie banner wording. If your internal documentation says Google Signals controls Ads identity use, update it. If your banner says users can opt out of ad personalization, but your Consent Mode does not send ad_personalization correctly, fix it.

Google Signal Shift: What is the real risk?

Quick read: The risk is not only lost tracking. It is mismatched consent, incorrect assumptions, broken audience use, weaker bidding inputs, and privacy documentation that no longer matches actual product behavior.

The biggest risk is forgotten settings. Many accounts are held together by settings someone configured months or years ago, and they have not been reviewed since then. Google Signals enabled? Good. GA4 linked? Good. Conversions imported? Good. But after this update, those checks are not enough.

If Consent Mode is missing, you may lose measurement quality in regions where consent signals are required. If Consent Mode is present but misconfigured, you may send signals that do not reflect the user's actual choice.

Another risk is audience shrinkage or inconsistent audience behavior. If ad personalization consent is denied for many users, remarketing audiences may be smaller. The uncomfortable part is that some advertisers have been judging remarketing health by audience size alone. Under the newer model, audience quality and permission status matter more than raw size.

Inconsistencies may arise between GA4 behavioral reports, Google Ads conversion data, and BigQuery exports. For instance, Google Signals and BigQuery often diverge in cross-device user counts because GA4 exports event data alongside pseudonymous cookies.

So what should you do next?

Quick read: Treat this as a measurement governance update. Your next step is checking whether your consent, tagging, linking, audiences, and privacy documentation all say the same thing.

If you manage client accounts, this is also a good time to explain the change before clients ask why remarketing lists, modeled conversions, or Ads diagnostics look different. The best client conversation is the one where you sound prepared, not the one where you say, "Google changed something again".

That is less glamorous than a new campaign hack. But it is much more useful. And in 2026, useful beats glamorous almost every time.

Sources and further reading

Google Analytics Help, Updates to Google Analytics Data Controls: https://support.google.com/analytics/answer/17016975?hl=en

Google Analytics Help, Activate Google Signals for Google Analytics properties: https://support.google.com/analytics/answer/9445345?hl=en

Google Ads Help, About Consent Mode: https://support.google.com/google-ads/answer/10000067?hl=en

Google Ads Help, Adapt to privacy and regulatory changes with Consent Mode: https://support.google.com/google-ads/answer/14505993?hl=en

Google Analytics Help, Connect Google Ads to Google Analytics: https://support.google.com/analytics/answer/9379420?hl=en

Google Analytics Help, Share audiences in Google Analytics with your linked advertising products: https://support.google.com/analytics/answer/12800258?hl=en