Microsoft Clarity
Microsoft Clarity records sessions and builds heatmaps in the browser. Signal loads the Clarity tag through its consent-gated SDK loader: the tag loads only once the visitor has granted the analytics category, and Clarity’s cookies (_clck, _clsk) are removed when consent is withdrawn.
⚠️
Client-side only. Clarity has no server-side ingestion API: its client API (events, identify, tags, consent) runs in the browser, and its only REST API exports dashboard data. Signal does not deliver any events to Clarity server-side.
Why load Clarity through Datafly Signal
- Consent is enforced before anything loads. Clarity is gated by the same consent state as every other destination, so a withdrawal applies across your whole stack at once.
- Cookie clean-up on withdrawal. Signal removes Clarity’s cookies when consent is withdrawn.
- One place to manage it. The project ID lives in your pipeline configuration rather than in a separate tag.
Prerequisites
- A Microsoft Clarity project.
- The Project ID: in the Clarity dashboard, Settings > Setup > Install tracking code.
Configuration fields
| Field | Required | Notes |
|---|---|---|
project_id | Yes | Clarity project ID. |
Known limitations
- Identity is not forwarded yet. The SDK loader calls
clarity(userId), but Clarity needsclarity("identify", userId), so the call is ignored. A fix is planned. - No consent signal. The loader does not yet send
clarity("consent")after loading the tag, so a Clarity project that waits for a consent signal runs without cookies. A fix is planned.
Blueprint
The Clarity blueprint version is 0.13.0 (client-side; not yet tested against a live Clarity project).