Linking AppFollow as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The AppFollow connector syncs app collections, app lists, users, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your AppFollow API token to pull your app reviews and ratings.
An Account Owner or Admin can generate an API token on the API management page in your AppFollow account. The token authenticates every request via the X-AppFollow-API-Token header.
Note that AppFollow bills API usage against a credit balance (reviews and ratings cost more per request) and rate-limits to 1000 requests/hour per token.
You'll be asked for:
- API token: for example
Your AppFollow API token.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All AppFollow tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
app_collections | Workspaces (collections) on your AppFollow account, each grouping a set of tracked apps. | Full refresh | — | id |
app_lists | The apps tracked across every collection, including each app's store | Full refresh | — | app_collection_id, app_id |
users | Users on your AppFollow account. | Full refresh | — | id |
reviews | App Store and Google Play reviews for your tracked apps, incrementally synced on the review's last-modified timestamp. | Incremental, Full refresh | updated | ext_id, review_id |
ratings_history | Daily star-rating history per app and store, incrementally synced by date. | Incremental, Full refresh | date | ext_id, store, date |
rankings | A daily snapshot of each tracked app's category rank positions in the store charts. | Full refresh | — | ext_id, country, device, genre_id, date |
keywords | A daily snapshot of the search position your tracked apps hold for each keyword you track in AppFollow. | Full refresh | — | ext_id, country, device, date, keyword |
app_versions | Store release history for your tracked apps, including metadata changes. Resolves the app version recorded on each review. | Full refresh | — | ext_id, country, version |
reviews_stats | Aggregate review and reply counts per app and day, so review volume can be charted without syncing every raw review. | Incremental, Full refresh | date | ext_id, date |
Troubleshooting
- If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.