> 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.md).

# Appfollow

Appfollow is a mobile app intelligence platform that helps you track app reviews, ratings, and user feedback across the App Store and Google Play. It centralizes review management, sentiment analysis, and app performance data in one place.

Connecting Appfollow to Coupler.io lets you pull your app reputation data into any destination — from spreadsheets and dashboards to AI tools — without manual exports or custom scripts.

**Why connect Appfollow to Coupler.io?**

* Sync app ratings and review stats automatically to Google Sheets, Excel, BigQuery, or Looker Studio
* Send review and rating data to AI destinations like ChatGPT, Claude, or Gemini for automated sentiment summaries
* Combine data from multiple app lists or collections using Append or Join transformations
* Keep stakeholders updated with fresh data on a schedule, without touching a CSV

## Prerequisites

Before connecting, make sure you have:

* An active Appfollow account with at least one app being tracked
* Your Appfollow API key (available in your account settings)
* Access to the entities you want to export (app lists, collections, ratings, or reviews)

## Quick start

{% hint style="success" %}
If you want review stats and ratings in one place, add both **Stat reviews** and **Ratings** as sources in a single data flow and use the Join transformation to combine them by app ID.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to the Data flows section, and click **Add data flow**. Search for Appfollow and select it as your source.
{% endstep %}

{% step %}
**Enter your Appfollow API key.** In your Appfollow account, navigate to **Settings → API** and copy your API key. Paste it into the API key field in Coupler.io. Click **Proceed** to authenticate.
{% endstep %}

{% step %}
**Select an entity.** Choose which data you want to import — Users, App collections, App lists, Stat reviews, or Ratings. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land. Options include Google Sheets, Excel, BigQuery, Looker Studio, or AI destinations like ChatGPT, Claude, Gemini, Perplexity, Cursor, or OpenClaw.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your Appfollow data will appear in your chosen destination.
{% endstep %}
{% endstepper %}

## Available entities

| Entity          | Description                                         |
| --------------- | --------------------------------------------------- |
| Users           | User accounts and profiles within Appfollow         |
| App collections | Curated groups of apps organized by criteria        |
| App lists       | Lists of apps you're actively tracking              |
| Stat reviews    | Statistical metrics around app reviews and feedback |
| Ratings         | App rating scores, trends, and distributions        |


---

# 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.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.