Connect WooCommerce

Previous Next

Connect WooCommerce

Connecting WooCommerce gives Squoosh your store's real order data — a geography hint and a conversion count — to ground synthetic-shopper calibration against. This page covers what the connection does, its real limits, and how to set it up from the Integrations page.

Beta — orders only, not traffic

WooCommerce has no visit or session data of its own — only orders. It connects as a conversion source, not a traffic source: it contributes a geography hint (from order billing addresses) and a real order count, but device and traffic-source mix have to come from somewhere else. Pair it with a traffic source like Google Analytics, Plausible, or another connector if you want the full picture.

What the connection does

WooCommerce is a conversion source. Once connected, Squoosh reads your store's recent orders and derives a geography breakdown (weighted by order count, not visits) plus a real order total for the window. This is a genuinely different role from Google Analytics or Shopify Analytics, which contribute both traffic and conversion data — WooCommerce contributes conversion-side signal only.

The connection is not required to run a test — Squoosh can build a pool from a general e-commerce mix without it. For how the calibrated pool behaves and how the match is measured, see Synthetic shoppers.

Connect WooCommerce

You'll need a WooCommerce REST API key pair, created in your WordPress admin under WooCommerce → Settings → Advanced → REST API → Add key (Read permission is enough).

  1. In the sidebar, click Integrations.
  2. In the WooCommerce row, click Connect.
  3. Enter:
  4. Store URL — your store's base URL, e.g. https://shop.example.com.
  5. Consumer key and Consumer secret — from your WooCommerce REST API key. Both kept private; Squoosh never shows them again after you save them.
  6. Click Connect.

Squoosh verifies the store live before saving. Once connected, the row shows Orders connected · geo calibrated — WooCommerce's honest ceiling. It does not progress to a "conversion calibrated" state on its own; blending its order data with a separate traffic source's session count is a capability that's still rolling out.

What it grounds

Dimension Source Notes
Geography Order billing address, country Weighted by order count, not by visits — a genuinely different signal than a visit-based geography breakdown.
Device / traffic source — Not available. WooCommerce's Orders API carries no device or referrer data.
Order count Completed and processing orders in the window A real count, reported honestly even when it's zero.

Limits and caveats

  • Conversion-only. WooCommerce contributes geography and an order count, not a device or traffic-source mix.
  • Geography is order-weighted, not visit-weighted. One order counts as one sample — customers who visited but didn't order aren't represented in this breakdown.
  • Up to 500 orders per calibration read. If your store does more volume than that in a window, Squoosh still reports what it fetched, flagged as a partial read.
  • A conversion RATE requires a paired traffic source. WooCommerce alone gives you an order count, not a rate — Squoosh needs a traffic source's session count to turn that into a percentage.

Troubleshooting

Problem What to do
Connection fails immediately Confirm the store URL is correct and reachable over HTTPS, and that the WooCommerce plugin's REST API is enabled on the store.
"the WooCommerce REST API route was not found" The WooCommerce plugin isn't active, or its REST API isn't enabled — check both in your WordPress admin.
No geography data shows up Orders need a billing country on file — check that your checkout collects one.
Connect Amplitude Connect BigCommerce