Linking ShopWired as a source
This source is currently in beta. It works end to end, but you may still hit rough edges. Let us know if you do.
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.
Contents
The ShopWired connector syncs your e-commerce store data into the PostHog Data warehouse, so you can analyze your products, customers, and orders alongside your product analytics data.
Prerequisites
You need a ShopWired account with access to API keys. API credentials inherit full access to your store's data.
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 ShopWired, you'll need:
- API key and API secret – create these under Account > API keys in your ShopWired account.
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.
Orders support incremental sync using their creation date. ShopWired doesn't expose a modified-date filter, so incremental syncs only pick up newly created orders — changes to existing records are only captured by a full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
API secret | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
products | A product in your ShopWired store, including pricing, stock, and SEO fields. | Full refresh | — | — |
categories | A category used to group products in your ShopWired store. | Full refresh | — | — |
brands | A brand assigned to products in your ShopWired store. | Full refresh | — | — |
tags | A tag used to label and filter products in your ShopWired store. | Full refresh | — | — |
customers | A customer account (regular or trade) registered on your ShopWired store. | Full refresh | — | — |
orders | An order placed on your ShopWired store, including line items, addresses, and totals. | Incremental, Full refresh | created | — |
order_statuses | An order status configured on your ShopWired store (e.g. Paid, Dispatched). | Full refresh | — | — |
vouchers | A discount voucher customers can redeem on your ShopWired store. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key or secret is invalid or has been revoked. Generate new credentials under Account > API keys in ShopWired, then reconnect.
- Syncs of very large stores can be slowed by ShopWired's API rate limit (2 requests per second sustained). The connector backs off and retries automatically, so this shows up as a longer sync, not a failure.
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.