Dodo Payments
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.
Connect Dodo Payments to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Sync payments, subscriptions, customers, refunds, disputes, payouts and your product catalog from Dodo Payments into PostHog. Create an API key in your Dodo Payments dashboard under Developer > API keys. Read access is enough.
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. |
Linking Dodo Payments to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Dodo Payments
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
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 |