Hotjar Alternatives: Four Tools for Replay, Friction and Product Analysis
Choose Microsoft Clarity for a free website investigation workflow, Mouseflow for a planned conversion-analysis program, FullStory for detailed session investigation, and PostHog for replay connected to engineering-owned product analytics. These Hotjar alternatives solve different problems. First compare them with Contentsquare, where Hotjar now lives, then test the capture, retention and privacy requirements behind your actual investigation before moving the installation.
On this page
Hotjar alternatives compared
The free entry plans below have different capture and retention limits; paid scope needs a separate budget.
| Alternative | Starting cost and allowance | Best fit | Main tradeoff |
|---|---|---|---|
| Microsoft Clarity | Free service | Website heatmaps and replay investigation | Ordinary recordings expire after thirty days |
| Mouseflow | Free: 500 monthly sessions, one website | A conversion program with defined funnels and form questions | Surveys, form analytics and exports have different paid boundaries |
| FullStory | Free: 30,000 monthly sessions, up to ten users | Session investigation and debugging | Advanced analysis and paid plans need a quote |
| PostHog | Free: 5,000 recordings and 1 million analytics events monthly | Replay joined to product behavior and technical work | Each product has its own meter and capture decisions |
Sources: Microsoft Clarity overview, Clarity retention, Mouseflow plans, FullStory Free, PostHog pricing.
At Martechdevs, we scope analytics and tracking work around the decision a team needs to make. A replay tool earns its place when someone can find a meaningful failure, reproduce it, fix it and check the outcome. A large library of unwatched recordings adds storage and review work without completing that job.
Hotjar, Contentsquare and the existing account
Hotjar is now part of Contentsquare. New buyers looking for Hotjar are directed to Contentsquare's current platform. Treat the current product and your actual subscription as the baseline instead of comparing competitors with a retired Hotjar entry plan. Official Hotjar destination.
Contentsquare Free lists 200,000 monthly analytics sessions, one project and one month of data access. Its replay allowance captures 5% of sessions, capped at 10,000 monthly recordings. Growth lists thirteen months of analytics access and two months of replay access at a volume-dependent price. Keep those capture and retention measures separate when comparing heatmaps, funnels, surveys and individual recordings. Contentsquare plans.
For an existing account, record the current allowance, remaining commitment, retained reports and cancellation conditions before making a savings forecast. A new-account offer does not establish the terms of an existing contract. Export the reports and annotations that need to remain accessible and confirm which historical recordings can be retained through supported routes.
Our Hotjar versus Microsoft Clarity comparison covers that specific choice. This shortlist adds alternatives for a deeper product or conversion workflow, rather than treating every heatmap product as interchangeable.
The four alternative workflows
Microsoft Clarity
Clarity is our first trial when a website team needs to inspect navigation, clicks and friction without adding a software subscription. Microsoft's overview describes a free service with recordings, heatmaps and dashboard insights. Clarity scope.
- Best for: a website owner with a clear investigation question and someone responsible for fixes.
- Pros: a no-cost entry point for connecting a suspicious page or behavior with individual visits.
- Cons: ordinary replay retention is short, and consent configuration needs explicit implementation.
- Free plan and startup offer: the service is free; a startup discount is unnecessary for that subscription line.
- Choose it if: the required pages, devices and customer paths produce usable evidence within the retention window.
- Skip it if: the site targets users under eighteen, or the required historical replay access exceeds the tested scope. Microsoft excludes under-eighteen audiences in its usage guidance.
Clarity retains ordinary recordings for thirty days. Favorites and a randomly selected sample can remain for up to nine months. That is not a nine-month archive of every recording. If the team investigates only once a quarter, its operating cadence can be incompatible with the ordinary window. Recording retention.
Clarity requires a valid consent signal for full functionality for visits from the EEA, UK and Switzerland. The relevant configuration controls cookie access and must receive changes in the user's choice. Test the actual consent path rather than assuming the presence of a banner communicates a signal. Clarity Consent Mode.
Mouseflow
Mouseflow is a candidate when the investigation should connect replay with a maintained conversion process. Its plan matrix separates basic heatmaps, feedback surveys, form analytics and export capability. Select the plan from the particular question the team must answer. Mouseflow plan matrix.
- Best for: a conversion team that has defined the important funnel, form and follow-up work.
- Pros: replay, friction analysis and funnel investigation can sit in one operating workflow.
- Cons: a low-volume entry plan does not include every form, survey or export capability.
- Free plan and startup offer: Free includes 500 sessions monthly and one website; a paid-plan trial is available, with no separate startup reduction assumed.
- Choose it if: the selected tier covers the actual form and funnel requirements at the intended volume.
- Skip it if: the team would buy a tier solely for a feature it has no process to use.
The published matrix places feedback surveys in Advanced and form analytics, data export and REST API access in Premium. It lists one month of history on Free, three on Essential, six on Advanced and twelve on Premium. Price the required combination, including the number of websites, rather than choosing from session volume alone. Feature and retention boundaries.
Confirm currency and billing commitment in the offer or checkout. Mouseflow's terms allow fees in euros or US dollars, with the order specifying the payment basis. Use the selected currency and payment period when comparing the quote with your current bill. Mouseflow commercial terms.
FullStory
FullStory is the first candidate here when the main work is reconstructing a difficult customer session and connecting it with debugging evidence. FullStory Free includes basic analytics and debugging tools, thirty thousand monthly sessions and up to ten users. Paid Business, Advanced and Enterprise scope is quoted. FullStory plans.
- Best for: teams investigating customer problems across replay and technical context.
- Pros: a substantial free session allowance and a route into a wider behavioral-analysis platform.
- Cons: advanced dashboards, StoryAI and other paid capabilities should not be assumed from the free offer.
- Free plan and startup offer: FullStory Free is a continuing plan; any other startup benefit needs its own approved terms.
- Choose it if: the team can locate, explain and hand off representative failures in the selected configuration.
- Skip it if: the required paid scope costs more than the investigation work can justify.
FullStory Free also grants the vendor rights to anonymized non-PII data, including model training and partner sharing, while its FAQ distinguishes paid-plan customer ownership; include that difference in the plan acceptance. Free-plan data rights.
Free lists twelve months of replay and analytics retention. Other plans can have different replay and analytics windows, so record both on the purchasing sheet. An aggregate chart can remain available after the underlying session is no longer replayable. FullStory Free, retention definitions.
The FullStory and Amplitude comparison covers the broader decision between session investigation and behavioral analysis. A team may need both capabilities, but that does not automatically mean it needs two subscriptions.
PostHog
PostHog is a candidate when engineers and product analysts want replay alongside events, flags and experiments. Its free monthly replay allowance is five thousand recordings, separate from the one-million-event analytics allowance. PostHog pricing.
- Best for: a team that owns instrumentation and wants to connect an observed problem with product behavior.
- Pros: the same operating stack can support investigation, analysis and controlled product changes.
- Cons: multiple billing meters and capture rules require someone to maintain them.
- Free plan and startup offer: recurring product allowances cover small workloads; approved startup credits should be modelled separately from later usage.
- Choose it if: engineering can maintain identity, capture and the route from a finding to a tested fix.
- Skip it if: the team only wants a narrow website-review workflow and would leave the broader setup unowned.
PostHog billing caps can stop ingestion and processing. Additional data after the applicable cap is reached is lost, rather than waiting for a later upgrade. Set alerts and choose the limit with the person who needs the evidence, because a cost control can also remove the incident session being investigated. Billing limits and data loss.
The PostHog pricing guide explains the product meters. The Pendo alternatives guide covers a different requirement when the team also needs to show onboarding guides or change in-product behavior.
A workload comparison before a price comparison
Consider a hypothetical site with 80,000 eligible visits monthly. Its team needs to investigate the 12,000 visits that enter a checkout path, retain useful evidence for ninety days and collect survey responses from customers who abandon that path. Those are separate requirements.
| Requirement | Model quantity | Implication | Acceptance evidence |
|---|---|---|---|
| Whole-site visits | 80,000 monthly | Above FullStory Free and PostHog free replay volume | Explicit eligible capture plan |
| Checkout visits | 12,000 monthly | A smaller investigation population | Targeting covers entry and the preceding context |
| Random replay sample | 25% of whole-site visits | Approximately 20,000 recordings | Sample coverage checked by device and outcome |
| Useful history | 90 days | Ordinary thirty-day recording windows are insufficient | Required replay still accessible at review time |
| Customer explanation | Targeted survey responses | Replay alone does not provide the reason | Survey scope and response allowance confirmed |
A 25% sample is not a guarantee that every rare failure is captured. If a technical failure occurs in forty visits and sampling is independent, the expected captured count is ten. The actual count can differ. A sample can support pattern investigation while still missing the individual customer incident a support team needs to reconstruct.
Define whether capture is whole-site, random, session-triggered or restricted to a path. Check whether a trigger retains preceding context and whether that behavior matches the product's actual implementation. A session that starts recording only after a failure can omit the action that caused it.
Do not remove surveys from the cost comparison when leaving a product that supplied them. Add the required survey product or tier and ensure the same team can connect answers with the relevant journey. Heatmaps reveal interaction patterns; the reason behind a decision often needs direct customer explanation and further testing.
Retention, privacy and useful capture
Retention is a purchasing requirement tied to the work. A weekly conversion review can use a shorter replay window than a quarterly investigation of an intermittent customer complaint. Define the longest useful lookback before comparing free allowances.
| Product reference | Retention fact | Operating consequence |
|---|---|---|
| Clarity ordinary recordings | Thirty days | A regular review or approved evidence-preservation process |
| Contentsquare Free analytics and replay access | One month; replay capture 5%, up to 10,000 monthly | Capture coverage and history need separate checks |
| Mouseflow Essential | Three months | Confirm required features as well as history |
| FullStory Free | Twelve months replay and analytics | Paid capability needs still require their own check |
Sources: Clarity retention, Contentsquare, Mouseflow, FullStory.
Review privacy before useful capture becomes broad capture. FullStory's Private by Default setting masks text unless allowed. Its guidance distinguishes masking, which preserves interaction events, from exclusion, which omits the targeted element and its interactions. Web images need particular care because text masking does not mask them. FullStory capture rules.
Apply the same concrete acceptance exercise to whichever product you select: a typed message, customer name, uploaded image, payment-related screen and sensitive URL. Check the captured result and the underlying collection settings. Recheck after UI changes, especially when new fields inherit selectors or components from an existing form.
A privacy control can legitimately remove an event needed for a funnel. Update the analytical definition rather than weakening the control to recover a convenient chart. Record which population is measurable so the team does not interpret restricted capture as evidence that no one experienced the problem.
The investigation-to-fix workflow
Start with a specific symptom: mobile visitors reach the address form but fail to continue. Define the relevant device, page version, traffic source and outcome before watching recordings. Compare failed visits with successful visits from the same operating context.
Create a short issue record with the observed behavior, reproduction steps, affected population, suspected mechanism and owner. Keep observation separate from interpretation. Repeated clicks on a button can be evidence of a blocked interaction, a slow response or impatient behavior; the recording alone may not establish the cause.
After a fix, monitor the same eligible population and outcome definition. A change in traffic composition or consent coverage can move the measured conversion rate without the interface becoming better. Use a suitable controlled experiment when causal attribution matters and the available traffic supports it.
For a hypothetical operating budget, a quoted $450 monthly package plus $300 monthly of analysis and maintenance costs $750. At an assumed $30 contribution per additional completed order, recovering that cost through extra orders alone requires 25 additional orders monthly. This is a planning threshold, not a predicted result from installing a replay tool.
Hotjar competitors by investigation job
| Situation | First candidate | Runner-up | Decision reason |
|---|---|---|---|
| Small website team with weekly reviews | Microsoft Clarity | Contentsquare Free | Usable replay without a software fee |
| Form and funnel optimization program | Mouseflow at the required tier | Contentsquare | Exact diagnostic and feedback scope |
| Support and engineering incident investigation | FullStory | PostHog | Session context, retention and technical evidence |
| Product team connecting behavior to releases | PostHog | FullStory paid scope | Instrumentation and operating ownership |
| Existing Hotjar account with no unmet requirement | Current Contentsquare scope | Alternative after a bounded trial | Migration value above transition work |
Hotjar replacement checklist
Read diagram as text
- Investigation and retention requirements to Current Contentsquare scope sufficient.
- Current Contentsquare scope sufficient to Existing setup repair or continuation: Yes.
- Current Contentsquare scope sufficient to Engineering-owned product analysis: No.
- Engineering-owned product analysis to PostHog or FullStory trial: Yes.
- Engineering-owned product analysis to Clarity or Mouseflow trial: No.
- PostHog or FullStory trial to Capture privacy and task evidence.
- Clarity or Mouseflow trial to Capture privacy and task evidence.
- Existing setup repair or continuation to Capture privacy and task evidence.
- Capture privacy and task evidence to Required investigation complete.
- Required investigation complete to Scope or capture repair: No.
- Scope or capture repair to Engineering-owned product analysis.
- Required investigation complete to Cost acceptance and controlled cutover: Yes
Checklist
- The replacement answers a named investigation question.
- Sessions, events, websites and survey responses use separate budget lines.
- Replay retention covers the actual investigation cadence.
- Capture covers the necessary context before the failure.
- Consent changes and sensitive content behave as intended.
- An ordinary team member can find and explain the required session.
- Historical evidence and annotations have an accepted retention plan.
- Findings have owners and post-fix outcome checks.
Use the analytics tool selector skill for the requirements. Request an analytics implementation scope when capture, consent and the reporting population need to be made consistent before a replacement can be judged.
Keep reading
Browse all Product Analytics guides
Product AnalyticsFullStory vs Amplitude: Product Decisions, Session Evidence and Full Cost
Choose FullStory or Amplitude by the decision your team needs to make. Compare event and session billing, replay retention, identity and practical trial requirements.
Jafrin Akter AloLast updated 12 min read
Product AnalyticsPendo Alternatives: Five Options for Onboarding, Analytics and Cost
Compare five Pendo alternatives by guides, analytics, active users and full cost. Includes current pricing, workload examples and migration acceptance checks.
Jafrin Akter AloLast updated 12 min read
Product AnalyticsPostHog Pricing: Estimate Each Product Separately
Estimate PostHog costs by event type, web and mobile recordings, flag requests and add-ons. Includes tier calculations and billing-limit consequences.
Jafrin Akter AloLast updated 13 min read
Analytics & tracking
See the implementation scope, deliverables and acceptance checks.
Questions people ask
Is the old Hotjar free allowance still the right comparison baseline?
New buyers are directed to Contentsquare, whose current Free plan has its own session allowance, retention and features. Compare that offer and the actual terms of an existing account before using an old Hotjar tier in a savings estimate. Preserved reports, outstanding commitments and required capabilities can make the account-specific decision different from a new signup comparison.
Does Clarity keep every recording for nine months?
Ordinary Clarity recordings are retained for thirty days. Favorites and a randomly selected sample can remain for up to nine months, so the longer period does not cover every visit. Set the review cadence around the ordinary window and confirm the permitted preservation route for evidence the team needs later. A quarterly review can otherwise arrive after the useful recording expires.
Can FullStory Free's session allowance replace a paid analytics package?
It can cover a suitable basic investigation workload, but session quantity alone does not establish equivalent features. The free plan includes basic analytics and debugging, while capabilities such as advanced dashboards and StoryAI need paid scope. Test the specific reports, permissions and handoffs the team relies on before counting the paid package as removable from the budget.
Will a PostHog spending cap preserve excess replay data for later?
The billing-limit guidance says additional data beyond the applicable limit is lost after ingestion and processing stop. Raising the limit later cannot restore evidence that was never retained. Choose capture rules and alerts with the investigation owner, and consider the value of missing an incident when setting the cap. Each product's allowance and cap require separate attention.
Can a replay prove that a page change increased conversion?
A replay can show an individual experience and help explain a suspected mechanism. It cannot by itself establish the causal effect of a page change across the eligible population. Compare consistent outcomes and populations, account for changes in traffic or capture, and use an appropriate controlled experiment when the decision requires a causal estimate.
Sources
- Official Hotjar and Contentsquare destination
- Contentsquare current plans
- Microsoft Clarity overview
- Clarity retention and feature FAQ
- Clarity Consent Mode
- Mouseflow plans and feature boundaries
- Mouseflow currency and payment terms
- FullStory plans
- FullStory Free allowances
- FullStory retention definitions
- FullStory Private by Default
- PostHog pricing
- PostHog billing limits

Written by
Jafrin Akter AloData Engineer and Co-founder at Martechdevs and Growth and Analytics Partners
Jafrin writes practical guides to marketing technology, customer data, analytics and AI workflows. Martechdevs is a Growth and Analytics Partners company.