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
Connecting verifies your store credentials live. Squoosh does not yet use BigCommerce order data to change how your AI shoppers behave. The connection remains in the validating stage. The order parser has fixture coverage but has not been validated against a live store; this connector remains at the auth stage.
What the connection does today¶
Connecting BigCommerce checks access to the Orders endpoint using your store hash and API token. The adapter can read order counts and billing-country geography, but this connection does not yet contribute to calibration. Orders provide no session denominator, so Squoosh does not calculate a conversion rate from them.
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 AI 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 > Store-level API accounts. Create a dedicated account with Orders: read-only (store_v2_orders_read_only). The verification request uses the Orders endpoint, so Information & Settings access is not required. See BigCommerce API accounts.
- 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. A successful connection remains in the validating stage and does not yet affect calibration.
Store-level tokens do not expire with time and cannot be changed individually. To replace a compromised token, delete its API account, create a replacement with Orders read-only access, and reconnect Squoosh. Deleting an account is irreversible and affects other integrations using it. See BigCommerce credential revocation.
Limits and caveats¶
- Verification only. 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. Squoosh accepts only letters and digits as a path-safety restriction.
- Watch this page (or the connector's detail view) to see when 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 its API account still exists. |
| "check that the store hash ... is correct" | BigCommerce returned a 404. Check the store hash against your API account details; the response does not establish which entity was missing. |
| The connection stays in the validating stage | Expected at this stage. See the note above. |
Related¶
- AI shoppers: how the calibrated pool behaves and how the match is read.
- Connect WooCommerce: another orders-only connector with its own documented limits.
- Connect Google Analytics and Connect Shopify: additional store and analytics connections.