How to Run a Hotjar Survey That Produces Fixable Answers
Open-ended "any feedback?" surveys fill with compliments nobody can act on. Targeting, question shape and response thresholds that turn surveys into tickets.
Hotjar is website behaviour analytics: heatmaps, session recordings and on-site surveys on one script. The free Basic plan records 35 sessions per day; paid plans start around $32/month and lift the cap to 100 sessions a day.
Hotjar is a Malta-founded tool, acquired by Contentsquare in 2021, that records what visitors do on a page rather than just counting them. Google Analytics tells you 80% of sessions left the pricing page. Hotjar shows you where their cursor went before they did.
The stack is three parts: session recordings with rage-click and dead-click flags, heatmaps that aggregate clicks, moves and scroll depth, and feedback widgets (surveys, polls, NPS) that pop up in-context.
The recording cap is the real limit. 35 sessions a day on the free plan sounds generous until you get 4,000 visitors and you are sampling roughly 1% of them. Real conclusions from behaviour data need bigger samples, so most people end up on the $32/month Basic plan within a month.
Page speed is a fair criticism. The single script is leaner than it was in 2020, but it still loads third-party code on every page. Sites chasing perfect Core Web Vitals usually defer it or restrict it to a few key pages.
Since the Contentsquare buyout, the roadmap has leaned toward enterprise add-ons. Smaller teams get fewer new features per year than they did before 2021, and pricing pressure has pushed some of them toward Microsoft Clarity — which is free with unlimited recordings.
Clarity is free and unlimited. Its heatmaps and recordings are solid, and it integrates with GA4 natively. Hotjar wins on surveys, feedback widgets, filtering depth and support. If budget is zero, start with Clarity; upgrade to Hotjar when you need survey rollout and someone to blame for a broken API.