Your visitors, not a simulation
Heatmaps, scroll depth and the attention split are built from the people who actually came, so a page that reads well in an audit but loses everyone at 40% depth stops being invisible.
Visitor Behavior
See what visitors actually did on the page, from your own traffic rather than a lab simulation.
Visitor Behavior reads events captured by the installed tag: where participating visitors clicked, how far they scrolled, where their attention stopped, and the Core Web Vitals their real devices measured. It is the only source in Novaverb that can report field experience for instrumented pages that receive captured traffic.
Heatmaps, scroll depth, attention and field Core Web Vitals on Free, watching a visit back on Solo and above
Why it is useful
A clear decision, with the supporting evidence close by
Field Core Web Vitals where captured
LCP, INP and CLS from participating visitors' devices on instrumented pages with captured traffic; pages without observations stay unavailable.
Watch the visit that went wrong
Session replay reconstructs the page from the DOM rather than storing video, so a ten-minute visit is a small recording you can scrub through and see exactly where the visitor gave up.
Data and evidence
See the evidence behind each result
Each result keeps its project source, scope and observation window close at hand.
Available evidence
The evidence available in the active project and the details you provide.
Decision support
Visitor Behavior reads events captured by the installed tag: where participating visitors clicked, how far they scrolled, where their attention stopped, and the Core Web Vitals their real devices measured. It is the only source in Novaverb that can report field experience for instrumented pages that receive captured traffic.
How to read this result
This result names the project evidence, scope and observation window used to produce it.
Core capabilities
What you can do with Visitor Behavior
Each capability stays tied to the product contract and the evidence available in the active project.
Core Web VitalsIncluded in your workspace
How the work moves
From available evidence to a reviewable next action
The workflow is designed to keep the source and the next decision connected, including the point where a fresh observation is still required.
- 01
Capture
Collect the crawl, search and connected-source evidence the decision actually needs.
- 02
Understand
Keep the source, scope and observation time attached while you diagnose the gap.
- 03
Act
Move from a supported finding to the page, brief, task or report that carries the work forward.
- 04
Verify
Use a fresh observation or the connected source to check what changed instead of assuming success.
Resources
Read more about Visitor Behavior
Written by the team that built it, and free to read without an account.
Guides
Step-by-step walkthroughs, five minutes each.
Definitions
What the terms on this page actually mean.
Connected products
Keep the work moving without losing the source
Trust & Experience
Put Visitor Behavior to work on your own evidence.
Start with a real project, keep unavailable data visible and follow the connected workflow when the result is ready for action.