Linking Maxio as a source
This source is currently in alpha. The interface and available tables may change.
The Maxio connector syncs your Maxio Advanced Billing (formerly Chargify) data into PostHog – customers, subscriptions, invoices, products, components, coupons, and billing events – so you can analyze revenue and billing activity alongside your product data.
Prerequisites
You need admin access to your Maxio Advanced Billing site to create an API key. API keys are site-scoped with full access. You also need to know which hosting region your site is on (US or EU).
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 Maxio, you'll need:
- Site subdomain – the subdomain of your Maxio site, e.g.
acmeforacme.chargify.com. You can find it in your site's URL. - API key – generate one in your Maxio dashboard under Config > Integrations > API keys.
- Hosting region – US (
chargify.com) or EU (ebilling.maxio.com), chosen when your account was provisioned.
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.
Subscriptions, invoices, customers, and events support incremental sync. All other tables use full refresh.
Incremental runs on subscriptions, invoices, and customers re-read a trailing day of updates to account for your site's timezone. Duplicate rows are merged away by primary key. Events use an integer cursor (since_id) which is exact and doesn't need a lookback window.
Configuration
| Option | Description |
|---|---|
Site subdomainType: text Required: True | The subdomain of your Maxio site, e.g. |
API keyType: password Required: True | |
Hosting regionType: select Required: True |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
customers | A person or organization that is billed for subscriptions on your Maxio site. | Incremental, Full refresh | created_at | — |
subscriptions | A single product subscription for a customer, including its state, product, pricing, and current billing period. | Incremental, Full refresh | updated_at | — |
invoices | An invoice issued to a customer, with totals, status, and optional line item, discount, tax, credit, payment, and refund breakdowns. | Incremental, Full refresh | updated_at | — |
products | A product that customers can subscribe to, defining recurring price and billing interval. | Full refresh | — | — |
product_families | A grouping of products, components, and coupons that belong to a single offering. | Full refresh | — | — |
coupons | A discount that can be applied to subscriptions, either a flat amount or a percentage. | Full refresh | — | — |
components | A metered, quantity-based, or on/off charge attached to a product family, billed alongside the base subscription. | Full refresh | — | — |
payment_profiles | A stored payment method (credit card, bank account, PayPal, or Apple Pay) belonging to a customer. | Full refresh | — | — |
events | Site activity events recording changes around the site, such as signups, renewals, payment successes and failures. | Incremental, Full refresh | id | — |
credit_notes | A credit issued to a customer that reduces the amount owed; the inverse of an invoice. | Full refresh | — | — |
Troubleshooting
- If validation fails with "Maxio site not found", double-check the subdomain (the label only, not the full URL) and that the hosting region matches where your site lives.
- If you see a 401 error, generate a new API key in your Maxio dashboard and reconnect.
- If you see a 403 error, the API key doesn't have access to the requested resource. Check key permissions in your Maxio site.
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.