Summary
The Page path dimension has too many unique values, exceeding the report's row limit. GA4 standard reports are built on pre-aggregated tables with a fixed number of rows, so the least common page paths are combined into a single (other) row. This is a cardinality limit, not sampling, which is why the data quality icon still shows 100% unsampled data.
Nitin Batra is a Google Analytics 4 certified analyst who configures GA4 properties for large eCommerce sites and regularly resolves high-cardinality and (other) row issues using URL parameter exclusions, Explorations and the BigQuery export.
Last updated: August 16, 2026
The (other) row appears because the Page path dimension has too many unique values, exceeding the report’s row limit, so GA4 aggregates the least common paths into a single (other) bucket even when the report is 100% unsampled.
- A secondary dimension was added, which automatically groups less common results.
- The query exceeded the event quota limit, triggering data sampling.
- The date range selected for the report is too short to populate all the data.
- The Page path dimension has too many unique values, exceeding the report’s row limit.
The correct answer is: The Page path dimension has too many unique values, exceeding the report’s row limit.
Key Takeaways
- – The (other) row appears because the Page path dimension has too many unique values, exceeding the report’s row limit.
- – GA4 standard reports read from pre-aggregated tables, so once unique values cross the limit the least common rows are combined into (other).
- – High cardinality and sampling are two different problems, and a report can be 100% unsampled and still show an (other) row.
- – Query parameters, session IDs and product variants in the URL are the usual reason Page path cardinality explodes on eCommerce sites.
What is a high-cardinality dimension in GA4?
A high-cardinality dimension is one that collects a very large number of distinct values, such as Page path, Page title, transaction ID or an event-scoped custom dimension holding user input. Google treats a dimension as high cardinality when it exceeds roughly 500 unique values in a single day. Once the aggregate table hits its row limit, the extra values are grouped into (other).
How is the (other) row different from data sampling?
Sampling means GA4 estimated your results from a subset of events, and the data quality icon will tell you what percentage was used. The (other) row means all your events were counted, but the individual dimension values could not all be stored as separate rows in the table. In the exam scenario the report is 100% unsampled, which confirms the issue is row limits, not sampling.
Will switching to an Exploration remove the (other) row?
Usually yes for standard reporting periods, because Explorations query event-level data rather than the daily aggregate tables used by standard reports. You still have limits though, and very large date ranges or very wide breakdowns in an Exploration can trigger sampling or its own (other) row. For a truly complete list of page paths on a large site, the BigQuery export is the reliable option.
How do I reduce Page path cardinality on an eCommerce site?
Clean the URL before it reaches GA4. Use Admin, Data Streams, Configure tag settings to list unwanted query parameters for removal, or use a Modify event rule to rewrite page_location. Cutting out session IDs, tracking parameters and sort or filter strings can collapse thousands of near-duplicate paths into a handful of real ones.