Microsoft Clarity
Validation pendingProduction setup or live validation is incomplete. Contact us before using these setup instructions.
The adapter is deployed, but no live production connection or successful collection has been verified.
What it collects
SyncingBeam reads aggregate project insights from Clarity's Data Export API, including supported behavior metrics such as sessions, scroll depth, and rage clicks. It does not download recordings or heatmaps.
Setup
A Clarity project administrator generates a Data Export API token under Settings → Data Export. Store that token with the project ID in the encrypted connector setup. There is no OAuth callback or shared environment credential.
Limits and daily collection
Clarity allows 10 requests per project per day, shared with your other tools and MCP use. SyncingBeam uses up to 8 requests per UTC day and leaves 2 spare. Failed calls can consume that allowance. Exports cover only the previous 1–3 days; data older than 72 hours cannot be recovered. Responses are limited to 1,000 rows with no pagination.
Daily buckets approximate rolling 24-hour windows. Missed-day recovery supports additive counts only; unique users and averages are unavailable for recovered days. URL query strings and fragments are removed before storage.
Consent and age restrictions
From 2025-10-31, Clarity enforces consent signals for visits from the EEA, UK and Switzerland (CH). Configure your consent management platform or Clarity Consent API and verify consent before collection. Missing signals limit Clarity features. Connecting an export token does not configure consent on your website.
Do not use Clarity on websites or apps aimed at people under 18.
Before production use
Verify one export, selected dimensions, scheduled collection, the daily request budget, a revoked token, and a token without access to the project. Keep the status at validation pending until those checks pass on the intended account.