Microsoft Clarity Not Recording Sessions: What to Check
When Microsoft Clarity is not recording sessions, the break can sit at the tracking code, the tag deployment, the consent layer, the browser or the account setup. A missing snippet, a blocked script, a consent gate that never resolves or a deployment that never published can all produce the same symptom: no recordings appear. Before reinstalling anything, isolate whether the tracking is missing, firing but blocked, or firing but not surfacing sessions.
Table of Contents
- 01.Three different failure states
- 02.What to check first
- 03.Tracking code and tag deployment
- 04.Consent and browser behavior
- 05.Traffic and processing
- 06.How to test the fix
- 07.How to validate the final result
Three different failure states
No recordings can mean three different things. The tracking code may not be installed on the page at all. The code may be installed and firing but blocked by consent, an ad blocker or a browser setting. Or the code may fire correctly but sessions do not appear in the Clarity dashboard because of coverage, traffic or processing reasons. These are different problems and the fix for each is different.
| State | What you see | How to confirm |
|---|---|---|
| Not installed | No Clarity script on the page | Search the page source for the Clarity snippet |
| Installed but not firing | Script present but no network request | Check the network tab for Clarity requests |
| Fires but no sessions | Request sends but dashboard is empty | Check traffic, coverage and processing time |
What to check first
- Confirm the Clarity project ID in the snippet matches the project you are viewing.
- Confirm the snippet is present on the page and not only on a staging environment.
- Confirm the script is not blocked by consent, an ad blocker or a browser extension.
- Confirm the page actually receives real visitor traffic.
- Confirm enough time has passed for sessions to process.
Tracking code and tag deployment
Clarity can be installed through a direct snippet, through Google Tag Manager or through a platform integration. Each path can fail differently. A direct snippet can be removed during a theme update. A GTM tag can be unpublished or moved to a container that no longer loads. A platform integration can disconnect. Confirm the deployment path actually used on the live site, not the one you intended to use.
If you deploy through GTM, open the GTM container and confirm the Clarity tag is published in the live environment. A tag that exists only in a draft workspace will never fire on production. If you use a direct snippet, confirm it sits inside the head or body of the live page and that the project ID is correct. A single wrong character in the project ID sends data to a different project.
Consent and browser behavior
Clarity is designed to work without cookies, but consent banners and privacy extensions can still block the script from loading. If your consent setup conditionally loads scripts based on user choice, confirm Clarity is not gated behind a consent category that most visitors decline. Browser extensions and strict privacy settings can also prevent the script from executing. This is expected behavior and not a defect in the tracking.
Traffic and processing
Clarity needs real visitor sessions to record. A page with no traffic will never produce recordings regardless of how well the tracking is installed. Equally, sessions do not always appear instantly. Processing time varies and depends on the platform. Do not assume a broken installation just because a session recorded minutes ago is not yet visible.
How to test the fix
- 1.Open the live page in a clean browser session without privacy extensions.
- 2.Open the network tab and confirm a Clarity request fires on page load.
- 3.Interact with the page and navigate as a real visitor would.
- 4.Wait for the processing window, then check the Clarity dashboard for the session.
How to validate the final result
A valid installation shows a Clarity network request on page load and produces sessions in the dashboard after processing. If the request fires but sessions never appear, the problem is likely traffic, coverage or processing rather than installation. If the request never fires, return to the deployment and consent checks.
Frequently Asked Questions
Does Clarity need consent to record?
Clarity is designed to operate without cookies, but your specific consent setup and local requirements may still affect whether the script loads. Confirm how your consent layer treats the Clarity script rather than assuming it is always exempt.
Why do sessions not appear immediately?
Session processing takes time and varies by platform. A session recorded recently may not be visible yet. Confirm the script fires first, then allow processing time before concluding the installation is broken.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Microsoft Clarity Heatmaps Not Showing Data: A Troubleshooting Guide
Empty heatmaps usually come from low traffic, wrong URL targeting or a page that changed since the heatmap was set up. Confirm the cause before recreating the heatmap.
Microsoft Clarity Tracking the Wrong Pages: How to Diagnose URL Problems
Sessions on unexpected URLs usually come from query parameters, redirects, subdomains or dynamic routing. Understand your URL structure before assuming the tracking is broken.
Hotjar Recordings Not Showing: Common Tracking and Session Problems
Recordings can be missing even when tracking is installed, because of consent, sampling, page targeting or browser restrictions. Distinguish a tracking problem from a capture problem first.