Set up your bannerConfigure Your ToolsSession Recording and Heatmaps

Microsoft Clarity

How to configure Microsoft Clarity at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service, Personalise the website

Overview

This guide explains how to implement different privacy configurations for Microsoft Clarity and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. This guide covers the Microsoft Clarity tracking script on a website (session recordings, heatmaps, insights), with Consenter passing consent to Clarity through the Consent API v2 (consentv2).

Out of scope. Clarity for mobile apps; custom identifiers set through the Clarity client API (custom-id), which would link recordings to known users and require separate assessment.

What the service does in this scope. Clarity captures how the page renders and user interactions such as mouse movements, clicks and scrolls. It sets the first-party cookies _clck (Clarity user ID, persisted per site) and _clsk (session), and, when advertising storage is granted, Microsoft cookies including MUID ("Identifies unique web browsers visiting Microsoft sites … used for advertising, site analytics, and other operational purposes").

Legal role. Microsoft states that Clarity "operates as a data controller". Clarity customers in the EU contract with Microsoft Ireland Operations Limited (MIOL).

Configurations included.

ConfigurationSummary
Configuration A — Lower riskScript loads after analytics consent; ad_Storage denied (no MUID); Strict masking.
Configuration B — Higher risk (default settings)Script loads after consent; ad_Storage and analytics_Storage granted (MUID set); Balanced masking (default).

No configuration without prior consent. Microsoft requires a valid consent signal for visitors from the EEA, the UK and Switzerland. When consent is denied, Clarity continues to run without cookies and still sends /collect calls. Recording sessions without consent still processes personal data, and Microsoft does not document this mode as a consent-free configuration. In both configurations below, Consenter blocks the script until consent.

ActionConfiguration A — Lower riskConfiguration B — Higher risk (default settings)
Cookies by default (Settings > Setup)OffOff
Script loadingBlocked until consentBlocked until consent
consentv2 after consentanalytics_Storage: "granted", ad_Storage: "denied"analytics_Storage: "granted", ad_Storage: "granted"
Masking modeStrictBalanced (default)
Consenter Manager entriesOne entry (Microsoft as Individual Controller)One entry (Microsoft as Individual Controller)

Step 1 — Configure Microsoft Clarity

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Higher risk (default settings)
1Processing purposesOperator decisionImprove the serviceImprove the service; Personalise the website (only if insights are used to adapt the site)
2Setting cookies by defaultSettings > Setup, turn off setting cookies by defaultOffOff
3Script loadingConsenter script blocking for the Clarity entryBlocked until consentBlocked until consent
4Consent signalwindow.clarity('consentv2', {analytics_Storage, ad_Storage})Analytics granted, ads deniedBoth granted
5Masking modeSettings > Masking > Masking modeStrict — entire content maskedBalanced (default) — numbers, email addresses and input content masked
6Element-level maskingSettings > Masking > Mask by elementAdd elements containing personal dataOptional
7Data retentionNot configurable. Recordings 30 days; labelled or favourited sessions 13 months; heatmaps and click data 13 monthsFixedFixed
8Withdrawalconsentv2 with both values "denied"; Clarity stops writing cookies for that userConfigure and testConfigure and test

Configuration A — Lower risk

  • Intended use: UX analysis with minimal content capture.
  • Resulting processing: interaction data and page structure; text content masked; _clck and _clsk only.
  • Why lower risk: no Microsoft advertising identifier; page text not captured.
  • Remaining risk: Microsoft is controller of the data; retention is fixed.

Configuration B — Higher risk (default settings)

  • Intended use: UX analysis with readable page content and the Microsoft Advertising link.
  • Resulting processing: as A, plus non-sensitive page text, and MUID and related third-party cookies used across Microsoft sites.
  • Why higher risk: a cross-site Microsoft identifier is set and more page content is captured.

Step 2 — Map the configuration in the Consenter Manager

Processing location (applies to all entries). EU customers contract with MIOL. Clarity data is stored in Microsoft Azure. Microsoft Corporation is a US company and can be required to disclose data in its possession, custody or control regardless of storage location. The United States is listed as a potential processing and access location.

Configuration A — Lower risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesImprove the serviceSession recordings and heatmaps for UX analysis.
Tracking methodFirst party tracking (cross-session)_clck persists the Clarity user ID per site.
IdentifierDevice identifiers, IP address_clck user ID; IP address with each request.
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP address, Aggregated site statisticsInteractions and rendering; heatmaps.
Legal role of data recipientIndividual ControllerClarity "operates as a data controller".
Personalisation modelNo personalisation—
Maximum storage duration13 monthsHeatmaps and labelled sessions; recordings 30 days.
Processing locationEU contracting entity (MIOL); Microsoft Azure; United States as potential processing and access locationSee note above.

Configuration B — Higher risk (default settings)

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesImprove the service; Personalise the website (if applicable)As used by the operator.
Tracking methodThird party tracking (crosssession, cross-website)MUID identifies browsers across Microsoft sites.
IdentifierDevice identifiers, IP address_clck, MUID.
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP address, Aggregated site statisticsAs A, with less masking. Add "User-provided data" only if unmasked elements display content the visitor entered.
Legal role of data recipientIndividual Controller—
Personalisation modelNo personalisationSelect "Group based (behaviour)" only if Clarity insights drive site variants.
Maximum storage duration13 months—
Processing locationAs ASee note above.

Privacy-policy follow-up

  • Microsoft (MIOL / Microsoft Corporation) as independent controller; session recording and heatmaps; cookies _clck, _clsk and, for B, MUID and related Microsoft cookies; masking applied; retention 30 days / 13 months; consent under ePrivacy / TDDDG and GDPR legal basis stated separately; US transfer and potential access by US authorities.

Verification checklist

  • Before consent: no request to clarity.ms; no _clck, _clsk or MUID.
  • After consent (A): _clck/_clsk set; no MUID.
  • Masking: recordings reviewed for unmasked personal data.
  • Withdrawal: cookies no longer written after consentv2 denied.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page