Capture
A stream, not a video
The tracker records DOM mutations, pointer movement, scroll and input events. The player rebuilds the page from that stream. No screen capture is taken.
DOM stream / no video file
WATCH THE SESSION.
Replay reconstructs the page as the visitor saw it, with every recording tied to its timeline.
The record, the mask, the trigger.
Three settings decide what a recording contains and how long it stays. All of them are applied before the stream is written to the project store.
Mask
Masked before transmission
Input fields are masked by default and selectors can be added to the mask list. Masked values are excluded from the stored stream, not hidden later in the player.
Default mask / selector list
Keep
Triggers decide the budget
Flag or record a session on a rage click, a JavaScript error, a failed request or a funnel exit. Sampling spends its budget on the sessions worth keeping.
Four trigger types / per project
CaptureDOM, pointer, scroll, input
MaskSelector list
StreamOrdered events with a session id
RebuildPlayer renders the page
What the recording holds.
Each recording is a stream with a session id, a page sequence and an event time for every mutation. The player replays the stream in order.
Sampling is a percentage per project. Retention is a window you set inside the plan limit. When the window closes, the stream is deleted and the session metadata stays in the index.
The timeline shows the page, then the moment it broke.
Get Started →