How Hotjar works
Hotjar is a behaviour analytics tool. You add a script to your site and it starts recording what visitors do, rather than only how many of them arrived. It produces heatmaps showing where people click, move and stop scrolling; session recordings that replay an individual visit as a video; and small on-page surveys or feedback widgets that ask a visitor a question while they are still on the page.
Where an analytics report tells you that a page converts poorly, Hotjar is where you go to see why. It is a commercial product, sampled rather than exhaustive on smaller plans, and its limits and pricing change, so check the current terms before you build a process around a particular volume. In practice it is best switched on for a specific investigation rather than left running on every page indefinitely.
Why Hotjar matters
Numbers tell you where the problem is; watching tells you what it is. A form that loses people at the third field, a mobile button hidden under a sticky bar, a price that makes people scroll back up and leave — none of that appears in an analytics report, and all of it shows up in a short run of recordings.
It is also the quickest way to end an internal argument. When one person insists the page is clear and another insists it is confusing, recordings of real visitors settle it without anyone having to win. That matters especially for sites in Nepal, where most traffic arrives on mid-range Android phones over mobile data, and where problems that never appear on an office laptop are obvious the moment you watch a real session.
Common mistakes with Hotjar
Watching recordings without a question is the big one. It is genuinely absorbing, and it can eat an afternoon while producing nothing you can act on. Decide first what you are trying to learn — why this form is abandoned, whether this section is ever read — and stop when you have the answer.
Two more are worth naming. A heatmap counts clicks, not intent: a heavily clicked element may be clicked because people are lost, or because they think an image is a link. And a tool that records behaviour brings real privacy duties with it, so mask form fields, say plainly in your privacy notice that sessions are recorded, and take consent where the law that applies to you requires it.
What to do about it
Run it in short campaigns. Pick one page that matters, switch on a heatmap and recordings for it, watch until the same problem repeats itself, fix that problem, then switch it off again. Pair each observation with a number from analytics so you can tell whether the fix actually worked, and write down what you saw, because recordings expire and memory does not survive the next quarter.
Ask questions as well as watching. One well-timed survey on the enquiry or checkout page — what nearly stopped you today? — usually produces clearer answers than any heatmap, because the visitor tells you directly. Treat all of it as evidence feeding a specific change, which is the working method behind conversion rate optimisation. If a subscription is out of reach, Microsoft Clarity covers much of the same ground free of charge.