Linking Kajabi as a source
This source is currently in alpha. The interface and available tables may change.
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.
Alpha: This source is in alpha. If you run into issues, please let us know.
The Kajabi connector syncs your contacts, customers, purchases, offers, products, courses, orders, transactions, and tags into the PostHog data warehouse so you can analyze them alongside your product data.
Prerequisites
You need a Kajabi account with access to the Public API settings. Create a User API Key and give it read access to the tables you want to sync.
You also need your Site ID. Each Kajabi import is scoped to a single site.
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 Kajabi, you'll need:
- Client ID – from your Kajabi User API Key.
- Client secret – from your Kajabi User API Key.
- Site ID – the ID of the Kajabi site you want to import data from.
PostHog authenticates with Kajabi using OAuth2 client credentials. No manual token management is needed after the initial setup.
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 Kajabi tables use full refresh sync. Each sync replaces the contents of the table so that updates and deletions to existing records are captured.
Configuration
| Option | Type | Required |
|---|---|---|
Client ID | text | Yes |
Client secret | password | Yes |
Site ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
contacts | Contacts and their profile, subscription status, and custom fields. | Full refresh | — | — |
customers | Customer profiles, activity, and total revenue. | Full refresh | — | — |
purchases | Offer purchases with payment amounts, attribution, and access status. | Full refresh | — | — |
offers | Offers with prices, payment types, and checkout URLs. | Full refresh | — | — |
products | Products that can be granted to contacts, excluding archived products. | Full refresh | — | — |
courses | Course titles, descriptions, and thumbnails. | Full refresh | — | — |
orders | Orders with totals, discounts, taxes, and fulfillment status. | Full refresh | — | — |
order_items | Order items with quantities, prices, discounts, and taxes. | Full refresh | — | — |
transactions | Payment transactions with amounts, currencies, and payment states. | Full refresh | — | — |
contact_tags | Tags available for contacts on the selected site. | Full refresh | — | — |
contact_offers | Offers granted to each contact on the selected site. | Full refresh | — | — |
contact_taggings | Tags assigned to each contact on the selected site. | Full refresh | — | — |
Troubleshooting
- If the connection fails with a credentials error, your client ID or client secret is wrong. Create a new User API Key in Kajabi's Public API settings, then reconnect the source.
- If a table fails with a permission error, your API key doesn't have read access to that table. Update its permissions in Kajabi, then reconnect the source.
- If the connection fails with an HTTP error referencing your site ID, double-check the site ID and try again.
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.