01
Contribution margin per channel
Revenue minus COGS, shipping and ad spend for every channel and campaign.
Margin after ads
E-commerce
WooCommerce + Kimo
WordPress store orders and products. Orders, products and customers joined with your ad spend, so you see real contribution margin per channel.
- Auth
- API key
- Sync
- Hourly
- Setup
- ≈ 3 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / woocommerceSyncing
Sync loghourly
- Succeeded:orders+1,588 rowsnow
- Succeeded:products+807 rows2m ago
- Succeeded:line_items+2,426 rows4m ago
- Succeeded:orders+1,645 rows6m ago
Rows synced · 30 days
117.7M
Workspaces
18%
What you can do
What teams build with WooCommerce
WooCommerce on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Repeat purchase cohorts
See how first-order channel and product drive second and third orders.
90-day repeat rate
03
Product performance
Revenue, units and refunds by product and variant, with stock-out alerts.
Top SKUs
Objects & tables
Exactly what gets synced
Kimo maps WooCommerce into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 13 fields
Tables
orders
Incremental≈ 31,400,000 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| customer_id | id | References customer |
| total_price | decimal | Measure |
| currency | enum | Low-cardinality dimension |
| created_at | timestamp | Incremental cursor |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw WooCommerce tables to a certified metric
A starter model Kimo suggests the moment WooCommerce is connected. Every join is editable.
WooCommerce · Store performance
Orders and line items joined with ad spend on UTM campaign and date.
- WooCommerceorders
- Meta Adsads_insights
- Google Adscampaigns
Model
utm_campaign · date
Measuresrevenueorders
Revenue · last 30 days
$29.1K+2.0% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect WooCommerce in 3 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Create a read-only key in WooCommerce
Use a dedicated key scoped to read access, so it can be rotated independently.
- 2
Paste it into Kimo
Keys are encrypted with a per-workspace key and never shown again.
- 3
Choose streams
Pick which objects to sync, starting with orders.
- 4
Validate and sync
Kimo tests the key, backfills history and keeps it fresh (hourly).
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect WooCommerce
Step 2 of 3 · Kimo demo workspace
- Reaching host
- Authenticating
- Reading schema
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair WooCommerce with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
WooCommerce questions, answered
By default Kimo syncs WooCommerce hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
WooCommerce · API key · Hourly
See your WooCommerce data in Kimo in 3 min.
Try it on the live demo workspace first, then connect your own account when you are ready.
