> 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

Connect Appfollow to Coupler.io to sync app reviews, ratings, and user feedback from App Store and Google Play into spreadsheets or dashboards.

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        |

## Appfollow data overview

Appfollow exposes data across five entities, covering app organization, review statistics, and rating performance. Here's what you can access through Coupler.io.

## Entities overview

| Entity          | What it contains                                                |
| --------------- | --------------------------------------------------------------- |
| Users           | Account-level user profiles in your Appfollow workspace         |
| App collections | Grouped sets of apps organized by custom or preset criteria     |
| App lists       | Individual lists of apps you're tracking in Appfollow           |
| Stat reviews    | Aggregated review counts, sentiment stats, and feedback metrics |
| Ratings         | Rating scores, historical trends, and distribution breakdowns   |

## Stat reviews

#### Review metrics

| Field                | Description                                   |
| -------------------- | --------------------------------------------- |
| Total reviews        | Total number of reviews collected for the app |
| Positive reviews     | Count of reviews with positive sentiment      |
| Negative reviews     | Count of reviews with negative sentiment      |
| Neutral reviews      | Count of reviews with neutral sentiment       |
| Average rating       | Mean rating derived from the review set       |
| Review response rate | Share of reviews that received a reply        |

#### Review dimensions

| Field    | Description                      |
| -------- | -------------------------------- |
| App ID   | Unique identifier for the app    |
| App name | Name of the tracked application  |
| Store    | App Store or Google Play         |
| Country  | Country or region of the reviews |
| Date     | Date of the review data snapshot |

## Ratings

#### Rating metrics

| Field          | Description                      |
| -------------- | -------------------------------- |
| Current rating | Latest overall rating score      |
| Rating count   | Total number of ratings received |
| 1-star count   | Number of 1-star ratings         |
| 2-star count   | Number of 2-star ratings         |
| 3-star count   | Number of 3-star ratings         |
| 4-star count   | Number of 4-star ratings         |
| 5-star count   | Number of 5-star ratings         |
| Rating delta   | Change in rating over a period   |

#### Rating dimensions

| Field    | Description                          |
| -------- | ------------------------------------ |
| App ID   | Unique identifier for the app        |
| App name | Name of the application              |
| Store    | App Store or Google Play             |
| Country  | Country or region of the rating data |
| Date     | Date of the rating snapshot          |

## App collections and app lists

#### Fields

| Field              | Description                      |
| ------------------ | -------------------------------- |
| Collection/List ID | Unique identifier                |
| Name               | Name of the collection or list   |
| App count          | Number of apps included          |
| Created at         | Timestamp of when it was created |
| Updated at         | Timestamp of the last update     |

## Common metric combinations

* **Ratings + Stat reviews** — Join on App ID to see how rating scores correlate with review volume and sentiment for each app.
* **App lists + Ratings** — Append ratings data across multiple app lists to compare performance by category or market.
* **Stat reviews over time** — Track review sentiment trends by pulling Stat reviews on a recurring schedule and appending historical snapshots.

## Use cases by role

{% tabs %}
{% tab title="Product & App teams" %}

* Monitor rating trends after each app release to catch regressions early
* Track review sentiment week-over-week to identify recurring user complaints
* Compare App Store vs. Google Play ratings side by side using the Store dimension
  {% endtab %}

{% tab title="Marketers" %}

* Pull app ratings into a Looker Studio dashboard to report on brand perception
* Use Stat reviews data to measure how campaigns affect user sentiment
* Send review summaries to ChatGPT or Claude for automated weekly reports
  {% endtab %}

{% tab title="Customer support" %}

* Track review response rate from Stat reviews to monitor team performance
* Identify spikes in negative reviews and correlate with support ticket volume
* Export review stats to Google Sheets for daily team standups
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Stat reviews and Ratings data are store-specific — App Store and Google Play figures are reported separately
* Historical rating data availability depends on your Appfollow plan tier
* App collections and App lists are organizational entities — they don't contain review or rating metrics directly, but you can use their IDs to join with Ratings or Stat reviews
* User data reflects workspace members in Appfollow, not end users of your apps

## Appfollow common issues

### Connection issues

<details>

<summary>My API key is not being accepted</summary>

Double-check that you're copying the full API key from **Appfollow Settings → API** with no leading or trailing spaces. If the key still fails, regenerate it in Appfollow and use the new one. Make sure your Appfollow account is active and not suspended.

</details>

<details>

<summary>The data flow fails immediately after authentication</summary>

This usually means the selected entity isn't accessible with your API key's permission level. Check that your Appfollow plan includes API access and that the entity you selected (e.g., Stat reviews or Ratings) is available on your subscription tier.

</details>

### Missing data

<details>

<summary>No data appears for Stat reviews or Ratings</summary>

Appfollow only returns data for apps that are actively tracked in your account. If you haven't added any apps to a list or collection in Appfollow, these entities will return empty. Log in to Appfollow and confirm at least one app is being monitored.

</details>

<details>

<summary>App collections or App lists return empty results</summary>

This happens when no collections or lists have been created in your Appfollow workspace. Create at least one list or collection in Appfollow, then re-run the data flow.

</details>

<details>

<summary>Rating data is missing for certain countries</summary>

Country-level rating breakdowns depend on your Appfollow subscription. Some plans only include global or top-market data. Check your plan's country coverage in Appfollow's documentation or contact Appfollow support to confirm what regions are included.

</details>

### Permission errors

<details>

<summary>I get a "403 Forbidden" or "Unauthorized" error</summary>

This indicates the API key doesn't have the right permissions for the entity you're trying to access. Some Appfollow features are restricted by role or plan. Verify that your user role in Appfollow has API access enabled, and that your plan supports the entity you're querying.

</details>

### Data discrepancies

<details>

<summary>Rating counts in Coupler.io don't match what I see in the Appfollow dashboard</summary>

Appfollow's dashboard may display real-time or cached figures, while the API returns data at a specific snapshot time. If you're comparing numbers, make sure you're looking at the same date range and store (App Store vs. Google Play) in both places. Rating deltas can also differ if the dashboard uses a rolling window.

</details>

<details>

<summary>Review sentiment percentages look different between exports</summary>

Sentiment classification in Appfollow can be recalculated retroactively when their models are updated. If you notice historical figures changing, this is expected behavior from Appfollow's side — it's not a Coupler.io sync issue.

</details>

### Rate limits

<details>

<summary>The data flow fails with a rate limit error</summary>

Appfollow enforces API rate limits based on your plan. If you're running multiple data flows simultaneously or refreshing very frequently, you may hit these limits. Stagger your data flow schedules and avoid running more than one Appfollow data flow at the same time to stay within limits.

</details>

## Appfollow 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](#appfollow-data-overview) article. If you're running into connection or sync errors, check the [Common Issues](#appfollow-common-issues) 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
