> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/marketing/appfigures/faq.md).

# FAQ

<details>

<summary>Where do I find my Appfigures API key?</summary>

Log in to Appfigures, go to **Account Settings**, and select the **API** tab. Your personal API key is listed there. If you don't see an API tab, your account may not have developer access enabled — contact Appfigures support to request it.

</details>

<details>

<summary>Can I pull data from multiple app stores in one data flow?</summary>

Each data flow instance is tied to one `search_store` value (e.g., `apple` or `google`). To combine data from multiple stores, create a separate data flow for each store and use Coupler.io's **Append** transformation to merge them into a single destination.

</details>

<details>

<summary>Can I track multiple apps at once?</summary>

Yes — Appfigures aggregates data across all apps in your account by default. Use the `group_by: product` setting (the default) to see data broken down by individual app. If you want a single total across all apps, switch to grouping by `date` or `country`.

</details>

<details>

<summary>Why does my revenue data look different from App Store Connect?</summary>

There are two common reasons: (1) Appfigures separates **proceeds** (after store fees) from **gross revenue** — make sure you're using the right metric. (2) Apple finalizes reporting data with a 24–72 hour delay, so very recent figures may not match yet. See the Data Overview article for a breakdown of revenue metrics.

</details>

<details>

<summary>Can I use Appfigures data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including **ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw**. You can send your Appfigures reports directly to these tools to get AI-generated insights, trend summaries, or recommendations based on your app performance data.

</details>

<details>

<summary>What's the difference between Reports ads and Reports adspends?</summary>

**Reports ads** contains performance metrics — impressions, clicks, and engagement. **Reports adspends** contains cost data — how much you spent on each campaign. To calculate metrics like CPC or ROAS, you'll want to join both entities using Coupler.io's Join transformation.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

The date range depends on your Appfigures plan and the data available from each store. Use the date picker to set a start date as far back as you need — but note that very large date ranges combined with daily grouping can slow down the data flow or trigger rate limits. Start with a 90-day window and expand from there.

</details>

<details>

<summary>Can I schedule automatic data refreshes?</summary>

Yes, once your data flow completes a successful manual run, you can set up a schedule to refresh data automatically. For more on timing and frequency, see the Best Practices article.

</details>

{% hint style="info" %}
For a full breakdown of available metrics and dimensions, see the [Data Overview](/sources/category/marketing/appfigures/data-overview.md) article. For help with errors or missing data, check [Common Issues](/sources/category/marketing/appfigures/common-issues.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/marketing/appfigures/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.