Data Thresholding

Data thresholding is GA4 automatically hiding rows of data when the volume is too low, so no individual user can be identified from the report.

You open a report and see "a data threshold was applied," which means GA4 withheld some rows because the underlying counts were small enough that a person could theoretically be singled out. It happens most often when a report includes demographic or interest data, or when Google Signals is contributing to the identity, since both narrow groups down toward individuals.

You segment last week's conversions by age and city and get a near-empty table. The purchases happened, but each age-and-city cell held only a handful of users, so GA4 suppressed those rows to protect identity and your totals no longer reconcile with the unsegmented report.

You cannot switch thresholding off, but you can stop triggering it. Set the reporting identity to device-based and remove demographic dimensions from the view, and the suppression usually disappears because the data is no longer tied to Google-identified people. Many analysts assume the data is missing or broken; it is present, just hidden by the privacy filter.

The numbers are there. The threshold just refuses to show them to you.