> 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/appfollow/faq.md).

# FAQ

<details>

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

Log in to your Appfollow account and go to **Settings → API**. Your API key will be listed there. Copy it and paste it into Coupler.io when prompted during the connection step. If you don't see an API section, your Appfollow plan may not include API access — check with Appfollow support.

</details>

<details>

<summary>Can I pull data for multiple apps in one data flow?</summary>

Yes. If your apps are organized into App lists or collections in Appfollow, you can add multiple sources to a single data flow and use the **Append** transformation to combine them. This gives you a unified dataset across all your tracked apps without running separate data flows.

</details>

<details>

<summary>What's the difference between Stat reviews and Ratings?</summary>

Stat reviews contains statistical and sentiment-based metrics around user reviews — counts, sentiment breakdowns, and response rates. Ratings focuses on the numeric score data — current ratings, star distributions, and rating trends over time. For a complete picture of app reputation, use both and join them on App ID.

</details>

<details>

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

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can send Stat reviews or Ratings data directly to these tools for automated analysis, sentiment summaries, or report generation.

</details>

<details>

<summary>Does Coupler.io support both App Store and Google Play data from Appfollow?</summary>

Yes, as long as Appfollow is tracking apps from both stores in your account. The data includes a Store field so you can filter or segment by platform in your destination.

</details>

<details>

<summary>Why does the Users entity only show a few records?</summary>

The Users entity in Appfollow represents the team members (workspace users) in your Appfollow account — not the end users of your mobile apps. If you're expecting consumer-level user data, that's not what this entity provides.

</details>

<details>

<summary>How far back does historical ratings data go?</summary>

The historical depth of ratings data depends on your Appfollow subscription plan. Higher-tier plans typically provide longer history. Check your plan details in Appfollow or contact their support to confirm what range is available via the API.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see the [Data Overview](/sources/category/marketing/appfollow/data-overview.md) article. If you're running into connection or sync errors, check the [Common Issues](/sources/category/marketing/appfollow/common-issues.md) guide.
{% 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/appfollow/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.