{ "ids": [ "hotjar", "microsoft-clarity" ], "title": "Hotjar vs Microsoft Clarity: current tools and limits", "deck": "Understand Hotjar’s move to Contentsquare before comparing replay, heatmaps and review workflows.", "answerHeading": "Which current service should a new team evaluate?", "answer": "New users researching Hotjar are now directed to Contentsquare; new standalone Hotjar accounts are no longer available. Compare the current Contentsquare offer with Microsoft Clarity, then match capture, retention, feedback and review needs. Clarity is a free hosted tool for visual behaviour investigation. Existing Hotjar accounts need their own migration and historical-data assessment.", "rows": [ [ "Current new-user route", "Contentsquare; standalone Hotjar sign-up ended", "Microsoft Clarity" ], [ "Visual investigation", "Heatmaps and replay through Contentsquare", "Heatmaps and session recordings" ], [ "Feedback scope", "Survey workflows in the current Contentsquare offer", "Evaluate visual evidence and any separate feedback tool" ], [ "Free entry", "Recurring Contentsquare Free tier", "Free hosted Clarity service" ], [ "Capture and retention", "Confirm current product-specific limits and access periods", "Ordinary recordings 30 days; selected data longer" ], [ "Existing history", "Establish Hotjar migration and export arrangements", "A new collection does not recreate earlier visits" ], [ "Selection proof", "Current successor workflow meets the defined review brief", "Clarity workflow meets the same review brief" ] ], "scenarios": [ { "name": "New mobile-form review", "question": "Can the team understand a visible point of friction?", "left": "Evaluate the relevant replay and heatmap tools in Contentsquare.", "right": "Filter recordings and heatmaps around the same form journey.", "note": "Hypothetical brief: use an instrumented test route and masked synthetic inputs." }, { "name": "Existing Hotjar account", "question": "What happens to saved findings and historical access?", "left": "Confirm the account-specific transition and any export arrangements.", "right": "Treat a move to Clarity as a new implementation.", "note": "A new script cannot recover sessions that were never collected or have expired." }, { "name": "Feedback plus behaviour", "question": "Does the team need visitors to explain the problem?", "left": "Scope the survey workflow and response entitlement.", "right": "Decide how a separate feedback channel would connect to visual findings.", "note": "Do not infer motivation solely from a click pattern or a replay." }, { "name": "Monthly review cadence", "question": "Will the evidence still be available at review time?", "left": "Check each current Contentsquare product’s data-access period.", "right": "Plan around ordinary recording retention and selected retained sessions.", "note": "Set a review owner and preserve permitted findings before the relevant retention window ends." } ], "sections": [ { "id": "current-product", "title": "Compare the current successor, not old Hotjar packages", "navLabel": "Current identity", "paragraphs": [ "The familiar Hotjar name can lead to an outdated buying shortlist. Its official site now directs new users to Contentsquare, so an evaluation should use the present successor product and its current plan. Old Hotjar daily capture or Observe and Ask prices are not a new-purchase quotation.", "For an existing account, make a separate inventory of collections, permissions, findings and historical access. A migration decision should distinguish evidence that must be retained from data that the team does not need to carry forward." ] }, { "id": "review-evidence", "title": "Turn recordings into a bounded review process", "navLabel": "Review process", "paragraphs": [ "Choose one journey and one question, such as whether a mobile visitor can complete a form after reading an error. Record the pages and device context needed to investigate it, then check masking before collecting real sessions.", "Review behaviour alongside completion events and direct feedback where available. A repeated click is a useful clue, but the team still needs to establish the cause and verify a proposed fix. Assign an owner and a follow-up check to each finding." ] } ], "faqs": [ { "question": "Can a new user still create a Hotjar account?", "answer": "The official Hotjar transition page says new Hotjar accounts can no longer be created. New users are directed to Contentsquare." }, { "question": "Is Contentsquare Free only a trial?", "answer": "No. It advertises an ongoing Free plan, with a separate introductory Growth trial. Scope and limits vary by product." }, { "question": "How long does Clarity retain ordinary recordings?", "answer": "Microsoft’s retention documentation gives ordinary playback data a 30-day period. Labeled or favorited sessions and heatmap data can have longer specified periods." }, { "question": "Does free Clarity remove setup responsibilities?", "answer": "No. The team still needs appropriate collection, masking, access and consent configuration, and a process for reviewing the findings." } ], "id": "hotjar-vs-microsoft-clarity", "heading": "Hotjar (now Contentsquare) vs Microsoft Clarity", "kicker": "Analytics comparison", "description": "Hotjar vs Microsoft Clarity: current tools and limits. Compare free access, implementation scope, operating costs and practical buying requirements.", "checkedAt": "2026-10-15", "researchTag": "Buying requirements comparison", "researchLimit": "The buying briefs and acceptance checks are hypothetical evaluation proposals. They are not hands-on tests, performance measurements or vendor scores.", "datasetDescription": "Seven practical differences, four hypothetical buying briefs and a four-row acceptance checklist.", "type": "workflow-buying", "exampleTable": { "caption": "Hypothetical buying checklist; the conditions below are proposed acceptance checks, not measured results.", "headers": [ "Requirement", "Evidence to collect", "Acceptance condition" ], "rows": [ [ "Measurement scope", "An agreed journey, events and relevant context", "Both evaluations answer the same defined question" ], [ "Collection quality", "A synthetic journey reconciled with expected records", "Counts and missing context can be explained" ], [ "Commercial scope", "Written plan limits and operating responsibilities", "Every required capability has an owner and a budget" ], [ "Review process", "A short report and follow-up action", "The intended team can repeat the investigation" ] ] }, "sources": [ { "url": "https://contentsquare.com/hotjar/", "facts": "Hotjar (now Contentsquare): current product scope, access boundaries and operating requirements." }, { "url": "https://contentsquare.com/pricing/", "facts": "Hotjar (now Contentsquare): current product scope, access boundaries and operating requirements." }, { "url": "https://clarity.microsoft.com/", "facts": "Microsoft Clarity: current product scope, access boundaries and operating requirements." }, { "url": "https://learn.microsoft.com/en-us/clarity/about-clarity", "facts": "Microsoft Clarity: current product scope, access boundaries and operating requirements." }, { "url": "https://learn.microsoft.com/en-gb/clarity/data-retention", "facts": "Microsoft Clarity: current product scope, access boundaries and operating requirements." }, { "url": "https://learn.microsoft.com/en-us/clarity/faq", "facts": "Microsoft Clarity: current product scope, access boundaries and operating requirements." } ], "relatedLinks": [ { "path": "/guides/analytics-measurement-plan/", "title": "Write an analytics measurement plan" }, { "path": "/guides/software-total-cost/", "title": "Estimate the complete software cost" }, { "path": "/guides/software-buying-checklist/", "title": "Prepare a repeatable software evaluation" }, { "path": "/categories/web-product-analytics/", "title": "Browse web and product analytics" } ] }