Located in the Menu bar, Session Replay allows you to watch replays of your user sessions to understand and validate analysis results. With Session Replay, you immediately identify what the issue is, so you can accelerate areas for improvement without any delay.
Session Replay for Flutter and React Native
- Flutter plugin (3.0.0)
- React Native bridge (3.4.0)
Session Replay list overview
Here is the list you see when you first access the module. Thanks to contextual parameters and filtering options, you can decide which sessions are worth watching and filter them by behaviors, number of screens viewed, duration of sessions, etc. so you save time and jump directly to the session you're interested in.
1. Analysis context: Select the device, date range, and segment. The list of sessions is updated according to the chosen analysis context. It's recommended to first select your analysis context and then use the filters on the left menu to narrow your results.
2. Filters:
- Select a screen or screen group (from a mapping)
-
Filters:
- Latest replays: Filter to sessions collected yesterday and today.
- Duration of the session: Set an average duration for your sessions and display only those that match the selected duration.
- Number of screens viewed: Determine how many screens should be seen by your users on average
- The user ID (CS): It relies on CS assigned user ID. The user ID corresponds to the one created by Contentsquare and does not involve personal data (data that directly identifies an individual).
3. Show by:
- Session, screenview, user
- Sorted by: your sessions by newest to oldest, oldest to newest, session duration, number of screens viewed.
4. Each session bar is composed of:
- Play button to watch the session. Once you have already watched a replay, the button will read "Replay"
- Session context (Session date and time, screen size, country, visitor ID and browser used).
- Your timezone vs. the timezone of the user. If you hover over the date and time next to a replay, you'll see the user's date and time being displayed. This is very useful to understand if the user was connected at a time the server was overloaded.