How to Remove Thresholding in Google Analytics 4
Seeing your data suddenly vanish in a Google Analytics 4 report can be incredibly frustrating, especially when you know it should be there. This isn't a bug, it's a feature called data thresholding. This article explains what thresholding is and walks you through several practical ways to work around it so you can see your complete dataset.
What is Data Thresholding in GA4?
Data thresholding is a privacy protection measure implemented by Google. It automatically hides rows of data in your reports if the user count for that specific row falls below a certain minimum number. The goal is to prevent you from being able to infer the identity of individual users based on their demographics, interests, or actions on your website.
Think of it like this: if you have a report filtered to show users from a small town who visited a specific page and are of a certain age, and there's only one person who fits that criteria, Google will hide that row. Showing you that one user's data could make it too easy to figure out who they are, especially if you have other pieces of information about your customers.
This protection is automatically triggered when a report or exploration meets two conditions:
- It uses data from Google Signals.
- The number of users in a slice of the data is small.
Google Signals collects data from users who are signed into their Google accounts and have Ads Personalization turned on. This is what allows GA4 to report on valuable demographic data like age, gender, and interests, as well as track users across multiple devices. However, this rich data comes at the cost of thresholding.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
How to Tell if Your Data is Being Thresholded
Identifying thresholding in GA4 is simple once you know what to look for. When viewing a standard report or a custom exploration, look at the top-right corner, right above your charts and tables. You'll see an indicator icon (either a green checkmark or an orange triangle).
If you see the orange triangle icon, your data is being thresholded. Hover your mouse over the icon, and a message will pop up confirming it, often saying something like, "Google Analytics has applied thresholding to one or more cards in this report to protect user privacy."
If you see a green checkmark, it means your report is not being affected. Seeing this discrepancy is the first step toward figuring out how to get your data back into view.
How to Fix GA4 Thresholding by Changing Your Reporting Identity
The most direct way to “remove” thresholding is to change a core setting in your GA4 property called Reporting Identity. This setting tells GA4 how to identify and de-duplicate users. The default option, "Blended," relies on Google Signals, which is the root cause of thresholding. By changing it, you can bypass the privacy controls that trigger hidden data.
Important Note: This change is not retroactive. It only affects data processed from the moment you save the new setting moving forward. Your historical data will still be subject to thresholding if you try to view it.
Here are the step-by-step instructions:
Step 1: Navigate to the Admin Section
Click on the Admin gear icon in the bottom-left corner of your Google Analytics 4 dashboard.
Step 2: Go to Reporting Identity
In the "Property" column (the middle column), scroll down to the "Data Display" section and click on Reporting Identity.
Step 3: Select the "Device-based" Option
You will see a few options for how GA4 can identify users. The "Blended" option, which uses Google Signals, is likely selected. To disable thresholding, you need to change this.
Click the "Show all" button to reveal all available options. Select Device-based from the list.
The Device-based option relies only on the Client ID (a unique identifier stored in the user's browser cookie) to identify users. This method removes the dependency on Google Signals, and therefore, it removes the trigger for thresholding.
Click the Save button at the bottom.
The Main Trade-Off
By switching to "Device-based" reporting, you tell GA4 to ignore Google Signals data for its reports. This successfully stops thresholding, but it comes with a cost. You will lose access to:
- Rich demographic and interest data: Reports will no longer be populated with age, gender, or "Affinity category" information, as this data comes exclusively from Google Signals.
- Cross-device user reporting: Without Signals, GA4 loses the ability to recognize when the same logged-in Google user visits your site from their phone and then later from their laptop. Each device visit will be counted as a separate user, potentially inflating your user counts and making customer journey analysis less accurate.
You must decide what is more valuable for your specific analysis: a complete, non-thresholded dataset, or richer, cross-device demographic data.
Other Tactics to Reduce Thresholding
If changing your reporting identity isn't an ideal permanent solution, you can use these other strategies to view thresholded data in your current reports without making long-term changes.
1. Widen Your Date Range
Thresholding is applied when user counts are low. The simplest way to increase the user count is to expand the time frame of your report. If you're looking at a single day's worth of data and seeing a lot of thresholding, try expanding the date range to a full week or an entire month. With a larger pool of users, fewer of your rows will fall below the privacy minimum.
2. Simplify Your Report or Exploration
Often, thresholding appears when you get too granular with your analysis. Using many filters or adding multiple secondary dimensions (like Town/City, Device Category, and Age) can slice your dataset so thinly that each row represents only a small handful of people.
Try removing some of your filters or secondary dimensions one by one. You may find that removing just one specific dimension is enough to bring the user counts back up and reveal the hidden data.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
3. Use the BigQuery Export
For a more technical but foolproof solution, you can export your raw GA4 event data to BigQuery. The raw event-level data sent to BigQuery is completely unfiltered and not subject to thresholding. This gives you a complete, unmasked view of your analytics data, exactly as it was collected.
The downside is that this requires setting up a Google Cloud account (GA4's export is free within BigQuery's free tier for most small to medium businesses) and using SQL or a connected BI tool to query and visualize the information. It offers the most accurate data but comes with a steeper learning curve.
4. Create a Separate "Reporting" GA4 Property
A sophisticated strategy is to use two GA4 properties in parallel. This gives you the best of both worlds:
- Primary Property: Keep Google Signals active and the Reporting Identity set to "Blended". Use this property for high-level analysis, audience building for Google Ads, and accessing demographic data.
- Reporting Property: Create a second GA4 property that also receives traffic from your site, but set its Reporting Identity to "Device-based". Use this property when you need to dig into granular details without worrying about thresholding hiding your data.
This approach requires a bit more setup but provides the flexibility to choose the right dataset for the job at hand.
Final Thoughts
Navigating data thresholding in Google Analytics 4 is a common challenge, but it's manageable once you understand its purpose as a privacy feature. While you can't truly switch off the mechanism, you can effectively bypass it by changing your property's reporting identity to "Device-based," adjusting your report's scope, or leveraging more advanced tools like the BigQuery export to access your raw, unfiltered data.
Dealing with platform constraints like thresholding is exactly the kind of manual reporting work that eats up valuable time for marketers and analysts. Instead of navigating complex settings and exporting CSVs, we built Graphed to do the heavy lifting for you. We connect directly to your Google Analytics data and allow you to build real-time reports and dashboards using simple, natural language. Just ask, "Show me my top landing pages by conversions this month," and get an instant visualization without worrying about settings or data limits.
Related Articles
How to Create Facebook Ads API for Claude Code
Create a Meta Marketing API access token that never expires, using a system user, so Claude Code can pull Facebook ad reports and manage campaigns.
ClickHouse vs Postgres: When to Switch to Columnar
Comparing ClickHouse vs PostgreSQL means matching storage architecture to workload. Row storage wins for transactions. Columnar wins for scan-heavy analytics.
Google Ads for Orthodontists: Get More Booked Consults
Most orthodontic Google Ads campaigns waste money on low-intent searches. The problem is structure, not the platform.