Linking Dodo Payments 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 Dodo Payments connector syncs payments, subscriptions, customers, 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.
Sync payments, subscriptions, customers, refunds, disputes, payouts and your product catalog from Dodo Payments. Create an API key in your Dodo Payments dashboard under Developer > API keys. Read access is enough.
You'll be asked for:
- API key: create a key under Developer > API keys. A read-only key is enough to sync.
- Mode: dodo Payments keeps test and live data on separate hosts with separate keys. Pick the mode your key was issued for.
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 Dodo Payments tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
API keyType: password Required: True | Create a key under Developer > API keys. A read-only key is enough to sync. |
ModeType: select Required: True | Dodo Payments keeps test and live data on separate hosts with separate keys. Pick the mode your key was issued for. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
payments | One-off and subscription payments collected by Dodo Payments as merchant of record. | Incremental, Full refresh | created_at | payment_id |
subscriptions | Recurring subscriptions, their billing schedule and current lifecycle status. | Incremental, Full refresh | created_at | subscription_id |
customers | Customers who have paid through Dodo Payments. | Incremental, Full refresh | created_at | customer_id |
refunds | Refunds issued against payments. | Incremental, Full refresh | created_at | refund_id |
disputes | Chargebacks and disputes raised against payments, with their current stage and status. | Incremental, Full refresh | created_at | dispute_id |
payouts | Settlements paid out to the merchant, with the fees, tax, refunds and chargebacks netted off. | Incremental, Full refresh | created_at | payout_id |
license_keys | License keys issued to customers by payment and subscription flows, or imported by the merchant. | Incremental, Full refresh | created_at | id |
balance_ledger_entries | Merchant balance ledger: every credit and debit against the account balance, including payments, refunds, disputes, fees and payouts. | Incremental, Full refresh | created_at | id |
events | Usage events ingested for metered billing. | Incremental, Full refresh | timestamp | event_id |
products | Products available for purchase, one-off and recurring. | Full refresh | — | product_id |
product_collections | Groupings of products presented together in checkout. | Full refresh | — | id |
discounts | Discount codes, their redemption limits and how often they have been used. | Full refresh | — | discount_id |
addons | Add-ons that can be attached to a subscription. | Full refresh | — | id |
brands | Brands configured on the account, each with its own checkout branding and verification state. | Full refresh | — | brand_id |
meters | Meters that aggregate usage events into billable quantities. | Full refresh | — | id |
license_key_instances | Individual activations of a license key, one row per activated instance. | Full refresh | — | id |
entitlements | Entitlements that grant customers access to something on purchase, such as digital files. | Full refresh | — | id |
credit_entitlements | Credit entitlements: prepaid credit balances customers draw down, with rollover and overage rules. | Full refresh | — | id |
Troubleshooting
- If the connection fails with an authorization error, the API key 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.