Linking BigCommerce 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 BigCommerce connector syncs products, categories, brands, 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.
Enter your BigCommerce store hash and API access token to pull your store data. Create an API account under Settings → API → Store-level API accounts with read-only scope for Products, Orders and Customers.
You'll be asked for:
- Store hash: found in your store's control panel URL:
https://store-{store_hash}.mybigcommerce.com. - Access token
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 BigCommerce tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
Store hashType: text Required: True | Found in your store's control panel URL: |
Access tokenType: password Required: True |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
products | A product listed for sale in the BigCommerce catalog. | Incremental, Full refresh | date_modified | — |
categories | A category used to organize products in the storefront navigation. | Full refresh | — | — |
brands | A brand that products in the catalog can be assigned to. | Full refresh | — | — |
customers | A registered customer account on the storefront. | Incremental, Full refresh | date_modified | — |
orders | A customer order placed on the store. | Incremental, Full refresh | date_modified | — |
Troubleshooting
- If the connection fails with an authorization error, the access token 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.