Destinations
Microsoft Clarity
Session recordings and heatmaps, correlated with PixelFox identity.
Microsoft Clarity is browser-only (it has no server ingestion API), so this destination
works differently: PixelFox injects the Clarity tag with your project id and calls
clarity("identify", <distinct_id>), correlating Clarity sessions with the same visitor
ids you see everywhere else in Signals.
Credentials
| Field | Where to find it |
|---|---|
| Project ID | Clarity dashboard → your project → Settings → Overview - the id also appears in the URL (clarity.microsoft.com/projects/view/<PROJECT_ID>/…). (screenshot placeholder) |
Paste it under Destinations → Microsoft Clarity. No secret is involved - the project id is public by nature (it appears in the tag on your pages).
What you get
- Session recordings & heatmaps for every tagged page.
- Identity correlation - Clarity's
identifyAPI receives the PixelFox distinct id, so you can find the recording for a specific visitor/customer journey. - Conflict safety - if your site already loads Clarity, PixelFox detects
window.clarityand injects nothing.
Verify
Clarity's dashboard shows sessions within a few minutes of the first tagged visit. If
nothing arrives, check the browser console for a blocked clarity.ms request (ad
blockers commonly block it) and confirm the project id.