Hotjar — Examples

Example 1 — Watching five recordings on one step

A support team claims users “get confused by the address form”, but nobody has watched the behaviour behind the claim. The funnel points at one step. Set up the review so it answers that single question, and write what you will take away from it.

Funnel: checkout 900 -> address 720 -> pay 300 -> confirmed 285
(illustrative counts; enough daily traffic to filter)
Claim:  "confusing address form"

Solution

Question: why do people who reach the address step not pay?
Filter:   sessions that reached checkout and did not confirm
Watch:    first 5 matching recordings, not 50
Note:     the repeat action each one shows
Found:    3 of 5 re-typed the postcode after the field rejected it
Keep:     the 420-person gap beside the finding, never on its own

The question names one step and one segment, which is what turns a pile of traffic into evidence: five recordings on that filtered set surface the repeated action, and more would rarely change the conclusion while costing an afternoon. The funnel count stays beside the clip, so the pattern is an illustration of a mechanism and not a claim about everyone. The usual mistake is watching unfiltered sessions and learning nothing, and the other is presenting a single recording as if it were representative.