Linking Etsy 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 Etsy connector syncs shop, shop sections, listings, 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.
Sync your Etsy shop's orders, listings, reviews and payment ledger.
Register a personal app in the Etsy developer portal to get a keystring and its shared secret, then run Etsy's OAuth flow to grant your shop and keep the refresh token it returns. The token needs the transactions_r, listings_r and shops_r scopes - add billing_r if you want the payment ledger. Leave the shop ID blank and we'll use the shop the token belongs to.
You'll be asked for:
- API keystring: for example
Your app's keystring. - Shared secret: for example
Your app's shared secret. - Refresh 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 Etsy tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API keystring | password | Yes |
Shared secret | password | Yes |
Refresh token | password | Yes |
Shop ID | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
shop | The Etsy shop this connection syncs, including its policies, currency and listing counts. | Full refresh | — | — |
shop_sections | Seller-defined sections used to group listings within the shop. | Full refresh | — | — |
listings | Every listing in the shop across all states (active, inactive, sold out, draft and expired). | Full refresh | — | — |
receipts | Orders placed with the shop, one row per receipt, with buyer, shipping, totals and status. | Incremental, Full refresh | updated_timestamp, created_timestamp | — |
transactions | Line items on shop orders, one row per purchased listing, expanded from the receipts payload. | Full refresh | — | — |
reviews | Buyer reviews left on the shop's transactions, one row per reviewed transaction. | Incremental, Full refresh | created_timestamp | — |
ledger_entries | Payment account ledger: every credit and debit against the shop's Etsy Payments balance, including sales, fees, refunds and payouts. | Incremental, Full refresh | created_timestamp | — |
Troubleshooting
- If the connection fails with an authorization error, the API keystring 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.