What Is Session Replay?
Voidr Session Replay captures and reconstructs real user sessions in your web application. You can see exactly what users experienced:- Clicks and navigation
- Errors and console logs
- Network requests and performance
- UI behavior over time
What Is It Used For?
- Generate automated tests from real usage
- Analyze how features are actually used
Installation (1 Minute)
Step 1: Add the Script to the <head> of Your HTML
Step 2: Get Your API Key
- Go to: https://app.voidr.com/settings/api-keys
- Click Generate New Key
- Copy and paste it into your code
Step 3: Verify It’s Working
Open your application and visit: https://app.voidr.com/sessions You should see your session appearing in real time.No npm, webpack, or build step required.
Just copy, paste, and it works.
Just copy, paste, and it works.
What Is Captured?
User Interactions
- Clicks (buttons, links, elements)
- Form inputs
- Scroll and navigation
- Mouse events (hover, movement)
Errors and Console
- JavaScript errors (
window.onerror) - Unhandled promise rejections
- Console logs (optional)
- Full stack traces
Network Requests
- Fetch and XHR calls
- Status codes and response times
- Performance timing (DNS, SSL, TTFB)
- Third-party requests
Privacy by Design
- Sensitive data is anonymized server-side
- Passwords, credit cards, IDs are always masked
- Capture behavior is fully configurable
Configuration Parameters
Configuration Structure
Session Replay configuration is organized by areas of responsibility:Quick Reference Table
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
apiKey | string | ✅ Yes | — | Authentication key |
user.id | string | ✅ Yes | — | Unique user identifier |
user.email | string | No | null | User email |
user.name | string | No | null | User name |
applicationId | string | No | null | Application identifier |
environment | string | No | null | production, staging, etc |
samplingRate | number | No | 0.1 | Sampling rate (0 to 1) |
sessionTimeout | number | No | 30 | Inactivity timeout (minutes) |
networkCapture | boolean | No | true | Capture network requests |
captureConsole | boolean | No | true | Capture console logs |
dataMasking.inputs | boolean | No | false | Mask input values |
dataMasking.text | boolean | No | false | Mask all page text |
dataMasking.blockSelectors | array | No | see below | CSS selectors to block |
meta | object | No | null | Custom metadata |
Parameter Details
1. apiKey (required)
What it does: Authenticates your application with the Voidr platform.
2. user.id (required)
What it does: Identifies the user using your application.
Important: This value must be stable across sessions (always the same for the same user).
3. user.email and user.name (optional)
What it does: Adds information to facilitate search and session identification.
j***@c******.com).
4. applicationId (recommended)
What it does: Separates sessions when you have multiple applications.
environment (Recommended)
Identifies the environment where the session occurred(e.g.
production, staging).
samplingRate
Controls how many sessions are recorded.
1.0→ 100% of sessions0.1→ 10% of sessions (default)
sessionTimeout
Defines how long inactivity ends a session.
networkCapture
Captures Fetch and XHR requests.
captureConsole
Captures console.log, warn, error, and info.
dataMasking.inputs
Masks all input values before sending data.
dataMasking.text
Masks all visible text on the page.
dataMasking.blockSelectors
Completely blocks elements from capture.
meta (Custom Metadata)
Adds searchable metadata to sessions.
Privacy Protection
Server-Side (Automatic)
Voidr always masks:- Emails
- Phone numbers
- IDs (CPF, SSN, etc)
- Credit cards and CVV
- Passwords
Client-Side (Configurable)
Full Example
Where to View Sessions
Access the session player at: https://app.voidr.com/user-monitoringSupport
Need help?Contact your Forward Deployment Engineer (FDE).