Why isn’t Microsoft Data Clarity working accurately for my website?

Angga 5 Reputation points
2026-04-16T01:39:14.1566667+00:00

Why isn’t Microsoft Data Clarity working accurately for my website? It’s different from before, when the results were very accurate. Lately, more and more data isn’t being detected, and I’ve noticed a pretty significant discrepancy in the data. I wonder what the problem might be? I’ve already tried contacting support via email, but I haven’t received a response yet.

Community Center | Not monitored

1 answer

Sort by: Oldest
  1. AI answer

    2026-04-16T01:39:30.9166667+00:00

    Several common issues can cause Microsoft Clarity to appear less accurate or to miss data compared to what was seen previously. Work through these checks to narrow down the cause:

    1. Confirm the tracking code is still installed correctly
    • Ensure the Clarity script is present in the <head> of all pages that should be tracked.
    • If the site was redesigned, moved to a new template, or new pages/subdomains were added, verify the script was carried over everywhere.
    • In Clarity, go to Projects → Setup → Installation methods → Install manually, copy the script, and compare it to what is on the site. If it differs, replace the old script with the current one.
    1. Check for CSP (Content Security Policy) blocking Clarity If a CSP was recently added or tightened, the browser may now be blocking Clarity resources, which reduces or stops data collection.
    • Open the browser developer console on the site and look for CSP errors mentioning clarity.ms or c.bing.com.
    • If present, update the CSP to allow Clarity, for example by adding it to default-src, such as:
        default-src 'self' https://*.clarity.ms https://c.bing.com 'unsafe-inline';
      
    • If using more granular directives, ensure https://www.clarity.ms, https://c.bing.com, and https://[a-z].clarity.ms are allowed where required.
    1. Verify Clarity is not blocked by environment or access rules If parts of the site were moved behind authentication, IP restrictions, VPN, or internal-only environments, Clarity may not be able to load assets or record correctly.
    • Ensure pages and styling assets (CSS, fonts) are accessible to Clarity and not restricted by IP, geolocation, or referrer rules.
    • If the site blocks bots or specific user agents, allow requests with "User-Agent" : "Clarity-Bot" so recordings and heatmaps can render correctly.
    1. Check subdomains and new pages If data is missing only for certain sections:
    • Confirm the script is installed on all subdomains and pages that should be tracked. Clarity does not automatically track subdomains without the script on each.
    1. Review consent behavior in EEA/UK/Switzerland If the site targets users in the EEA, UK, or Switzerland, or receives traffic from there, consent handling changes can affect data volume:
    • Clarity requires explicit consent before placing cookies in these regions.
    • If consent is not correctly conveyed via the Clarity client API, sessions may fragment or not be fully recorded, leading to apparent data loss or discrepancies.
    • Implement or verify the consent integration as described in the Clarity client API documentation.
    1. Check for styling/asset issues that affect what is visible in Clarity If recordings or heatmaps look wrong (missing elements, no styling), it can appear as if data is inaccurate:
    • Ensure CSS and fonts are publicly accessible and served with correct MIME types.
    • Avoid temporary or short-lived stylesheet URLs; make styling resources available long-term so Clarity can cache and reuse them.
    1. Verify filters and sampling in Clarity Apparent discrepancies can come from filters rather than tracking issues:
    • In heatmaps, when opened from a recording, Clarity automatically filters by that recording’s URL and device type. Remove or adjust filters if clicks or views seem missing.
    • For click maps, if no clicks appear, it may simply mean no clicks match the current filters.
    1. Confirm that Clarity is still collecting sessions at expected scale
    • Clarity can record up to 100,000 sessions per project per day. If traffic has grown beyond that, not all sessions will have recordings, though metrics still track sessions.
    1. Next steps with support Since email support has already been contacted:
    • Include specific examples: affected URLs, time ranges, screenshots of discrepancies, and any CSP or console errors.
    • If styling or rendering is wrong, include links to recordings/heatmaps and a list of failing resource URLs.

    If, after checking installation, CSP, consent, and filters, data still appears incorrect, continuing to work with Clarity support (for example via the in-product feedback/smiley icon) is recommended so they can inspect the project configuration and backend signals.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.