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.
Untagged Clarity replays drown in traffic. Tag sessions by feature flag at load time to filter recordings, heatmaps and rage clicks to the cohort you actually changed.
Learn how to use Microsoft Clarity session replays and heatmaps to identify UX friction points like rage clicks and dead clicks that standard analytics miss.
Server metrics look healthy but users still complain about slow pages. Dynatrace RUM with session replay reveals hidden client‑side bottlenecks—here’s how to set it up, what to watch for, and how to turn the data into faster experiences.
A decision guide for enabling Microsoft Clarity session replay in production: compare replay vs. heatmaps, implement consent-gated loading with masking and SPA route tracking, and validate with a concrete checklist.
Clarity records DOM mutations and replays them against a snapshot rather than capturing video. Here is the architecture, the masking boundary, and the checks that catch silent failure.
Goal Determine the upper bound on the retention period for Session Replay data in Microsoft Clarity and how to confirm it. Constraints Clarity’s default retention is 30 days; the UI offers an override but the maximum value is not publicly documented, and no API exposes the cap. Unresolved behavior When the retention setting is changed to 90 days, the dashboa
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
As of the current Microsoft Clarity release, Session Replay data is automatically deleted after 30 days, with no user-configurable retention extension in the UI. When a site upgrade disrupts the tracking script, no documented rollback or recovery mechanism exists, forcing a choice between accepting the fixed retention window or building a separate export wor
clarity
dynatrace