Scope
This guide covers daily operation for Heatmaps, Recordings & Form Friction. Availability depends on your tenant package, role and configured providers.
Purpose
Understand clicks, scroll depth and conversion friction.
Explore heatmaps, sessions and form-field friction.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Explore heatmaps, sessions and form-field friction.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Generate supported friction findings from captured behaviour.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Compare interaction, scroll and form completion patterns.
Verify the result
Compare interaction, scroll and form completion patterns. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Use privacy controls and avoid capturing sensitive input. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.