Linking Skio 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.
Contents
This source is currently in alpha. The interface and available tables may change.
The Skio connector syncs your Shopify subscription data into PostHog: subscriptions, subscription lines, orders, customers, products, and more. Use it to analyze subscription revenue and churn alongside your product data.
Skio's data model mirrors Shopify's GraphQL objects: a Skio subscription is a Shopify SubscriptionContract, a Skio customer is a Shopify Customer, and each record's platformId column holds the Shopify GID (for example gid://shopify/SubscriptionContract/123), so you can join synced tables against Shopify data.
Prerequisites
You need a Skio account and an API token. In your Skio dashboard, click API in the left navigation bar, set a name for the token, and generate it.
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 Skio, you'll need:
- API token: the token you generated under API in your Skio dashboard.
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 Skio tables support incremental sync on updatedAt (recommended) or createdAt.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
subscriptions | Subscription contracts, mirroring Shopify SubscriptionContract objects. | Incremental, Full refresh | updatedAt, createdAt | — |
subscription_lines | Line items on a subscription, mirroring Shopify SubscriptionLine objects. | Incremental, Full refresh | updatedAt, createdAt | — |
orders | Orders generated by subscriptions, mirroring Shopify Order objects. | Incremental, Full refresh | updatedAt, createdAt | — |
order_line_items | Line items on an order, mirroring Shopify LineItem objects. | Incremental, Full refresh | updatedAt, createdAt | — |
customers | Storefront customers with subscriptions, mirroring Shopify Customer objects. | Incremental, Full refresh | updatedAt, createdAt | — |
addresses | Shipping addresses attached to customers and subscriptions. | Incremental, Full refresh | updatedAt, createdAt | — |
products | Products available on subscription, mirroring Shopify Product objects. | Incremental, Full refresh | updatedAt, createdAt | — |
product_variants | Product variants available on subscription, mirroring Shopify ProductVariant objects. | Incremental, Full refresh | updatedAt, createdAt | — |
Troubleshooting
If syncs fail with Invalid response from authorization hook, the API token is invalid or has been revoked. Generate a new token under API in your Skio dashboard and update the source credentials.
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.