Data Thresholding

Data thresholding is GA4 withholding rows from a report when the numbers are small enough that a single person could, in theory, be identified. It's a privacy safeguard, triggered most often when Google Signals is switched on. The data isn't wrong or deleted — it's hidden, and GA4 marks the report with a small warning icon to tell you so.

Why it matters

For a small business with modest traffic, thresholding bites hard. Low-volume reports are exactly the ones where it kicks in, so the segments you most want to understand — a specific city, age band, or niche landing page — are often the ones GA4 quietly blanks out. You end up with totals that don't add up to the sum of their visible parts, and no obvious reason why.

A concrete example

Say you check which cities your visitors came from last week. The total says 200 users, but the listed cities only account for 150. The missing 50 weren't lost — they're spread across small cities where the per-row count fell below GA4's threshold, so each of those rows was suppressed. The data exists; GA4 just won't show it at that level of detail.

The common misreading

The mistake is reading a thresholded report as "we got no traffic from there." A blank row means hidden, not zero. To recover the numbers, switch the property's reporting identity to Device-based, which turns off Signals-driven thresholding, or widen the date range so each row clears the threshold. Watch for the same suppression in the (other) row.