Linking Zuora as a source
This source is currently in alpha. The interface and available tables may change.
The Zuora connector syncs your subscription billing data into PostHog, so you can analyze billing activity alongside your product data.
Prerequisites
You need a Zuora tenant and an OAuth client with permission for the objects you want to sync. The OAuth client inherits the permissions of the user it's created under.
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 Zuora, you'll need:
- Environment – choose the environment that matches your tenant (US Production, US API Sandbox, US Cloud Production, US Cloud Sandbox, EU Production, EU Sandbox, or Central Sandbox). Credentials only work against their own environment.
- Client ID – the OAuth client ID. A Zuora admin can create an OAuth client under Settings → Administration → Manage Users.
- Client secret – the OAuth client secret shown when the client is created.
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 | Type | Required |
|---|---|---|
Environment | select | Yes |
Client ID | text | Yes |
Client secret | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
accounts | A customer account holding billing, payment, and contact information. | Incremental, Full refresh | updatedDate | — |
subscriptions | A customer's agreement to be billed for products over a period of time. | Incremental, Full refresh | updatedDate | — |
invoices | A bill issued to a customer account for amounts owed. | Incremental, Full refresh | updatedDate | — |
payments | A payment applied against one or more invoices on a customer account. | Incremental, Full refresh | updatedDate | — |
credit_memos | A document crediting a customer account, reducing the amount they owe. | Incremental, Full refresh | updatedDate | — |
refunds | A return of funds to a customer against a payment or credit memo. | Incremental, Full refresh | updatedDate | — |
products | A product in the Zuora product catalog that can be sold to customers. | Incremental, Full refresh | updatedDate | — |
orders | An order capturing one or more subscription changes for a customer account. | Incremental, Full refresh | updatedDate | — |
Troubleshooting
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.