Google Signals

Google Signals is session data that Google Analytics collects from visitors who are signed in to a Google Account and have Ads Personalization turned on. It lets GA4 recognize the same person across devices and adds age, gender, and interest data to your reports. It is off by default and has to be switched on in the property’s data collection settings.

The data comes from Google’s own account records rather than from your site. That is the source of both its value and its restrictions.

What Google Signals Unlocks

Four features depend on it, and none of them work without it.

• Demographics and interests reports. Age brackets (18-24, 25-34, 35-44, 45-54, 55-64, 65+), gender, and affinity or in-market interest categories.
• Cross-device reporting. Sessions from the same signed-in Google user on a phone and a laptop merge into one user rather than two.
• Remarketing audiences in Google Ads. GA4 audiences can reach the same person on a different device.
• Cross-device conversions. Google Ads can credit a conversion that started on one device and finished on another.

Everything else in GA4 works fine without it. Traffic acquisition, events, conversions, and campaign reporting are unaffected by the setting.

How Google Signals Works

GA4 matches your site’s activity to a signed-in Google identity when three conditions hold at once.

1. The visitor is signed in to a Google Account.
2. That account has Ads Personalization enabled.
3. Google Signals data collection is switched on in your GA4 property.

When all three are true, Google stitches sessions across devices using its own account identifier rather than the browser cookie. When any one fails, the visit falls back to standard device-level measurement.

Coverage is partial by design, and Google publishes no figure for what share of traffic it matches. It varies by audience: consumer sites with a heavy Android and Chrome mix see far more matching than a B2B site whose visitors browse in signed-out work profiles. Treat demographic reports as a sample of your audience, never as a census of it.

How to Enable Google Signals in GA4

1. Open Admin in the bottom left of GA4.
2. Under Data collection and modification, select Data collection.
3. Find Google signals data collection and click to expand it.
4. Toggle it on and confirm.
5. Confirm you meet the disclosure obligations described below before you leave the screen.

The setting applies at property level and takes effect going forward only. Demographic reports stay empty for historical dates and start filling within 24 to 48 hours.

Turning it back off stops collection from that point. It does not delete data already collected, which remains subject to your property’s retention setting.

Google Signals and Thresholding

Turning on Google Signals is what introduces data thresholding to most GA4 properties. This is the trade nobody warns you about.

Thresholding withholds rows when the number of users behind them is small enough that someone could be re-identified from demographic or interest data. Once Google Signals is on, any report that touches age, gender, or interests can hide rows, and an audience built on a demographic condition carries that restriction wherever it is used.

Two related details are worth knowing. Google removed Google Signals from the reporting identity setting in February 2024, specifically to reduce thresholding, so switching reporting identity no longer exempts a report. And Google Signals data is never included in the BigQuery export, so demographic fields are simply absent there.

Google Signals and Privacy

Enabling it puts you under Google’s Advertising Features policy, which sets three obligations.

• Disclose it. Your privacy policy must state that you use Google Analytics Advertising Features, and that Google collects data through advertising cookies and identifiers.
• Offer an opt-out. Point users to Google’s Ads Settings and the Google Analytics opt-out browser add-on.
• Get consent where the law requires it. In the EEA and UK, Google Signals depends on the ad_user_data consent signal. Deny it and no signals data is collected for that user, whatever the property setting says.

Google Signals is not a workaround for consent. It collects less when consent rates are low, not more.

Should You Turn On Google Signals

Turn it on when you need one of the four features it unlocks, most often demographic reporting for audience research or cross-device remarketing in Google Ads.

Leave it off when your reporting depends on complete, unthresholded rows, when BigQuery is your source of truth, or when your legal position favors collecting the minimum. A B2B property whose visitors rarely browse signed in gets thin demographic data and a thresholding problem in exchange.

A middle path works for most teams: turn it on for a defined research period, pull the demographic picture you need, then decide whether the ongoing thresholding cost is worth it.

Frequently Asked Questions

What is Google Signals in GA4?

Google Signals is data Google Analytics collects from visitors signed in to a Google Account with Ads Personalization enabled. It powers demographics and interests reports, cross-device reporting, cross-device conversions, and remarketing audiences in Google Ads. It is a property-level setting that is off until you enable it.

How do you enable Google Signals in GA4?

Go to Admin, then Data collection and modification, then Data collection. Expand Google signals data collection and switch it on. The change applies from that moment forward, so historical dates stay empty and new demographic data appears within a day or two.

Does Google Signals cause thresholding?

Yes, and it is the most common cause of thresholding in GA4. Any report or audience touching age, gender, or interest data can have rows withheld once Google Signals is active. Turning the setting off removes that trigger, and removes the demographic reports along with it.

Is Google Signals GDPR compliant?

It can be used lawfully, but it is not compliant by default. You must disclose the use of Advertising Features in your privacy policy, provide an opt-out, and obtain consent where required. Under Consent Mode, ad_user_data must be granted before any signals data is collected for a user in the EEA or UK.

Should I turn on Google Signals?

Turn it on if you need demographic reporting or cross-device remarketing and can accept thresholded rows. Leave it off if you rely on complete reports, work primarily in the BigQuery export, or serve an audience that rarely browses signed in to Google. Nothing else in GA4 breaks when it stays off.

Campaign source data does not depend on Google Signals at all, so keep tagging links and reading click data in linkutm alongside your GA4 reports.