An analyst is reviewing a standard report for a large eCommerce site and notices a significant portion of their data for the Page path dimension has been grouped into an (other) row. However, when they check the data quality icon, it indicates that the report is 100% unsampled. What’s the cause of the (other) row appearing in this report?
- A secondary dimension was added, which automatically groups less common results.
- The query exceeded the event quota limit, triggering data sampling.
- The Page path dimension has too many unique values, exceeding the report’s row limit.
- The date range selected for the report is too short to populate all the data.
Explanation
The (other) row can appear when a report contains a high-cardinality dimension. Page path often creates many unique values because large sites can have thousands of distinct URLs. Google Analytics may group less frequent dimension values when the number of rows exceeds report limits. This can happen even when the report is unsampled, because cardinality and sampling are different data quality concepts.
Why the other options are incorrect
Short date range is incorrect because a limited date range does not cause values to be grouped into (other).
Secondary dimension is incorrect because adding one can increase complexity, but grouping is caused by cardinality limits.
Event quota sampling is incorrect because the report is unsampled, and sampling is not the cause of the (other) row.
Source for verification
https://support.google.com/analytics/answer/13331684