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?

The cause is that the Page path dimension has too many unique values, exceeding the report's row limit. Standard reports can only hold a certain number of distinct dimension values, and on a large ecommerce site page paths run into the tens or hundreds of thousands. Once that limit is reached, the remaining values are bundled into an '(other)' row so the totals stay accurate even though the individual rows are not listed. High-cardinality dimensions such as page path, page title with query parameters, and product IDs are the usual culprits. The workarounds are practical: analyse the same data in an exploration, which handles the detail differently, narrow the report with filters or a shorter date range, or look at a grouped dimension such as page path level rather than the full path.