Advanced Tracking
Optional collection is configured per project. Behavioral features require granted consent; switching a feature on does not bypass Consent. Known bots are excluded from these tracking modules.
Scroll, cursor and URL measurements
| Setting | Events | What to use it for |
|---|---|---|
| Scroll tracking | PageScrolled | Depth percentage, maximum reach and page/viewport dimensions |
| Cursor tracking | CursorMoved | Sampled pointer positions and movement patterns |
| URL visit logging | UrlVisited | Visits to a URL within the session |
| Visit time tracking | UrlVisitTime, UrlExited | Entry/exit and time on a URL |
Cursor data is sampled, not a record of every native mouse event. URL timing reacts to navigation and page visibility; treat it as measured activity rather than proof that someone read the content.
Session replay
To start, enable replay, accept tracking consent on a test visit, navigate through the relevant flow and then open the available recording in Session Replay. Test a masked field before using the feature on sensitive pages. If a recording is missing, check collection settings, consent, page installation, plan access and retention.
Enable Session Replay in Project Settings before collecting recordings. Replay reconstructs captured page changes, pointer movement, clicks and scrolling; it is not a video of the visitor's desktop.
Input values are masked by default. Add fm-mask to an element whose visible text should also be masked:
<div class="fm-mask">Private account details</div>
Other visible text can be recorded. Review your pages before enabling capture; do not assume all personal content is automatically hidden. Cross-origin embedded content and assets that are no longer available may not reproduce exactly.
Use the Session Replay list to open available recordings and investigate the timeline. Feedback can link to a relevant clip when a matching recording exists. Recordings are subject to plan access, usage allowances and retention; enabling replay cannot recover earlier visits.
Heatmaps
Open Heatmap, choose a page with an available recording, then select the device and interaction mode. If the view is empty, check whether both the snapshot and the selected interaction data exist for that page/device. A missing background and no recorded interactions are different gaps.
The Heatmap view offers click, mouse movement and scroll modes with page-path and device selection. It uses a recorded page snapshot for visual context. Collect eligible replay data for the page/device before expecting a background snapshot to be available, and enable the relevant behavioral tracking switches.
Keep device layouts separate when comparing positions. A hot area indicates concentrated interactions, not necessarily a successful action; inspect recordings or feedback to understand the outcome.
Video analytics
Enable video tracking, accept consent during a test visit and play a supported video through a progress milestone. Open Video Analytics and the individual video to review results. If it is missing, check player support and collection settings; video visibility alone does not count as a play. Pintelly measures interactions; it does not host or modify the player.
Enable Video Tracking to collect supported native video, YouTube, Vimeo and supported player integrations. Measurements include play, pause, progress milestones (25/50/75%), completion and seeking. Player support determines which additional events are available.
The dashboard provides an overview and individual video detail. Use play and completion data together: a started video is not a completed view. Data begins after the setting is enabled and consent is granted.
Console logs
Enable Console Log Tracking and select from log, error, warn, info, debug. Review collected entries in Console Logs. Only select the levels you need; application messages can contain personal or confidential values.
SEO collection
SEO Analysis checks title/description, heading structure, images, links, structured data and content signals. Before consent, only content-free checks are sent; text/NLP analysis requires consent. See SEO Analysis for page-check behavior, bot access, issues and verification.