How Microsoft Clarity works
Clarity is a small script you add to your site, usually through Google Tag Manager. Once installed it records what happens in the browser — where the pointer moves, what is clicked, how far the page scrolls, where the visitor hesitates — and plays it back as a session recording, or aggregates it into heatmaps and scroll maps for a page.
Alongside the recordings it flags behaviour that usually means frustration. Rage clicks are repeated clicks in the same spot, normally on something that looks interactive and is not. Dead clicks are clicks that produce no response at all. Excessive scrolling and quick backwards navigation point at people who could not find what they came for. Each flag is a filter you can use to find the sessions worth watching.
Microsoft provides it at no cost, and it can be connected to GA4 so an audience or segment defined in analytics can be opened as recordings. That pairing is the useful part: the analytics tells you which page has a problem, and Clarity lets you watch it happening.
Why Microsoft Clarity matters
Analytics counts behaviour but never explains it. Knowing a page loses visitors does not tell you that the phone number is not tappable on Android, or that a sticky banner covers the submit button on a small screen. Watching a few sessions does, and those faults tend to be quick to fix once seen.
Because it costs nothing, it removes the usual excuse for skipping qualitative work on smaller sites. For a business in Nepal running a modest budget, having session playback and heatmaps on every page is a genuine advantage — most of what it finds is layout and mobile usability, which can be corrected without a developer contract.
Common mistakes with Microsoft Clarity
The first is treating it as an analytics replacement. It is not a system of record: its job is explaining a problem you have already identified elsewhere, and its counts should not be reconciled against GA4 or an ad platform.
The second is watching sessions at random. Unfiltered playback is hours of people behaving normally. Always arrive with a question and filter to it — a page, a device, a rage-click flag, an audience that abandoned a form.
The third, and the one that matters legally, is privacy. Recording tools capture the page as the visitor sees it, which can include what they type. Clarity masks input by default, and that default should stay on. Whatever you record, your privacy policy must say that session recording happens and why, and any consent mechanism you operate must actually gate the script.
What to do about it
Install it through a tag manager rather than editing the theme, so it can be removed or gated cleanly. Check the masking settings before you look at anything, exclude any page that handles payment or sensitive information, and confirm the privacy notice reflects what you have switched on.
Then use it deliberately. Take a step where funnel analysis shows people leaving, filter to that page on mobile, watch a handful of sessions, and write down what you see rather than what you assume. Turn each observation into a change you can test, and check the heatmap again afterwards. A short, regular review beats an occasional afternoon of watching everything.
