Session Replay is a powerful tool that can modernize your Digital Experience Monitoring (DEM) strategy. You can use it to capture and visually replay the complete digital experience of every user.
You can record your customers' interactions with your web application and replay each click and action in a movie-like experience. Session Replay also makes it easy for your QA teams to reproduce production issues, which your developers can use to bridge the gap between code and user experience.
Session Replay helps identify errors that should be fixed immediately and other problems such as malformed pages and infinite spinners. You can also use Session Replay to identify and analyze areas of struggle in your application and improve its overall usability.
Uses for Session Replay
With Session Replay, you can drill down further into the details of detected errors:
- Understand the exact user actions that led to an error.
- Understand the severity of the problem and its effect on user experience.
- Observe the customer impact by replaying and viewing a session when the problem isn't obvious.
Developers can use Session Replay to view, analyze, reproduce, and fix errors.
For error drill-down, you don't need to have all sessions recorded. You could use cost and traffic control to record only a subset of sessions. If the error to be analyzed isn't too sporadic, it can be detected even if only 20% of sessions are recorded.
The default data retention timeframe of 35 days is applied to these sessions.
The ability to play back recorded user sessions with or without playback masking settings is permission controlled. Permissions are available at the environment level as well as the management-zone level. Read more in Manage user groups and permissions.
Because Session Replay is the best way to demonstrate what the user actually did, it provides the means to resolve customer complaints. Use Session Replay to:
- See the exact journey of the customer in your application.
- Identify the exact problem faced by the user.
- Provide correct instructions.
For customer complaint resolution, it's ideal that all sessions be recorded. However, to save storage space, we recommend that a lower retention time be set.
You can use Session Replay to detect and analyze the following issues:
- The UX design isn't intuitive enough.
- The process flow is too complicated, and users leave your application midway.
- The application is slow, and the user repeatedly clicks to move to the next page.
- The application doesn't work as expected on all browsers.
- The mobile web app prompts the user to change the orientation of their mobile device, but the user doesn't understand the prompt.
The default data retention time is applied to these sessions.
Session Replay is compatible with page-based applications, single-page applications, and applications that use iFrames. However, certain restrictions apply.
Frequently asked questions
Around 100 KB of data is generated for every minute of a session and around 500 KB of storage is consumed by a fully recorded session.
No. Session volume depends on a variety of factors, including the application size, session duration, and users' interactivity with the application.
Session sizes vary from 100 KB to over 1 MB.
No. To record sessions, Session Replay monitors changes on the DOM tree of a web application. Every visual change in a web application has a corresponding change in the underlying DOM. Session Replay captures and recreates these changes. Because all of this is text-based data, small session sizes are achieved through compact representation and compression.
Because compression takes place on the client side, the bandwidth consumption is the same as the storage consumption: around 100 KB per minute or 500 KB per session.
This is advantageous for recording sessions from users on mobile devices with limited internet data or with connections that have limited bandwidth.
Session Replay was designed to have a low impact on the UI thread, which impacts user experience. Most Session Replay tasks, including an efficient compression algorithm, are executed by a worker thread that runs in the background and doesn't interfere with the user interface.
Recording masking rules are transmitted to the client. This ensures that confidential data does not leave the client browser by default. Masking settings for recording as well as playback are configurable.
You can use the RUM browser extension to enhance the Session Replay playback, specifically in the following cases:
|Resource type||Extension required|
|Images||To load images from HTTP origins|
|Style sheets||When resource capture is disabled 1|
When the resource is excluded 1
In these scenarios, the RUM browser extension serves as a fallback mechanism. If the resource isn't captured, it will be retrieved from the original source.