Additional features, tools, or issues not covered by specific Microsoft Advertising categories
Below are the main areas to check and how to troubleshoot lower-than-expected data in Microsoft Clarity, based on supported behavior.
- Common reasons Clarity shows fewer sessions than GA4
- Clarity and GA4 are different tools and can legitimately show different numbers because they measure and process data differently.
- When consent is not provided in regions where Clarity requires cookie consent (EEA, UK, CH), Clarity changes how it reports data:
- Each pageview is treated as a separate session.
- Funnels, user intent, returning users, and other user-level metrics become inaccurate or degraded.
- Some insights and Copilot answers can be inaccurate.
- If Clarity’s script is missing on some pages, or blocked by browser security (CSP) or network rules, those visits will not appear in Clarity at all.
- If filters or date ranges in Clarity are too narrow, dashboards and heatmaps can appear to have “missing” data even though it exists.
- Sampling limits or recording restrictions
- Clarity does not use sampling and does not impose traffic limits. It is designed to process large volumes of data with no sampling and no per-site traffic cap.
- Clarity is a free service with no paid tier and no feature gating based on traffic volume.
- Impact of consent, ad blockers, CSP, GTM, and similar factors
- Cookie consent (EEA/UK/CH):
- When users in these regions do not provide consent, Clarity still counts pageviews but treats each pageview as its own session.
- Effects include:
- Session count: sessions are counted as pageviews; each pageview creates a new session.
- Pages per session: always 1.
- Funnels: multi-step funnels show full drop-off at each step.
- Unique/returning users: every user is treated as unique; no returning users.
- User intent: more sessions labeled “Low intent.”
- Channel/source/referrer: more traffic labeled as “Other,” “Direct,” or self-referrer.
- Content insights: all sessions appear as “One and Done.”
- These behaviors can make Clarity’s user/session metrics look very different from GA4, especially for multi-page journeys.
- Content Security Policy (CSP):
- If the site uses CSP and Clarity domains are not allowed, browsers block Clarity resources and data will not be collected.
- To allow Clarity, add it to the CSP, typically via
default-src, for example:-
default-src 'self' https://*.clarity.ms https://c.bing.com 'unsafe-inline';
-
- Clarity may load from multiple domains (
https://www.clarity.ms,https://c.bing.com, andhttps://[a-z].clarity.ms), so all must be permitted if using explicit domain lists. - CSP blocking can be confirmed by checking the browser developer console for CSP errors related to Clarity.
- GTM implementation:
- Clarity works when installed directly or via tag managers, but if GTM conditions, triggers, or environments prevent the tag from firing on some pages, those pages will not be tracked.
- Ensure the Clarity tag fires on all intended pages and environments.
- Verifying that Clarity is tracking all pages correctly
Use the following checks:
- Installation correctness:
- Confirm that the Clarity tracking code is installed on all pages that should be monitored. If the site was redesigned or templates changed, verify the script is still present.
- If using multiple projects, ensure the correct project’s tracking code is used on each site.
- Project script validation:
- In Clarity:
- Go to Projects and open the relevant project.
- Select Setup → Installation methods → Install manually and copy the Clarity code.
- Compare this script with the one in the site’s
<head>section, including thesrcURL. - If they differ, replace the existing script with the correct one.
- In Clarity:
- Subdomains:
- Clarity only tracks pages where its script is installed. If subdomains are not tracked, ensure the script is present on those subdomains as well.
- Network collection endpoint:
- Verify that requests to
https://www.clarity.ms/collectare being sent and not blocked:- Revisit setup instructions.
- After loading a page, use the browser’s network tools to look for the
collectrequest and confirm it succeeds.
- Verify that requests to
- CSP verification:
- Open the browser developer console and look for CSP errors mentioning Clarity domains. If present, update CSP as described above.
- Troubleshooting missing recordings and incomplete data
- Dashboard/recordings behavior:
- If the dashboard shows that a URL has recordings but none are visible when selected, this can happen when there are too few sessions in the current filter set to reconstruct a full replay.
- Mitigation:
- Broaden or clear filters (device, country, time range, etc.) to increase the number of sessions.
- Heatmaps and low page views/clicks:
- If heatmaps show low page views or clicks:
- Confirm the tracking code is installed on all relevant pages.
- After installing or changing code, wait at least 30 minutes for heatmaps to be generated.
- Ensure the correct URL is targeted in the heatmap view.
- Clear all filters and set the Time frame to “Today” (or a broader range) to see the latest data.
- If heatmaps show low page views or clicks:
- Installation troubleshooting steps:
- If data is unexpectedly low or missing:
- Re-check installation against the official setup guide.
- Ensure the tracking code was copied directly (not altered by text editors).
- If
collectrequests are not visible, revisit setup and verification steps. - If, after these checks, Clarity still does not track as expected, contact Clarity support as indicated in the installation troubleshooting guide.
- If data is unexpectedly low or missing:
- Summary actions to improve data accuracy
- Ensure Clarity script is present and correct on every page (including subdomains) and matches the intended project.
- Confirm that CSP allows all required Clarity domains and that no CSP errors appear in the console.
- Verify that
https://www.clarity.ms/collectrequests are being sent and succeeding. - Review and broaden filters and time ranges in the dashboard, recordings, and heatmaps when checking for data.
- Be aware that in EEA/UK/CH without consent, Clarity will alter session-level reporting, which can make metrics diverge from GA4.
References: