Behavioural Analytics
Every page and mapped group, side by side.
A large site is thousands of URLs that mean a few dozen things. Map them into groups once, then compare templates rather than addresses — so a regression in a checkout step is visible without knowing which of forty URLs it lives at.
Page Comparator
Compare web pages and native screens across navigation, engagement, outcomes, and performance.
Right-click any row to open it in Journeys, Heatmaps or Session Replay.
Templates, not addresses
Group every product URL into one row and the number finally means something. One page per SKU means nothing at all.
One table, not forty tabs
Every page and group in a single view, so a comparison is read rather than assembled.
Sorted by the argument
Order by the metric the discussion is actually about, and the outlier is at the top before anyone opens a spreadsheet.
What Page Comparison does
Map once
Define the groups that describe your site, and every new URL that matches falls into the right row automatically.
- Group URLs into named page groups
- New pages matching a pattern join their group without maintenance
- Keep individual pages visible alongside groups when detail matters
Compare properly
The metrics that separate a page that works from one that does not, on every row at once.
- Sessions, engagement and exit behaviour per page or group
- Sort and rank by any column
- Spot the template that underperforms its siblings
Then open one
A row is a set of real sessions, not a summary statistic.
- Move from a page row into replays of sessions that visited it
- Cross into heatmaps for the page that looks wrong
- Check whether the gap is one device class or all of them
Better with the rest of it
Every module reads the same identity, events and sessions, so an investigation that starts here does not have to be rebuilt to continue somewhere else.
Frequently asked questions
What is a mapped group?
A named set of URLs that behave as one page — every product detail page, every article, every step of a checkout. You define the rule once and matching pages join automatically.
Does this work for mobile apps?
The equivalent unit in an app is the screen, which is captured automatically by the SDK. Screens can be compared the same way pages are.
Why not just use a dashboard?
A dashboard answers a question you already knew to ask. This view is for the case where you do not yet know which of your pages is the problem.