What Is Google Signals in GA4?

Google Signals is one of the most misunderstood settings in GA4 — partly because it does two distinct things (cross-device reporting and audience building), and partly because enabling it introduces a privacy-related behavior that confuses a lot of analysts: data thresholding. Google Signals uses data from signed-in Google users who have opted into ads personalization to stitch together cross-device sessions and power remarketing audiences. Whether you should enable it depends on what you need from GA4 and what trade-offs you're willing to accept. Here's how it works.

What Google Signals Does

When a user is signed into their Google account and has enabled ads personalization, Google can identify that user across different devices and browsers. Without Google Signals, GA4 treats the same person on their phone and laptop as two separate users. With Google Signals, GA4 can recognize them as one person and stitch those sessions into a continuous journey.

This cross-device stitching serves two functions:

Cross-device reporting. GA4's User reports and cross-device reports show a more complete picture of the customer journey when Google Signals is active. Instead of seeing a mobile session and a desktop session as separate users, you see them as one user with two touchpoints. This improves user count accuracy and session-to-conversion path analysis.

Remarketing audience building. When Google Signals is enabled, GA4 audiences — "users who visited the pricing page," "users who started checkout but didn't convert" — can be shared with Google Ads and include the cross-device user pool. This expands the reach of your remarketing campaigns and improves match rates between GA4 audiences and Google Ads users.

The Data Thresholding Trade-Off

This is where Google Signals gets complicated. When Signals is enabled, GA4 applies data thresholding to reports that include user or session count dimensions alongside demographic or device information. The threshold is Google's privacy protection mechanism: if a report dimension combination would expose data for fewer than a minimum number of users, that row is withheld from the report.

In practice, this means:

• Demographic reports (Age, Gender) may show missing or suppressed rows for low-volume segments
• Explorations that include user-level dimensions may show "Data threshold applied" warnings and reduced totals
• Breakdowns by device category combined with acquisition source may suppress rows for rare combinations

The threshold doesn't affect standard session-level reports like Traffic Acquisition or Pages and Screens when those reports don't include personal demographic dimensions. The impact is concentrated in Explorations and reports that combine user identity dimensions with granular breakdowns.

Who Should Enable Google Signals

Google Signals is worth enabling for most businesses running Google Ads — the audience building capability is the primary reason. If you're using GA4 to create remarketing audiences that feed into Google Ads campaigns, Google Signals is required to make those audiences include cross-device users and achieve competitive match rates.

Specifically, enable Google Signals if:

• You run Google Ads remarketing campaigns and want to build audiences from GA4 behavior data
• Your customers regularly switch between mobile and desktop before converting, and you want cross-device path visibility
• You use the User Lifetime report or other user-centric reporting that benefits from cross-device stitching

Be cautious about Google Signals if your reports are already struggling with data quality and demographic thresholding would add more noise. For very small-volume properties (under 10,000 monthly sessions), the thresholding can suppress a significant portion of your exploration data.

Google Signals and Reporting Identity

GA4 gives you control over how it identifies users across sessions through the Reporting Identity setting in Admin → Property Settings → Reporting Identity. There are three options:

Blended (default): GA4 uses Google Signals data when available, then falls back to device ID. This provides the best cross-device user stitching but introduces the most thresholding.

Observed: GA4 uses only directly observed signals — Google Signals and User-ID (if implemented) — without probabilistic modeling. This is a middle ground.

Device-based: GA4 ignores Google Signals entirely for reporting purposes and uses only device/cookie-based identification. This eliminates thresholding from Signals but also eliminates cross-device stitching in reports. Note: even with Device-based reporting identity, Google Signals can still be enabled for audience sharing to Google Ads — the reporting identity setting only affects how data is shown in GA4 reports.

A practical configuration for most businesses: enable Google Signals (for audience sharing to Ads), but set Reporting Identity to Device-based or Observed to minimize data thresholding in your analysis. This lets you benefit from the Google Ads integration without degrading your report quality.

Google Signals vs. User-ID

GA4 offers two ways to identify users across devices: Google Signals (which uses Google account sign-in data) and User-ID (which uses your own first-party user identifier). If your site has user authentication — a login system that gives each user a unique ID — User-ID is more powerful and more reliable than Google Signals for cross-device tracking.

With User-ID enabled, GA4 can stitch together sessions across any device where the user is logged in to your application — regardless of whether they're signed in to a Google account. This covers a wider portion of your authenticated users and doesn't depend on Google account sign-in rates in your audience.

User-ID also doesn't introduce the same thresholding behavior as Google Signals, making it a better choice for businesses where cross-device reporting accuracy is critical. The implementation requires passing your hashed user identifier to GA4 via the user_id parameter in your GA4 tag configuration, typically via GTM.

Google Signals and Consent

Google Signals data can only legally be collected from users who have consented to analytics and advertising tracking. Under GDPR and similar frameworks, this means Signals should only be active for users who have accepted your cookie consent banner. If your Consent Mode v2 implementation is correctly configured, Google handles this automatically — Signals data is only collected for users who grant analytics_storage and ad_storage consent.

If you're collecting Google Signals data without a consent mechanism in place in EU/EEA markets, that's a compliance issue that needs to be resolved before Signals provides any useful data anyway.

How to Enable Google Signals in GA4

Google Signals is enabled in your GA4 property settings: Admin → Property Settings → Data Collection → Google Signals data collection → Get Started. The setup wizard confirms that you have a privacy policy in place and walks through the activation. Once enabled, it typically takes 24–48 hours for cross-device data to begin appearing in reports and for audiences to become available for Google Ads sharing.

After enabling Signals, review your Reporting Identity setting (Admin → Property Settings → Reporting Identity) and decide whether Blended, Observed, or Device-based best suits your reporting needs. For most advertisers, the combination of Signals enabled + Device-based reporting identity gives you Google Ads audience access without degrading your core GA4 reports.

If you're unsure how Google Signals, User-ID, and Consent Mode interact in your specific setup, our GA4 implementation service configures all three correctly as part of a complete property setup.

Frequently Asked Questions

What is Google Signals in GA4?

Google Signals is a GA4 feature that uses data from signed-in Google users who have opted into ads personalization. When enabled, it allows GA4 to stitch together sessions from the same user across different devices, enabling cross-device reporting and making GA4 audiences available for Google Ads remarketing campaigns.

Does Google Signals cause data thresholding in GA4?

Yes. When Signals is enabled and your reporting includes dimensions that could identify small user groups — age, gender, interests, device type — GA4 suppresses rows with insufficient user counts to protect privacy. This shows as "Data threshold applied" warnings in Explorations. You can reduce the impact by setting Reporting Identity to Device-based, which preserves Signals for audience sharing without applying the same thresholding to reports.

Should I enable Google Signals in GA4?

Enable Google Signals if you run Google Ads remarketing and want to build audiences from GA4 behavior data — the cross-device audience matching is the primary use case. Set Reporting Identity to Device-based to minimize report thresholding. If your site has user authentication, also implement User-ID as a more complete cross-device identifier that doesn't depend on Google account sign-in rates.