ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Clarity's session replay shows you the DOM-level reason users abandon a form — but on pages with sensitive inputs, masking is the real engineering decision. Here's how to enable, mask, and verify it before production.
Clarity snapshots the DOM, so plain-text account numbers and health data can leak into replays. Add element-level masking in your front-end code and verify in staging before opening access.
Session replay masking granularity change in Microsoft Clarity The goal is to choose a masking strategy that protects sensitive UI regions while preserving enough behavioural data for useful heatmaps and replays. Clarity permits two patterns: apply a broad mask to the whole page and selectively unmask safe areas, or start with an unmasked page and mask only
clarity