Additional features, tools, or issues not covered by specific Microsoft Advertising categories
Clarity should be installed only once per page. Multiple Clarity tracking codes on the same page cause conflicts and unpredictable behavior, which explains why the global project is capturing most sessions while the page-specific project records only a few.
Key points and recommendations:
- Single Clarity script per page
- Each page should load only one Clarity tracking code snippet.
- Having both a global project script and a product‑specific project script in the
<head>of the same page leads to inconsistent recording behavior.
- Use one Clarity project and segment instead of duplicating scripts
- Keep the global Clarity code and remove the additional product‑specific Clarity script from the product pages.
- Use Clarity’s filtering and features (for example, filtering by URL or using the Clarity Live Extension’s Select area and View recordings options) to analyze product pages separately.
- From Clarity Live, fire the product page or popup and select the View recordings icon to quickly see recordings relevant to that experience from the last three days.
- Ensure cookies and consent are correctly configured
- In Clarity Advanced Settings, make sure cookies are enabled so that recordings can be linked into proper sessions across pages. If cookies are off or consent is not passed correctly (especially for EEA/UK/Switzerland visitors), session tracking and recordings can be fragmented or reduced.
- If the site targets users in the EEA, UK, or Switzerland, ensure consent status is conveyed to Clarity as described in the Clarity client API documentation; otherwise, session recordings and funnels can be impacted.
- Verify that Clarity is not being blocked
- If a Content Security Policy (CSP) is configured on the site, confirm that Clarity domains are allowed (for example via
default-src 'self' https://*.clarity.ms https://c.bing.com 'unsafe-inline';). - Use the browser developer console to check for CSP errors that might be blocking one of the scripts.
- If a Content Security Policy (CSP) is configured on the site, confirm that Clarity domains are allowed (for example via
- Avoid multiple projects for the same traffic unless truly needed
- If separate projects are absolutely required (for example, different environments or domains), ensure that only one project’s script is present on any given page.
After removing the extra product‑specific script and relying on a single global Clarity script plus URL/area-based filtering, recording counts for the product page should align and be consistent.
References: