Connect BigCommerce¶
Connecting BigCommerce lets Squoosh verify access to your store's order data ahead of using it for calibration. This page covers what the connection does today, its current limits, and how to set it up from the Integrations page.
Beta — connecting and verifying only, for now
BigCommerce is our newest connector and the earliest-stage one: connecting verifies your store credentials live, but Squoosh doesn't yet use BigCommerce order data to calibrate shoppers. The row stays at Connected — validating rather than progressing further — that's accurate, not a bug. Calibration grounding from your orders is on the way; this page will be updated when it ships. If you need order-derived calibration today, see Connect WooCommerce, which has reached that stage.
What the connection does today¶
Connecting BigCommerce checks that your store hash and API token are valid and that Squoosh can reach your store — nothing more yet. Once BigCommerce reaches the same stage as WooCommerce, it will contribute a geography hint (from order billing addresses) and an order count as a conversion source, the same role WooCommerce plays today.
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 BigCommerce¶
You'll need your store's hash (the short identifier in your BigCommerce control-panel URL) and an API token with orders read access, created under Settings → API → Store-level API accounts → Create API account.
- In the sidebar, click Integrations.
- In the BigCommerce row, click Connect.
- Enter:
- Store hash — letters and digits only, e.g.
abc123store. - API token — kept private; Squoosh never shows it again after you save it.
- Click Connect.
Squoosh verifies the store hash and token live before saving. The row shows Connected — validating — the connection is confirmed working, but it isn't calibrating anything yet.
Limits and caveats¶
- Verification only — no calibration data yet. BigCommerce doesn't contribute to your shopper pool's calibration at this stage, regardless of what the connection status shows.
- Store hash is validated strictly — only letters and digits are accepted, matching BigCommerce's own store-hash format.
- Watch this page (or the connector's detail view) for updates once order-derived calibration ships.
Troubleshooting¶
| Problem | What to do |
|---|---|
| Connection fails immediately | Confirm the store hash is correct (check your BigCommerce control-panel URL) and that the API token hasn't been revoked. |
| "check that the store hash ... is correct" | BigCommerce returned a 404 for that store hash — double-check it against your control-panel URL. |
| The row stays at "Connected — validating" | Expected for now — see the note above. This isn't an error. |
Related¶
- Synthetic shoppers — how the calibrated pool behaves and how the match is read.
- Connect WooCommerce — the equivalent connector, already at the order-calibration stage.
- Connect Google Analytics and Connect Shopify — traffic sources that calibrate today.