On this page

Data Tables FAQ

This page answers common questions about Data Tables charts.

Why is the sum of the rows in my Data Table greater than the overall value?

After you apply a group-by clause to a uniques metric in a Data Table, a single user may appear in more than one group if they triggered that event multiple times with different values for the property specified in the group-by. The sum of uniques after a group-by can be greater than the overall value.

The overall value in my Data Table doesn't equal the sum of the rows below it when it should. Why?

This is due to caching. The overall result and the group-by results come from different queries, so they're cached differently. To get consistent results, update the end day to yesterday in the date picker.

When I apply an attribution model in my Data Table, why doesn't the overall value equal the sum of the values in the rows below it?

When a metric with attribution is applied in a Data Table and there are more than ten possible values for the group-by clause, only ten values appear. When this happens, a pruning message at the top of the screen appears. Other users contribute to the total, but their values aren't included in the ten values shown (they're pruned from view), so the sum of the ten rows doesn't equal the overall value at the top.

Why do some of my values disappear in my Data Table when I sort from high to low?

Why does my Data Table show only 100 rows when I've applied a group-by clause?

When you apply a group-by to your Data Table, Amplitude displays the top 100 results by default. This is a display limit, not a data processing limit. Amplitude still processes all your data, but only shows the top 100 groups ranked by the sorted metric.

The display limits vary based on your configuration:

  • Single top-level group-by: 100 rows
  • Multiple top-level group-bys: 500 rows
  • Metrics with attribution: 20 rows
  • Multiple metric types: Smallest limit applies

When you export to CSV, different limits apply based on metric type. For complete details about display limits, export limits, and sorting logic, review Results limits and sorting logic in Data Tables.

Why do some formula metric column cells populate in my Data Table while others appear as null ("-")?

The formula metric in a Data Table works only for groups that have a value for all terms in the formula. If one cell that makes up the formula isn't available, the formula populates as a dash.

Why doesn't my exported CSV include all the rows displayed in the Data Table?

Why does my exported CSV show more values than what appears in the Data Table?

Why does my exported CSV contain more than 10,000 rows if 10,000 rows is the limit?

The limit is 10,000 groups per metric per group-by clause. If you have multiple metrics in your data table, and the groups of the first column differ from those of the second column, the results may display as a union of available properties across the board, which can exceed 10,000 rows overall.

When I export my Data Table as a PDF or PNG, why is the image cut off?

This is due to a bounded box of the Data Table, set intentionally for technical reasons. To request a change, submit feedback through the Amplitude widget at the bottom right corner of the UI.

Why can't I scroll horizontally in a Data Table?

When you have many group-by filters, the property values can take up the entire width of a laptop screen. This pushes the metric columns off the page, making them unreachable. Open the Data Table on a larger monitor, or reduce the number of group-bys applied.

To request a change, submit feedback through the Amplitude widget at the bottom right corner of the UI.

Can I show all the filters applied to the Data Table without hovering over the filter icon?

No. The filter is only visible on hover.

To request a change, submit feedback through the Amplitude widget at the bottom right corner of the UI.

Is there a way to perform simple calculations using the columns of Data Tables? For example, I have two columns, A and B. How do I calculate row-wise and display the result in a third column?

Was this helpful?