Skip to main content

Microsoft Clarity: heatmaps and session recordings

Why use heatmaps if you already have Analytics?

Google Analytics tells you how many people reach your website. Microsoft Clarity helps you see what visitors try to do and where they get stuck. You do not have to configure a separate event for every click to spot common behaviour patterns.

Clarity offers heatmaps, session recordings and behavioural signals. You might notice that an important button is too far down the page, or that people keep clicking an image they expect to be a link. These insights are not mind-reading: you can see what happened, but you still need to investigate why.

1. Get started on a Demona website

  1. Go to clarity.microsoft.com, sign in and create a project using your website's public address.
  2. In Demona, open Settings → Marketing → Analytics and enter your Google Tag Manager container ID (GTM-…). If you use that container for statistical tracking, select the appropriate consent category.
  3. In Clarity, open Settings → Setup, choose the Google Tag Manager integration and install the Clarity tag in the correct container. In GTM, review its firing rules and consent requirements, then publish the container.
  4. Enable and configure Demona's cookie banner. In a private browser window, test what happens both when you reject and when you accept tracking, then check that test data arrives in Clarity.

Important: Clarity's standard installation snippet may contain inline JavaScript. Demona does not accept inline JavaScript in the custom <head> field for security reasons. We therefore recommend the GTM approach, provided you test the consent behaviour carefully. See Analytics and tracking for Demona-specific details.

Consent signals matter, especially in Europe

Since 31 October 2025, Clarity has enforced consent-signal requirements for visitors in the EU/EEA, UK and Switzerland. Demona passes Google Consent Mode v2 signals to GA4 and GTM, which Clarity can also support. But you must still verify that your Clarity tag inside GTM receives the appropriate signal and respects the visitor's choice. If it does not, you may need Clarity's own Consent V2 API or a compatible consent management integration.

Neither a cookie banner nor a tracking integration replaces proper information about how personal data is handled. Review the service's data-processing terms and your own privacy notice as well.

2. Heatmaps: where do people click and how far do they scroll?

  • Click map: which elements attract the most clicks? If a non-clickable image gets a lot of attention, the interface might need clearer cues.
  • Scroll map: how far down the page do visitors go? If only a few people reach your main offer or contact button, consider moving it higher.
  • Device breakdown: mobile visitors may behave differently from desktop users. Review both views separately.

For example, visitors to a service page often stop scrolling around the pricing section, but the quote-request button is at the very bottom. Try placing a button closer to pricing, then check whether enquiries improve.

3. Session recordings: understand where visitors struggle

The Recordings view lets you replay the sequence of actions during a visit: scrolling, clicks and page navigation. Clarity can mask sensitive fields and content, but always check its masking settings, especially on pages with forms.

Do not redesign a page because of one unusual recording. Look for recurring patterns across multiple sessions: repeated clicks that do nothing, people leaving at the same form step or visitors struggling to find contact details. A short usability test with real people can help confirm what you think you are seeing.

4. Three signals to watch first

  • Rage clicks: repeated rapid clicks in the same area. They may suggest the interface is not behaving as expected.
  • Dead clicks: clicks that do not produce a visible response. Check whether an element looks like a button when it is not.
  • Quick exits or shallow scrolling: perhaps the first screen does not answer the visitor's question – or perhaps it answers it immediately.

Clarity signals highlight areas worth investigating; they are not automatic proof that something is wrong.

5. One simple improvement cycle

  1. Choose one important page, such as a service description or quote-request page.
  2. Review its mobile heatmap and a handful of relevant session recordings.
  3. Write down one specific problem: “Too few visitors see the contact button.”
  4. Change one thing in the Demona editor, such as the button position or headline.
  5. Collect fresh data and compare it with the previous period. Be especially careful about drawing conclusions when traffic is low.

Privacy: review Clarity's Masking settings, avoid collecting unnecessary personal information and share recordings only with authorised colleagues. Microsoft advises against using Clarity on websites that target people under 18.

To complement the behavioural picture with traffic numbers, read our Google Analytics 4 guide.

TIPS AND TRICKS

Set up tracking and consent before exploring heatmaps.

Demona's technical guide explains how to connect GTM and configure the cookie banner so you can focus on visitor behaviour.