> ## 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 Adform data source.

## Why can't I add more than 8 breakdowns or 10 metrics to one Adform data source?

Adform's Stats API enforces a hard cap of **8 breakdowns and 10 metrics** per report. Selecting more than that raises a `TOO_MANY_DIMENSIONS_OR_METRICS` error and the data source is not created. To report on a wider field set, create multiple Adform data sources, each staying within the limit, and combine them on the same dashboard. See the [Adform data reference](/data-sources/a-f/adform/data-reference) for the full metric and breakdown lists.

## Why is a breakdown or metric I expected missing from the picker?

Adform discovers its available fields dynamically from its metadata endpoints, and two compatibility rules can remove fields before selection:

* A subset of breakdowns and metrics is fully blocked because their compatibility with other fields cannot be reliably determined. Choosing a blocked breakdown surfaces a `BREAKDOWN_NOT_AVAILABLE` error, and choosing a blocked metric surfaces a `METRICS_NOT_AVAILABLE` error.
* Certain breakdown selections dynamically exclude incompatible metrics from the picker before the form is submitted, so which metrics appear can change depending on the breakdowns already chosen.

Because Adform itself determines which combinations are valid, building the same report directly in Adform first is a reliable way to confirm whether a breakdown and metric pairing is supported. The available field set is documented in the [Adform data reference](/data-sources/a-f/adform/data-reference).

## Why doesn't my dashboard date range change the data Adform returns?

Adform always operates over a fixed, rolling **397-day** window, and the report query is not driven by the dashboard date range. Each refresh re-fetches the full 397-day window, so adjusting the dashboard date range filters what is shown from data already held rather than requesting a different range from Adform. Data older than 397 days is not available from the API. See [Data history and retention](/data-sources/how-data-works/data-history-and-retention) and the [Adform data reference](/data-sources/a-f/adform/data-reference) for details on the window.

## Why is my Adform spend in a different currency than expected?

Spend and revenue are reported in the currency configured on the connected Adform account, not a currency selected in Adriel. When amounts look unexpected, the connected account's currency setting in Adform is the first thing to check. The currency behavior is noted in the [Adform data reference](/data-sources/a-f/adform/data-reference).

## Why did some of my Adform campaigns or creatives disappear from reports?

Once an element is deleted in Adform — a campaign, line item, or creative — it is no longer returned by the connector, so it stops appearing in reports and its historical rows are not retained. Elements that should remain reportable need to stay in place in Adform rather than being deleted.

## Why does a large Adform data source take a while to show data after connecting?

Adform generates reports asynchronously: the report job is submitted first, then the connector waits for Adform to finish building it. Very large requests — many breakdowns and metrics, or a full history — take longer to build, so data may not appear immediately after connecting or right after a refresh. It becomes available once the report finishes and is stored on the next sync. The refresh behavior is described in the [Adform data reference](/data-sources/a-f/adform/data-reference).

## Common issues

<AccordionGroup>
  <Accordion title="Why do cascade custom breakdowns on Adform return empty for several hours?">
    Adform data is fetched once per day, around 1 PM KST. Cascade auto-label custom breakdowns require the label to be synced to the database before the widget returns rows, and there's roughly a 7-hour gap between the Adform cache time and the label sync during which cascade breakdowns return empty.

    This is a known structural limitation. Workspaces that depend on Adform cascade breakdowns can be scheduled with an additional label sync closer to the Adform cache time — contact support to request it.
  </Accordion>
</AccordionGroup>

## Related

* [Adform data reference](/data-sources/a-f/adform/data-reference) — metrics, breakdowns, refresh strategy, and limits
* [How to connect Adform to Adriel](/data-sources/a-f/adform/how-to-connect) — connection steps for the data source
* [Data history and retention](/data-sources/how-data-works/data-history-and-retention) — how historical windows and caching work across data sources