Skip to main content

​
Overview

Session replay lets you watch a visual recording of what your users see and do on your site. It captures the page as they experience it — clicks, scrolls, navigation, and errors — so you can debug issues and understand behavior without asking users to describe what happened.

​
How it works

  1. Buffering — the SDK silently captures page activity in the background with minimal overhead. Nothing is uploaded during this phase.
  2. Triggered recording — when something notable happens (e.g., a JavaScript error or the user opens the chat widget), the buffer is flushed and full recording begins.
  3. Playback — recorded sessions are available in the Hacktionbase dashboard, where you can watch them with a timeline, event markers, and console logs.
This “buffer first, record on trigger” approach keeps bandwidth usage low while ensuring you capture the moments that matter.

​
What is captured

  • Page structure and visual changes
  • Mouse movements and clicks
  • Scroll positions
  • Form inputs (masked by default — see Privacy below)
  • Console logs (log, info, warn, error)

​
What is NOT captured

  • Cookies, localStorage, or network request/response bodies
  • Cross-origin iframe content
  • Canvas content
  • Images are referenced by URL, not inlined

​
Privacy & GDPR

Session replay is designed with privacy as a priority:
  • Inputs are masked by default — text fields show *** in playback, so sensitive data like passwords or credit card numbers are never recorded
  • Custom masking — add data-hb-mask to any HTML element to mask its text content in recordings
  • Block elements — add data-hb-block to exclude an element from recording entirely
  • Full opt-out — call Hacktionbase.disableReplay() to permanently disable recording for a user (ideal for GDPR compliance)
<!-- Mask sensitive content -->
<div data-hb-mask>This text will appear as *** in replays</div>

<!-- Exclude from recording entirely -->
<div data-hb-block>This element won't appear in replays at all</div>

// Permanently disable replay for this user
Hacktionbase.disableReplay();
See SDK Session Replay for full implementation details.

​
Quotas

Session replay quotas depend on your plan. When the quota is reached, recording stops automatically — no data is lost, and the SDK resumes when quota is available again.

​
Viewing replays

Replays are accessible from:
  • User profile → Sessions tab — see all recorded sessions for a specific user
  • Sessions list — browse all recorded sessions across your workspace
  • Session detail — full player with timeline, event markers, and console panel