Linking Appfigures 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 Appfigures connector syncs your app-store analytics – products, reviews, and sales and revenue reports – into PostHog, so you can analyze your mobile app performance alongside your product data.
Prerequisites
You need an Appfigures account with access to the developer portal so you can create an API client and Personal Access Token.
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.
When linking Appfigures, you'll need:
- Personal access token – create an API client and Personal Access Token at appfigures.com/developers/keys. When creating the client, grant the data sets you want to sync:
products:readfor products,public:readfor reviews, andprivate:readfor sales and revenue reports.
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.
Configuration
| Option | Description |
|---|---|
Personal access tokenType: password Required: True | |
ASO keyword countries (optional)Type: text Required: False | Country codes to pull tracked keyword positions for, comma-separated. Appfigures takes one country per request, so each code adds a request per app. Only the ASO keywords and ASO stats tables use it. They cover the United States when left blank. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
products | Apps, games, books, and other content in your Appfigures account, each with an Appfigures-assigned product id that is consistent across stores. | Full refresh | — | id |
reviews | App reviews across supported stores, filterable by product, country, stars, and creation date. | Incremental, Full refresh | date | id |
sales_report | Daily sales report aggregated across the account — downloads, updates, re-downloads, and related unit counts, one row per day. | Incremental, Full refresh | date | date |
revenue_report | Daily revenue report aggregated across the account, one row per day. | Incremental, Full refresh | date | date |
subscriptions_report | Daily subscription report aggregated across the account — active subscriptions, trials, activations, renewals, cancellations, churn, and MRR, one row per day. | Incremental, Full refresh | date | date |
ratings_report | Daily ratings report aggregated across the account — rating counts, averages, and star distribution, one row per day. Replaces the deprecated /ratings resource. | Incremental, Full refresh | date | date |
ads_report | Daily ad publishing report aggregated across the account — how many ad requests each network filled and what those ads earned, one row per day. | Incremental, Full refresh | date | date |
adspend_report | Daily ad spend report aggregated across the account — what user-acquisition campaigns cost and what they delivered, one row per day. | Incremental, Full refresh | date | date |
payments_report | Daily payments report aggregated across the account — the payouts to expect from app sales, in-app purchases, and ad revenue, one row per day. | Incremental, Full refresh | date | date |
ranks | Store category rank history, one row per product, country, category chart, and day. Rows are only written for days the product actually held a rank, and cover the country Appfigures returns by default (the United States). | Incremental, Full refresh | date | date, product_id, country, category_id, category_subtype |
aso_keywords | Daily snapshot of where each product ranks in store search for every keyword tracked in Appfigures. Appfigures returns the latest position rather than a dated series, so a row records what the sync saw that day, for the countries set on the source. | Full refresh | — | date, product_id, country, keyword_id |
aso_stats | Daily snapshot summarizing the tracked keyword set for one product in one country — average position, how many keywords sit near the top of search, and how many moved. | Full refresh | — | date, product_id, country |
stores | Reference table of the stores Appfigures supports, with the features and storefronts each one offers. Resolves the store codes on products and ranks. | Full refresh | — | id |
categories | Reference table of store category charts. Resolves the category ids on rank rows. | Full refresh | — | id |
countries | Reference table of countries Appfigures reports on. Resolves the ISO codes on reviews, reports, and rank rows. | Full refresh | — | iso |
Troubleshooting
- If you see an invalid or expired token error, create a new Personal Access Token in your Appfigures developer settings, then reconnect.
- If a table fails with a missing scope error, grant the required data sets to your API client, then reconnect.
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.