Secondary dimensions in reports
Adding a secondary dimension cross-tabulates a report by a second attribute — channel by device, page by country. It is the fastest way to add context to a table, but it multiplies row cardinality, which can push rare combinations into an (other) row and increase the chance of thresholding.
What this means
A secondary dimension is an extra column added beside the primary dimension in a report table, creating a cross-tab. Where a primary dimension lists channels, adding device category as a secondary dimension splits each channel by device.
Cardinality and the (other) row
Cross-tabulating multiplies the number of distinct rows: ten channels by five devices is fifty combinations, and high-cardinality pairings can explode further. GA4 caps distinct rows and groups the overflow into an (other) row, so deep secondary breakdowns can hide detail. Small cells are also more likely to be thresholded. Use secondary dimensions for focused questions, and watch the (other) row before trusting a long-tail breakdown.
- Cross-tabs primary by a second dimension
- Combined cardinality can be very high
- Overflow rows collapse into (other)
How it appears in analytics and logs
A secondary dimension means each primary row is split by a second attribute. If totals seem to fragment or an (other) row grows, high combined cardinality is grouping rare pairs together.
Diagnostic use case
Add a second breakdown to a report — landing page by source, event by country — to see the interaction between two dimensions without leaving the table.
What WebmasterID can help detect
WebmasterID lets you cross-tabulate first-party dimensions without third-party cookies, keeping breakdowns on data you own.
Common mistakes
- Stacking high-cardinality dimensions and trusting the long tail.
- Reading the (other) row as a real combined value.
- Ignoring thresholding on small cross-tab cells.
Privacy and accuracy notes
Cross-tabulating two dimensions raises the odds that small cells are thresholded for privacy. Hidden cells are a safeguard, not lost data.
Related pages
- Comparisons in GA4 reports
Comparisons let you split a standard report into side-by-side subsets defined by dimension conditions — for example, mobile vs desktop. They are the standard-report counterpart to explorations' segments, but they are simpler, evaluated inline, and limited to dimensions available in that report.
- GA4 standard reports overview
Standard reports are GA4's fixed, pre-aggregated reports — grouped into collections like Life cycle and User — that load fast because they read from aggregate tables. Unlike explorations they are not generally sampled, but they apply (other) row grouping and can differ from exploration numbers, which query event-level data with their own scope.
- High cardinality and the (other) row
Every analytics tool has limits on how many distinct values a dimension can hold in a report. When a high-cardinality dimension — like full URLs or custom IDs — exceeds the limit, the overflow is bundled into an aggregate (other) row. Detail you expected vanishes into it, and totals look complete while breakdowns are not. This page explains the cause and the workarounds.
- Website observability
Cross-tabulate first-party dimensions.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.