Connect Microsoft Clarity¶
Connecting Microsoft Clarity gives Squoosh a source to calibrate your synthetic shoppers' device and geography mix against. This page covers what the connection does, its real limits, and how to set it up from the Integrations page.
Beta — short-window traffic only
Clarity is the most limited connector in the lineup, by the shape of Clarity's own API rather than a Squoosh choice: it only ever reports on the last 3 days of traffic, and it has no conversion signal at all. If you need a conversion rate or a longer calibration window, connect Google Analytics, Shopify, or another analytics source alongside Clarity.
What the connection does¶
Clarity is a traffic calibration source for device and geography (and traffic source, when your Clarity project tracks it). Once connected, Squoosh reads Clarity's live-insights data and builds synthetic shoppers whose device and geography mix matches your real visitors.
Clarity does not calibrate conversion rate — it has no such signal. 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 Clarity¶
You'll need a Clarity Data Export API token (in Clarity, under Settings → Data Export). The token is project-scoped, so there's nothing else to configure.
- In the sidebar, click Integrations.
- In the Microsoft Clarity row, click Connect.
- Enter your Data export API token. Kept private; Squoosh never shows it again after you save it.
- Click Connect.
Squoosh verifies the token live before saving. The row shows Connected — syncing while the first calibration read runs, then Calibrating shoppers from Microsoft Clarity once real data is grounding your shopper pool.
What it grounds¶
| Dimension | Source | Notes |
|---|---|---|
| Device | Clarity's Device breakdown | |
| Geography | Clarity's Country breakdown | |
| Traffic source | Clarity's Source breakdown, when populated | |
| Conversion rate | — | Not available. Clarity has no conversion-tracking signal Squoosh can read. |
Limits and caveats¶
- Always a 3-day window. Clarity's live-insights API hard-caps how far back it reports — every calibration read from Clarity covers only the last 3 days, regardless of Squoosh's usual calibration window. This is a Clarity API limit, not adjustable.
- Rate-limited to a handful of reads per day. Clarity's API allows roughly 10 requests per day per project, so Squoosh refreshes Clarity data at most a few times a day, never on every page load.
- No conversion rate, ever. Clarity can't tell Squoosh whether a visit converted.
- Because of the short window, Squoosh always treats a Clarity read as a partial signal — useful for device and geography mix, not a substitute for a full-window connector like Google Analytics or Plausible.
Troubleshooting¶
| Problem | What to do |
|---|---|
| Connection fails immediately | Confirm the Data Export API token hasn't been revoked in Clarity's project settings. |
| Data looks thin or doesn't update often | Expected — see the 3-day window and daily-quota limits above. |
| I need a conversion rate | Connect a second source with conversion tracking (Google Analytics, Shopify, or one of the other providers) — Clarity itself never reports one. |
Related¶
- Synthetic shoppers — how the calibrated pool behaves and how the match is read.
- Connect Google Analytics and Connect Shopify — full-window sources with conversion tracking.
- Connect a CSV import — an alternative if you'd rather export numbers from another tool.