Microsoft Clarity vs Hotjar: When Free Is Enough

For a creator or small business comparing Microsoft Clarity vs Hotjar, Clarity is a sensible first choice when the job is reviewing heatmaps and watching visitors use a website. Start there if you can name the page you want to improve and make time to review it regularly.

Hotjar now sends new users to Contentsquare, which also offers a free plan [1]. That changes which limits you should compare before choosing.

Choose by the evidence you need. Recordings help you inspect a broken form or confusing page. Visitor feedback helps you ask what someone expected. Historical access matters when a problem reaches you weeks after it happened.

This comparison reviews official product documentation and pricing checked on September 8, 2026. It does not report a controlled performance test or an Anobee conversion result. Examples below are suggested investigations you can run on your own website.

Microsoft Clarity vs Hotjar: the current free-plan comparison

Microsoft lists Clarity as free with no paid upgrade requirement [2]. The table compares it with the Contentsquare Free offering available to new users. If your dashboard still shows a Hotjar Observe or Ask plan, check that account's entitlements before using the new limits.

The distinction between sessions and recordings deserves more attention than the headline allowance. Contentsquare explains that it can collect analytics for a session without keeping a playable replay of that visit [6]. A large monthly session number does not tell you how many individual journeys you can watch.

For a first project, write down your minimum requirement in plain language: “I need enough mobile checkout recordings to investigate failed submissions.” That is more useful than selecting whichever column contains the larger number.

When Clarity is enough

Clarity fits a recurring review of a few important pages. A freelancer can inspect a service inquiry form. Publishers can check whether readers reach useful internal links. For a shop owner, the priority might be taps on a product option that appears unresponsive.

Start with the page that needs work. Narrow the visits you review, watch what happens and check whether you can reproduce the issue. A larger platform has little value until someone makes time for that review.

You can review recordings before they expire

Clarity's ordinary playback window is 30 days. Microsoft separately documents nine-month retention for heatmaps and sessions you label or favorite [5].

That suits a weekly review. It is less comfortable if stakeholders bring you old support cases and expect any specific visit to remain available. Favoriting useful evidence helps, but you must identify it while it is accessible.

Keep a short issue log with the page, device, observed behavior, recording reference and next action. Record the finding in words as well. A link to a replay is a fragile substitute for an explanation when the underlying data can expire.

You need a funnel without another subscription

A funnel is an ordered series of actions, such as visiting a service page, opening a form and reaching a confirmation page. Clarity already supports funnels built from page visits and smart events, with links to filtered recordings and heatmaps [7].

This corrects a common buying assumption. You do not need to leave Clarity merely because your next question involves drop-off between steps. Define the intended journey, verify its events and check whether its existing funnel meets the task.

For example, a low completion rate could reflect a form problem, an unclear offer or visitors who never intended to inquire. Review the sessions around the failed step before changing the page. The funnel locates the gap; your investigation establishes a plausible explanation.

AI summaries help you choose what to watch

Copilot can summarize individual sessions, groups of sessions and heatmaps. Microsoft's documentation also warns that its generative AI can misinterpret information [8].

Use a summary to find a recording worth opening. Before assigning a developer a bug, watch the relevant interaction and reproduce it if possible. A summary that says someone struggled does not establish what caused the struggle.

Clarity's included summaries can be enough for someone with limited review time. The useful test is whether they lead you to clearer evidence faster during your own workflow.

When the Hotjar and Contentsquare route makes more sense

Consider the alternative when watching visits leaves a question you need to ask the visitor directly.

Suppose visitors pause on your pricing page, then leave. The replay may show repeated scrolling between the price and feature list. It cannot establish whether the price was too high, the package was unclear or the visitor was comparing options for later.

Hotjar's survey documentation describes targeting questions by page, events or user attributes and connecting a response with a captured recording. Availability depends on the relevant plan [9]. That combination gives you a route from observed hesitation to a visitor's own explanation.

Ask a specific question close to the decision: “What information is missing before you can choose a package?” Avoid turning every visit into an interruption. Review responses alongside the page and behavior, since the people who answer may differ from those who leave silently.

Test the free offering before budgeting for Growth

The current Contentsquare pricing page lists Growth from $49 per month and separates analytics history from replay access: 13 months for analytics and two months for replays. Session volume, billing selection and additional products affect the final quote [3].

Treat that as a starting configuration to inspect. It is not a promise that every tool, every visitor or every historical replay is covered by the entry price.

Pay when a specific capability changes how you work: a required segment, more useful replay coverage, feedback volume, collaboration or access to older evidence. If you cannot name the limitation you are buying your way past, keep evaluating the free options.

Existing Hotjar accounts need a separate check

For existing customers, Microsoft Clarity vs Hotjar is also a migration decision. You may already have saved research, team habits and a contract worth preserving.

Contentsquare's official transition guidance directs existing Hotjar customers to account and billing information [1]. Before changing tools, record your current capture allowance, replay retention, survey entitlement and renewal terms. Check which evidence remains accessible after a move.

A cheaper subscription can still cost more if it disrupts a review process your team uses every week. Conversely, a paid account nobody opens has little value even if its feature list is impressive.

Compare usable evidence on one real page

Choose one page connected to a business goal and one question you are prepared to act on. Use that same task to evaluate each tool.

For a service business, that might be: “Can mobile visitors complete the inquiry form?” For a publisher, it might be: “Can readers find the next relevant guide?” These are evaluation examples, not findings from Anobee traffic.

1. Define a successful visit. Use an observable action such as reaching a confirmation page. If your analytics setup needs work, start with Anobee's Google Analytics setup guide.
2. Check collection. Confirm the target page and device appear. Review consent and tracking configuration before interpreting missing recordings as missing visitors.
3. Inspect the relevant segment. Keep the page, date range and device consistent. Look at successful visits as well as unsuccessful ones.
4. Reproduce the suspected issue. Check whether the button, layout or form behaves as the replay suggests. Recording reconstruction can differ from the live page.
5. Write one proposed change. Explain what you observed, what remains uncertain and what outcome would support your hypothesis.
6. Evaluate the tool itself. Could you locate useful evidence, share it and return to it? Which unresolved question would require a different feature?

For the example inquiry form, evidence might lead you toward clearer field instructions or a fix for an overlapping mobile element. It might also show no repeatable problem. Both outcomes are useful because they narrow the next investigation.

Avoid treating a handful of recordings as a conversion experiment. They can expose a reproducible defect or generate a hypothesis. Measuring the effect of a change requires an appropriate comparison and enough relevant traffic for the decision.

Anobee's Clarity guide provides broader workflow context. Use the current official documentation cited here for plan limits and retention.

Privacy and setup can decide the choice

Treat collection settings as part of the evaluation. A replay tool needs enough page information to be useful, while private account details and sensitive content require protection.

Clarity masks input boxes and dropdowns in all masking modes. Its documentation says masking changes affect new recordings and cannot be applied retroactively [10]. Check an actual sample after setup, especially on pages that display personal information outside form fields.

For visits from the EEA, UK and Switzerland, Microsoft requires a valid consent signal for full Clarity functionality [11]. A consent banner must communicate the visitor's choice to the tool; its presence alone does not verify the integration.

For either option, review the vendor's current terms against your site and audience. Ask your developer or privacy adviser about a requirement you cannot verify. A vendor's compliance label does not establish that your particular implementation meets every obligation.

During a trial, compare page performance before and after installation and confirm the forms still work. Keep the same device and test conditions. Adding a tracking script is a change worth checking, even when it loads asynchronously.

Choose the tool you can turn into a useful change

The practical Microsoft Clarity vs Hotjar decision starts with your next website question. Choose Clarity when regular heatmap and replay reviews cover the work. Trial Contentsquare when visitor feedback or another specific capability would resolve a gap in that process.

Do one focused review before paying. Save the finding, make a justified change and measure what happened. If visitors are leaving an important page, Anobee's guide to reducing bounce rate offers a next step for examining the page experience.

Your purchase threshold should be concrete: “This feature lets us investigate a problem we otherwise cannot resolve.” Until then, a free tool and a consistent review habit are a reasonable place to work.