Microsoft Clarity. Check the implementation of heatmap and session replay.

Microsoft Clarity implementation checklist

Evaluate cookie consents (CMP), GTM installation, sensitive data masking and Clarity configuration alongside GA4. Result generated locally in the browser.

Verified June 23, 2026. This is a self-assessment; it does not inspect your Clarity project and is not legal advice.

Full Clarity Guide (GTM, GDPR, Hotjar comparison)

Original editorial checklist based on Microsoft documentation: Consent Mode, masking, IP blocking, GA4 integration.

Wynik: 0% · 0/16
Answer the questions below

Zgody i CMP

Clarity must receive a valid consent signal and cannot set cookies without valid consent.

-

Clarity Consent Mode is enabled and the consent status is sent to Clarity before cookies are saved.

The script may load before consent, but Clarity should receive DENIED and not save cookies until a valid GRANTED signal.

Clarity is listed in the privacy policy as a behavioral tool.

The user must be aware that the session may be recorded (subject to legal assessment).

Przy odmowie Clarity pokazuje status DENIED i nie zapisuje cookies _clck ani _clsk.

/collect requests may still occur. Verify the status with clarity('metadata', ...) and no Clarity cookies.

CMP poprawnie mapuje wymagane sygnały analytics_storage i - jeśli dotyczy - ad_storage.

The classification depends on how Clarity is used and local requirements. Agree on category mapping with your privacy officer.

Instalacja i GTM

Jeden poprawny tag - bez duplikatów hardcode + GTM.

-

Clarity is implemented via GTM (or one controlled channel), not duplicated in the page code.

Dual installation can distort sessions, heatmaps and deployment diagnostics.

The Project ID in the tag corresponds to the actual Clarity project.

Wrong ID = data on the wrong account or no data.

Tag jest opublikowany w kontenerze GTM produkcyjnym (nie tylko w wersji roboczej).

Preview ≠ produkcja - sprawdź opublikowaną wersję kontenera.

The implementation has been tested on mobile and desktop.

Część ruchu ecommerce to mobile - heatmapy muszą zbierać oba.

Privacy and cloaking

Ochrona PII w nagraniach sesji i heatmapach.

-

The masking mode and additional selectors have been tested on real recordings.

Input fields and drop-down lists are masked in all modes. For other content, use Strict/Balanced mode, selectors or data-clarity-mask='true'.

Office, agency and test environment IPs excluded.

Clarity blocks IPv4 and CIDR ranges, but does not stably support IPv6, dynamic addresses, or most mobile traffic.

Pages with sensitive data (e.g. customer panel) are excluded or additionally masked.

Consider excluding URLs or locking the tag in high-confidential zones.

Zespół wie, że nagrania sesji mogą zawierać dane osobowe - są procedury dostępu.

Limit access to Clarity to people who need to analyze UX.

Konfiguracja i GA4

Smart events, integracja z GA4 i wykorzystanie danych.

-

Smart Events correspond to key business actions, and rage/dead clicks are analyzed as separate UX signals.

Clarity automatically detects Smart Events and allows you to create up to 20 of your own. Rage clicks and dead clicks are separate frustration filters.

Integracja Clarity z GA4 używa właściwego Account ID, Measurement ID i Property ID - jeśli jest potrzebna.

Microsoft notes that the integration does not provide segments or play URLs in GA4.

The team knows Clarity does not replace conversions and revenue from GA4.

Clarity = UX quality; GA4 = business metrics and campaigns.

There is a process of reviewing recordings (e.g. monthly) while optimizing key pages.

Without the habit of viewing sessions, the tool has no effect.

Need to implement Clarity with GA4?

I help configure Clarity with CMP, connect it to GA4 and GTM, and mask sensitive data.

GA4 implementation Przewodnik Clarity Hub Web Analytics