Linking Memberful 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.
Contents
The Memberful connector syncs your membership data into the PostHog data warehouse, so you can analyze your members, subscriptions, and orders alongside your product data.
Prerequisites
You need a Memberful account with permission to create a custom application and API key. A read-only key is sufficient.
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 Memberful, you'll need:
Account subdomain – the part before
.memberful.comin your Memberful dashboard URL. For example, if your dashboard is atacme.memberful.com, enteracme. You can also paste the full URL and PostHog will extract the subdomain.API key – go to Settings → Custom applications in your Memberful dashboard, add a custom application with API key access, then copy its API key.
Sync methods
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.
Only the activities table supports incremental syncing, using createdAt as the replication key. All other tables (members, subscriptions, orders, coupons, plans, and downloads) sync via full table refresh.
The orders table is full refresh only because refunds and status changes do not update an order's createdAt timestamp. An incremental sync would miss those updates.
Configuration
| Option | Type | Required |
|---|---|---|
Account subdomain | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
members | A person with a Memberful account, with or without an active subscription. | Full refresh | — | — |
subscriptions | A member's subscription to a plan price. Group subscriptions can cover additional members. | Full refresh | — | — |
orders | A purchase of a plan price or a download, including renewals, upgrades and manual charges. | Full refresh | — | — |
activities | An event in the account's activity feed, such as a new order, a renewal or a cancellation. | Incremental, Full refresh | createdAt | — |
coupons | A discount code that members can apply at checkout. | Full refresh | — | — |
plans | A price that members can subscribe at. The API calls a dashboard price a plan, and a dashboard plan a pass. Each price belongs to one pass. | Full refresh | — | — |
downloads | A digital file that members can buy on its own or get with a plan. | Full refresh | — | — |
Troubleshooting
If you see an authentication error, your API key is invalid or has been deleted. Create a new API key under Settings → Custom applications in Memberful, then reconnect.
If you see an account not found error, check that your subdomain is correct. Use the part before
.memberful.com, not the full URL.
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.