This article is about Google Analytics 4 properties. Refer to the Universal Analytics section if you're still using a Universal Analytics property, which will stop processing data on July 1, 2023 (July 1, 2024 for Analytics 360 properties).

[GA4] (other) entries in reports

Learn about when the "(other)" row appears

An "(other)" row appears in a report when the underlying database table from which the report is built reaches its row limit.

This article provides more information about what causes an "(other)" row to appear and best practices to consider when the row appears.

In this article:

What causes the (other) row

Each report in Analytics has an underlying database table that Analytics uses to populate the report with data. The total number of rows in the underlying database table is equal to the result of multiplying together the cardinality of all dimensions in the table.

For example, if you had two dimensions in a table — the Device dimension with 3 unique values (i.e., desktop, tablet, mobile) and the Age dimension with 6 unique values (i.e., 18-24, 25-34, 35-44, 45-54, 55-64, 65+) — then the cardinality (or the total number of rows) can be up to 18 rows.

When the result of multiplying the cardinality of each dimension in a report exceeds the row limit, Analytics displays an "(other)" row. The applicable underlying table and its row limit varies depending on the report type (standard or custom), implementation details, and property type (standard or 360). Learn more about row limits

Note: A dimension is considered high-cardinality when it has more than 500 unique values in one day. High-cardinality dimensions make it more likely that a report hits its row limit, resulting in the "(other)" row. You should use high-cardinality dimensions only for information that's important and necessary to meet your business goals.

Reports and the Data API

The data in standard and custom reports and the Google Analytics Data API are subject to row limits, resulting in data being grouped under an "(other)" row.


Explorations have different limits, which results in differences in metrics when limits are reached. Unlike reports and the Data API, explorations never show an "(other)" row. Learn more

Best practices

Use standard reports and explorations

  • Use standard reports whenever possible because standard reports have special tables that decrease the likelihood of data being grouped under an "(other)" row.
  • If you see an "(other)" row in a report, consider looking at the same data in Explorations. If you use Analytics 360, and an exploration begins to sample data, you can request unsampled exploration results.

Use predefined dimensions

  • Use predefined dimensions before you create custom dimensions. For example, use the predefined gaming dimensions (e.g., Character, Virtual Currency Type) instead of setting up custom dimensions for the same data.
  • Only use high-cardinality dimensions when necessary. The row limit can apply to all the data in the property for the specified date range when you apply a secondary dimension or comparison to a standard report or when you use a custom report. Sometimes, data that isn't shown in the report contributes to the row limit.
  • Avoid using a custom dimension to create a distinct identifier for each user. Instead, use the User-ID feature.

Consider advanced features

  • If an "(other)" row appears in a standard property, consider upgrading to Analytics 360 to take advantage of automatic expanded datasets. If you use Analytics 360, Analytics automatically enables automatic expanded datasets when you consistently see the "(other)" row so that data aggregates under the "(other)" row far less frequently.
  • Export your data to BigQuery, which is available to both standard and 360 properties.
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue

Clear search
Close search
Google apps
Main menu
Search Help Center