Skip to content
A/MR

Analytics · · 2 min read

GA4 Can Withhold Rows When Counts Are Too Small: Google Says Data Thresholds Are System Defined and You Can’t Adjust Them

Diagram: GA4 data thresholds are system defined and cannot be adjusted; demographic data, search query rows and too few users can lead to rows or cards being withheld; a wider date range may reveal them

hi, i’m amr. when a ga4 report shows fewer rows than you expect, the first guess is a filter or a tagging bug. google’s help page names another cause that no setting will fix.

what google says, in its own words

  • “Data thresholds are system defined. You can’t adjust them.”
  • the purpose is privacy: thresholds exist so nobody can infer “the identity or sensitive information of individual users based on demographics, interests, or other signals”
  • “Data may be withheld when viewing a report or exploration or making an API call that includes demographic data”
  • for search query information, “the row containing that data may be withheld if there aren’t enough total users”
  • when it happens, a message at the top of the report says “Google Analytics has applied thresholding to one or more cards in this report”
  • “Expanding the date range may increase the number of users who triggered an event,” which can reveal data that was withheld

my reading, not google’s wording: a report that mixes demographic breakdowns with a small campaign or a short date range is the setup most likely to lose rows.

what to check this week

  • open the reports your clients read most and look for the thresholding message at the top
  • where it appears, widen the date range before you change anything else, then compare
  • if a number looks too low, check whether the report includes demographic data before you suspect tracking
  • when you compare two exports, make sure both used the same date range and breakdowns. i covered another limit that changes what you can build in a ga4 exploration in an earlier post

where this stops applying

the page gives no minimum user or event count, so this post names none. it also says nothing about how large a campaign has to be to avoid thresholding. i haven’t audited any property, so the list above is a starting point.


start scaling — if your ga4 numbers keep changing between exports, a short reporting review usually finds the cause. let’s connect.

Sources: Google Analytics Help, “[GA4] About data thresholds” (support.google.com/analytics/answer/9383630). Figures are published product documentation, not verified results from Amr’s own client accounts.

Leave a reply