> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQs

> Common questions, expected behaviors, and troubleshooting for the Amplitude data source.

## Why do newly tracked events take a few minutes to appear in the field picker?

The list of available metrics is built from the Amplitude project's event catalog, and that catalog is cached for about five minutes. When a new event is defined in Amplitude, it becomes queryable in Adriel once the cached list next refreshes, so a short delay before it shows up in the field picker is expected.

The two fixed user metrics, **New users** and **Active users**, are always available and do not depend on the event catalog. For the full set of generated metrics, see the [Amplitude data reference](/data-sources/a-f/amplitude/data-reference).

## Why does a funnel metric reject weekly or monthly date breakdowns?

Funnel metrics — the transition, transition time, and frequency metrics generated per event — support only a daily date breakdown. Selecting a weekly or monthly date breakdown on a funnel widget returns an `INVALID_BREAKDOWN_FOR_CHART` error, because Amplitude's funnel data cannot be aggregated at the week or month level.

To see funnel results over a longer span, keep the date breakdown at the daily level and widen the date range, or remove the date breakdown to get a single aggregate value for the period. Event segmentation metrics (such as event totals and event uniques) do accept daily, weekly, and monthly date breakdowns if a coarser granularity is needed.

## Why are my new-user or active-user counts blank when I break them down by country?

**New users** and **Active users** return values for a date breakdown or for the ungrouped total, but not when grouped by a non-date breakdown such as country or platform. In that case the widget shows the breakdown labels (each country, for example) with empty user counts rather than numbers.

To keep the counts populated, report **New users** and **Active users** without a non-date breakdown, or split them only by date. To segment engagement by country, use the per-event metrics instead — **Event uniques** for an event accepts breakdowns like country and platform.

## How many breakdowns can a single widget use?

The breakdown cap depends on the metric's query mode. A date breakdown does not count toward these limits.

| Metric type                                              | Maximum non-date breakdowns |
| -------------------------------------------------------- | --------------------------- |
| Event segmentation (event totals, event uniques)         | 2                           |
| Funnel metrics (transitions, transition time, frequency) | 1                           |
| User metrics (New users, Active users)                   | 1                           |

Exceeding the limit for a metric returns a `TOO_MANY_BREAKDOWNS` error. When mixing metric types in one widget, the strictest applicable limit governs. The available breakdowns are listed in the [Amplitude data reference](/data-sources/a-f/amplitude/data-reference).

## Why is part of a breakdown missing rows or marked incomplete?

When a breakdown produces a very large number of rows, Amplitude prunes the result. Adriel surfaces a `TOO_MUCH_DATA_REQUESTED_INCOMPLETE` warning and shows the partial data with an explicit caveat, so a high-cardinality breakdown can return fewer rows than expected. Narrowing the date range or choosing a lower-cardinality breakdown usually returns a complete result.

There is no city breakdown for this reason: grouping by city produces enough rows that Amplitude truncates the response, so it is intentionally not offered. Country and region are available as lower-cardinality geographic alternatives.

## How do I report revenue from Amplitude?

The Amplitude connector does not expose a dedicated revenue or currency metric. Revenue is reported through the standard event metrics applied to a revenue-tagged event — for example, **Event totals** or **Event uniques** for a `purchase` event. These values are counts of the event, so they reflect how often the revenue event fired rather than a monetary total. For monetary reporting alongside ad-platform spend, pair these event metrics with a custom metric on the dashboard.

## Related

<CardGroup cols={2}>
  <Card title="Amplitude data reference" href="/data-sources/a-f/amplitude/data-reference">
    Metrics, breakdowns, date-range limits, and query modes for the Amplitude data source.
  </Card>

  <Card title="How to connect Amplitude" href="/data-sources/a-f/amplitude/how-to-connect">
    Connect an Amplitude project with its API Key and Secret Key.
  </Card>

  <Card title="Google Analytics 4 data reference" href="/data-sources/g-n/google-analytics-4/data-reference">
    The web and app analytics counterpart connector.
  </Card>

  <Card title="Piano Analytics data reference" href="/data-sources/o-z/piano-analytics/data-reference">
    The alternative product and audience analytics connector.
  </Card>
</CardGroup>
