Historian vs.
Session replay shows you what users did. Historian shows you what the page did.
Hotjar and FullStory are session replay and heatmap tools — they record individual visitor journeys so teams can watch how real users navigated, clicked, and encountered friction on their site. They are reactive investigation tools: something goes wrong, you go look at the recordings to understand why.
Hotjar / FullStory watches your users in real time. It answers: what did this specific visitor experience on this page today?
Historian watches your pages over time. It answers: what did this page look like at any given point in history — and what changed?
| Dimension | Hotjar / FullStory | Historian |
|---|---|---|
| Core question | What did this visitor experience on my site? | What changed on this page — and what did it look like? |
| Data source | Live user sessions recorded via JavaScript | Crawled page snapshots — independent of user visits |
| Setup time | Hours — JavaScript snippet installation | Minutes — point at a URL and crawling begins |
| Historical page archive | No — recordings expire; no snapshot of the page itself | Yes — high-fidelity replay of any page at any moment in history |
| Change detection | No — detects user friction, not page changes | Yes — detects, archives, and surfaces page-level changes |
| Session replay | Yes — rich individual visitor recordings | No — Historian tracks pages, not sessions |
| Heatmaps | Yes — click, scroll, and attention heatmaps | No |
| Proactive intelligence | None — reactive investigation tool | Specialist agent layer surfacing insights without manual investigation |
| Requires live traffic | Yes — no users means no data | No — crawls independently of visitor activity |
| Developer dependency | Low — single JS snippet, but persistent maintenance | None |
Session replay tools are reactive by design. Their value appears when you already know something is wrong and need to investigate. You notice a conversion drop in GA, form a hypothesis, filter your recordings, and watch sessions to find the friction point. This is a powerful workflow — but it requires you to know where to look.
Historian is proactive. Its agent layer continuously monitors your tracked pages and surfaces significant changes and patterns without you needing to ask. The insight comes to you rather than requiring you to go find it.
Hotjar and FullStory only have data from the moment instrumentation was in place. Recordings expire after a period depending on plan tier. There is no concept of what a page itself looked like at an arbitrary point in the past — only what a user experienced during a specific recorded session.
Historian stores the pages themselves. A page archived six months ago can be replayed today with full visual fidelity. This is a fundamentally different kind of institutional memory — and it's the kind that answers post-hoc questions like "what did our Black Friday landing page look like last year?" or "when did we change the hero image on this category page?"
Session replay tools are powerful for individual-level investigation: watching a single user's frustrating journey, identifying a specific UI element that caused confusion. The unit of analysis is the session.
Historian's unit of analysis is the page. It tracks how a page evolves, what elements change, how content and structure shift over time. This makes it better suited to catalog-level and editorial questions — not "what did this one user experience" but "how has this page changed, and when?"
A major limitation of session replay tools is that they are entirely dependent on traffic. If a product page, category landing page, or campaign URL receives low or no traffic, there are no recordings and no heatmap data. The page is effectively invisible to these tools.
Historian crawls regardless of traffic. A low-traffic page that quietly had its description updated, its images swapped, or its metadata changed will have that change captured in Historian's archive — even if no user ever visited during the change window.
Used together
FullStory shows you that users are rage-clicking on your PDP. Historian shows you that the add-to-cart button layout changed two weeks ago — and exactly what it looked like before.
Book a 20-minute demo and we'll show you what Historian finds on your own webshop — live.