Historian vs.
Hotjar / FullStory
Session replay shows you what one visitor did. Historian shows you what the page looked like, what changed, and what each element earned.
The short version
Hotjar and FullStory are built around the individual visitor: session recordings, heatmaps and, in Hotjar's case, surveys and feedback. They are excellent for watching how real people move through a page and where they get stuck.
Historian is built around the page and its history. It keeps a copy of your pages every day, draws its heatmaps on the version that was live, ties every click to the revenue that followed, and lets agents tell you which change moved the numbers.
Both draw heatmaps. The difference is what the heatmap is attached to: a recording period in one case, a dated version of the page with its revenue in the other.
Side-by-side comparison
| Hotjar / FullStory | Historian | |
|---|---|---|
| Core question | What did visitors experience on this page? | What changed on this page, and what was it worth? |
| Data source | A JavaScript snippet that records visitor sessions | A tracking script on your store (sessions, page views, clicks, orders), a daily capture of your pages, and your ad accounts |
| Session replay | Yes — the core of both tools | No — Historian follows pages and elements, not individual visitors |
| Heatmaps | Yes — clicks, moves and scroll depth | Yes — on every captured version of the page, coloured by clicks, conversion or revenue per click, per template, device and traffic source |
| Revenue per element | Not the focus; the heatmap shows behaviour | Yes — revenue per click, the products bought after the click, and where visitors went next |
| Archive of the page itself | No — recordings show what a visitor saw during a session | Yes — your pages captured every day with a real browser, from the day you start |
| Change detection | No — they surface friction, not page changes | Yes — what changed on the page, where and when, connected to the numbers |
| Surveys and feedback | Yes in Hotjar | No |
| Proactive insights | AI summaries of recordings and feedback | A catalog of specialist agents that run on a schedule and deliver insights with an estimated revenue impact and the evidence |
Key differences in depth
One visitor vs. one page over time
Session replay is unbeatable when you want to see a real person struggle with a form or miss a button. The unit is the session.
Historian's unit is the page and its elements over time. The question is not what one visitor did, but how the page changed, how each element performed before and after, and which change cost or earned money.
Heatmaps with a date and a price
A heatmap that covers a period during which the page changed mixes two pages into one picture. Historian draws its heatmap on each captured version of the page, so before and after can be compared side by side.
And because the tracking script records orders, Historian can colour the page by revenue per click instead of clicks alone, and show which products were bought after a click on each element.
Investigation vs. agents
With replay tools, you usually start from a hunch and go looking in the recordings. Historian's agents run on a schedule and come to you with what they found: a change that hurt conversion, a banner that stopped earning, a template that underperforms everywhere.
When each tool makes sense
Choose Hotjar / FullStory when:
- You want to watch individual sessions to find specific friction
- Surveys and on-site feedback are part of your research
- Your main questions are about usability rather than revenue
Choose Historian when:
- You want to know which change on the site moved revenue
- You want heatmaps by revenue per click, on the version of the page that was live
- You want to go back and see any page as it looked on any day since you started
- You want agents to bring you the findings instead of searching for them
Used together
A recording shows a visitor hesitating at the add-to-cart button. Historian shows that the button's design changed two weeks ago, what it looked like before, and what a click on it earned then and now.
Other comparisons
All comparisons →Historian vs. Contentsquare
Both are built for e-commerce teams. Contentsquare follows the visitor's experience; Historian follows the page, its changes and its revenue.
Historian vs. Google Analytics 4
GA tells you the numbers changed. Historian tells you what changed.
Historian vs. Amplitude
Amplitude analyses how users move through a product. Historian follows what happens to a webshop's pages and revenue.
Historian vs. Mixpanel
Mixpanel tracks what your users do. Historian also keeps what your pages looked like, and what each change was worth.
Historian vs. Microsoft Clarity
Clarity shows you how visitors behave, for free. Historian shows you what changed on the page and what it was worth.
Historian vs. Triple Whale
Triple Whale measures your channels and attribution. Historian adds what happened on the site around them.
Historian vs. Polar Analytics
Polar collects your metrics in one place. Historian records the pages, campaigns and competitor moves behind them.
Stop guessing why revenue dropped.
Book a demo and we'll show you what Historian finds on your own store.