Are your GA4 reports showing fewer users than you actually have? Could misconfigured privacy settings be silently breaking your cross-device data? If you rely on GA4 for business decisions, these questions deserve serious attention.
Google Signals and Consent Mode are two distinct features inside GA4. Each handles a different part of user tracking and data collection. Google Signals focuses on recognising signed-in users across devices. Consent Mode manages how tags behave based on a visitor’s cookie choices. When both are set up correctly, GA4 delivers richer, more accurate reports without stepping outside privacy boundaries.
This blog breaks down how Google Signals and Consent Mode function individually and as a connected system within GA4. You will learn how they influence cross-device tracking, behavioural modelling, audience building, and data accuracy. Whether you manage analytics, run ad campaigns, or oversee compliance, this guide covers what you need to configure, why it matters, and what changes arrived in 2026.
Google Signals is a data collection feature that connects user activity across multiple devices when those users are signed in to their Google accounts.
When a visitor browses your website while signed in to Google, GA4 can link their sessions across phones, tablets, and desktops. This only works if the user has enabled Ads Personalisation in their Google account settings. GA4 then associates multiple device sessions with a single user identity, rather than counting each device as a separate visitor.
Without Google Signals, GA4 relies on device-level identifiers. That means a single person using a laptop in the morning and a phone in the evening appears as two separate users. Google Signals resolves that by connecting signed-in sessions to one recognised profile.
GA4 uses Google Signals data to build richer audience segments. These segments reflect actual user behaviour across devices rather than fragmented, device-specific interactions. For businesses running Google Ads, this means remarketing lists are more precise and reach the right people on the right device.
Demographics and interest reports in GA4 also rely on Google Signals. Without it enabled, those reporting dimensions remain empty. If your team uses these reports for campaign planning or content strategy, Google Signals activation is essential.
It is important to understand that Google Signals does not manage cookie storage. It does not decide whether a tracking cookie is placed on a visitor’s browser. That responsibility belongs to Google Consent Mode v2. Google Signals only handles identity resolution for users who are already signed in and have opted in to Ads Personalisation.
Google Consent Mode is a framework that adjusts how Google tags fire based on the consent choices a visitor makes through a cookie banner.
Consent Mode operates using four key parameters. Each one controls a different aspect of data collection and usage.
When a user grants consent, all parameters are set to ‘granted’, and tags fire normally. When consent is denied, tags adjust their behaviour. GA4 sends cookieless pings instead of full tracking data. These pings contain limited information but still allow Google to apply behavioural modelling.
In Basic mode, Google tags do not fire at all until a user grants consent. No data reaches GA4 from users who decline. In Advanced mode, tags fire with limited functionality even when consent is denied. This is the mode that enables GA4’s behavioural modelling, because it still collects anonymised, cookieless pings.
For most businesses that want both compliance and usable analytics data, Advanced mode is the practical choice. It respects user consent while keeping enough data flowing for GA4 to model what it cannot directly measure.
Consent Mode decides whether cookies are stored on a device. It governs whether advertising data is collected and shared with Google Ads. It also determines whether GA4 can use full cookie-based tracking or must fall back to cookieless pings. Google Signals has no role in any of these decisions.
These two features handle different layers of GA4’s data collection. When both are properly configured, they create a system that balances privacy with data depth.
Consent Mode acts as the gatekeeper. It determines what data GA4 can collect based on each visitor’s cookie preferences. If analytics_storage is granted, GA4 tracks the session fully. If denied, GA4 receives limited pings and relies on modelling to fill the gaps.
Google Signals adds a second layer. For users who are signed in to Google and have Ads Personalisation enabled, it enriches GA4 data with cross-device identity resolution. But it can only work when Consent Mode has already allowed the underlying data collection.
Consent Mode runs first. If a visitor denies consent, Google Signals cannot activate for that session. There is no signed-in identity to link because the tracking mechanisms are restricted. Google Signals depends on Consent Mode granting permission before it can do its job.
This means that a high consent denial rate directly reduces the pool of users available for cross-device tracking through Google Signals. Businesses that invest in clear, well-designed cookie consent banners tend to see higher consent rates, which in turn unlocks more Google Signals data.
When both features are active and correctly configured, GA4 can deliver reports that reflect actual user journeys rather than device-fragmented snapshots. Demographics, interests, and cross-device path analysis all improve. Behavioural modelling fills in data for users who denied consent, while Google Signals enriches data for those who are signed in.
Behavioural modelling is GA4’s method of estimating user activity when direct tracking is not possible due to denied consent.
When Consent Mode is set to Advanced, and a visitor denies cookies, GA4 still receives cookieless pings. These pings carry limited, anonymised signals. GA4 then uses machine learning to compare these signals against patterns from users who did grant consent. The result is a modelled estimate of how the non-consenting user likely behaved.
This modelling covers metrics like session count, page views, and conversion events. It does not fabricate data. It applies statistical patterns from consented users to estimate behaviour among those who declined.
GA4 does not apply behavioural modelling to every property. Your property must meet specific thresholds. It needs at least 1,000 events per day with analytics_storage set to ‘denied’ for a minimum of seven days. It also requires at least 1,000 daily users sending events with analytics_storage set to ‘granted’ for at least seven of the previous 28 days.
Properties that do not meet these thresholds will see gaps in their reports rather than modelled estimates. This makes proper Consent Mode implementation critical for businesses that want complete analytics coverage.
Google Signals and behavioural modelling serve different purposes but complement each other. Google Signals provides observed, identity-based data for signed-in users. Behavioural modelling provides estimated data for users who denied consent. Together, they reduce the overall data gap in GA4 reports.
Google introduced a significant structural change to how GA4 and Google Ads handle data controls, effective from 15 June 2026.
Before June 2026, the Google Signals setting in GA4 influenced both analytics reporting and Google Ads data collection. That dual role created confusion. Many teams assumed that toggling Google Signals on or off also governed how advertising data was shared.
From June 2026, Google Signals only controls signed-in user data for GA4 behavioural reporting and user recognition. It no longer has any authority over Google Ads cookie collection or advertising data flow.
All advertising data collection is now governed by Consent Mode parameters. The ad_storage parameter decides whether advertising cookies are placed. The ad_user_data and ad_personalisation parameters control how that data is used within Google Ads. This shift means that consent mode v2 for Google Ads is no longer optional for any business running paid campaigns.
If your team previously relied on Google Signals settings to manage ad data flow, that approach no longer works. You need to audit your Consent Mode configuration to confirm that all four parameters are correctly mapped to your cookie banner. Failing to do so could result in incomplete conversion tracking, broken remarketing audiences, or non-compliant data sharing with Google Ads.
Proper configuration of both features is essential. A mistake in either setting can silently degrade your GA4 data quality.
Navigate to your GA4 property settings. Under Data Collection, find the Google Signals option and enable it. Once activated, GA4 begins collecting cross-device data from signed-in users. Keep in mind that enabling Google Signals may trigger data thresholds. GA4 applies data thresholds to prevent identifying individual users, which can temporarily reduce visible data in some reports.
GDPR training software should integrate smoothly with your existing systems. Compatibility with HR platforms, learning management systems, and single sign-on solutions reduces friction and simplifies administration. Cloud-based deployment eliminates the need for local installation and IT overhead.
Consider whether the platform supports multiple languages if your organisation operates internationally. Multi-language capability ensures that every employee receives training in a language they fully understand, improving comprehension and compliance outcomes.
After setup, test your configuration using Google Tag Assistant and GA4’s DebugView. Confirm that consent states are passed correctly for both granted and denied scenarios. Check that Google Signals data appears in your demographics and cross-device reports. Verify that behavioural modelling is active by reviewing the data quality indicators in your GA4 property.
Even experienced analytics teams make errors when setting up these features. Here are the most frequent issues and how to avoid them.
Turning on Google Signals without a functioning Consent Mode setup can lead to compliance risks. Google Signals collects data from signed-in users, but without Consent Mode, there is no mechanism to respect cookie preferences. This combination can result in data collection that violates GDPR, the UK GDPR, or other privacy regulations.
Basic Consent Mode blocks all tag firing until consent is granted. While this is compliant, it eliminates all data from non-consenting users. GA4 cannot apply behavioural modelling because it receives no pings at all. Switching to Advanced mode solves this without compromising user privacy.
Teams that have not updated their setup since the June 2026 changes may still rely on Google Signals to manage advertising data. This no longer works. If your GA4 server-side tracking or tag configuration has not been reviewed since this change, now is the time to audit.
Google Signals and Consent Mode serve distinct but connected roles inside GA4. Consent Mode decides what data GA4 can collect. Google Signals enriches that data with cross-device identity. When configured together correctly, they deliver accurate reports, compliant data collection, and stronger audience insights. With the June 2026 changes now in effect, reviewing both settings is no longer optional.
Seers helps you configure Consent Mode correctly so Google Signals can deliver its full value within GA4. Set up compliant tracking, protect your data accuracy, and keep your analytics reporting reliable. No complex setup needed.
START FREE TODAYGoogle Signals handles cross-device identity resolution for signed-in Google users. Consent Mode controls how Google tags behave based on a visitor’s cookie preferences. They address different aspects of data collection. Google Signals identifies users, while Consent Mode determines what data GA4 is allowed to collect and store based on regulatory requirements.
When a visitor denies consent, Consent Mode restricts cookie-based tracking. Google Signals cannot activate for that session because the data collection mechanisms are blocked. GA4 falls back to cookieless pings and uses behavioural modelling instead. Google Signals only works when Consent Mode permits the underlying data collection.
Behavioural modelling is not triggered by Google Signals. It is triggered by Consent Mode operating in Advanced mode. When users deny consent, GA4 receives limited pings and applies machine learning to estimate their behaviour. Google Signals and behavioural modelling serve separate functions and are activated through different settings.
From June 2026, Google Signals no longer controls Google Ads data collection. All advertising data flow is now governed solely by Consent Mode parameters, specifically ad_storage, ad_user_data, and ad_personalisation. Google Signals retains its role for GA4 cross-device reporting and user recognition but has no influence over how ads data is collected or shared.
GA4 requires at least 1,000 daily events with analytics_storage set to denied over a minimum of seven consecutive days. It also needs at least 1,000 daily users with analytics_storage set to granted for at least seven of the previous 28 days. Both conditions must be met simultaneously for modelling to activate.
Advanced mode is the recommended configuration. Basic mode blocks all tag firing until consent is granted, which means zero data from non-consenting users. Advanced mode sends cookieless pings even when consent is denied, enabling behavioural modelling. This pairs well with Google Signals because it maximises the data available for GA4 reporting.
Enabling Google Signals without a functioning Consent Mode setup can create compliance issues. Google Signals collects cross-device data from signed-in users. Without Consent Mode managing cookie preferences, this collection could violate privacy regulations like GDPR or the UK GDPR. Both features must be configured together to maintain compliance.
Google Signals enriches audience segments with cross-device data from signed-in users. Consent Mode ensures this data is collected compliantly. After the June 2026 changes, audience data shared with Google Ads is controlled entirely by Consent Mode parameters. Properly configured, both features help create accurate, compliant remarketing audiences.
Smaller websites may not immediately qualify for behavioural modelling due to GA4’s traffic thresholds. However, enabling both features is still beneficial. Google Signals improves cross-device user recognition even at lower volumes. Consent Mode ensures compliant data collection from day one. As traffic grows, behavioural modelling activates automatically once thresholds are met.
Google Tag Assistant and GA4 DebugView are the primary verification tools. Tag Assistant checks that consent states are passed correctly for each parameter. DebugView shows real-time event data and consent status. Teams should also review GA4 demographics reports to confirm Google Signals data is flowing and check data quality icons for modelling status.
Rimsha ZafarRimsha is a Senior Content Writer at Seers AI with over 5 years of experience in advanced technologies and AI-driven tools. Her expertise as a research analyst shapes clear, thoughtful insights into responsible data use, trust, and future-facing technologies.
Take our Free Cookie Audit and find out
Join 50,000+ websites using Seers.Ai to turn compliance into trust, insights, & measurable business growth.
