Replay real user sessions to see exactly what your users are experiencing on your app, including the screens they visit, how they navigate, where they tap and swipe. Use Session Replay to deepen your analysis, alongside our other analytics capabilities to validate a hypothesis, discover the root cause, or uncover unexpected insights.
This article gives an overview of Session Replay for mobile app's key features and implementation steps to help you get started. Note that some of the implementation steps outlined below refer to our technical documentation and may need to be completed by your technical team.
Key features
- Session Replay list view: access your list of replays, sort and filter specific sessions to watch
- Replay summaries (AI): understand where to focus your attention with key insights and issues summarized for each replay, or a group of replays.
- Session Replay player: watch your user’s experience alongside a timeline of their activity, see the event stream of screens visited and events occurred, customize your player settings, share replays, and more.
Session Replay implementation
Many of these steps are completed during your Contentsquare app project’s implementation, but it’s important to ensure these Session Replay specific steps are in place.
Prerequisites
In order to start using Session Replay on your app the following steps must be completed, if not done so already:
- Upgrading to the Software Development Kit (SDK)
- Handling user consent: ensure this is handled, especially if implementing Session Replay for the first time.
- Implementing screen tracking: Ensure screen tracking is implemented, since session replay collection starts at the first screenview event.
Visit our technical documentation, by framework, for detailed information on all of these steps:
iOS | Android | Flutter | React Native | Capacitor
Configurations
The following configurations are important to ensure Session Replay is set up according to your unique app and needs.
To be configured with the support of Contentsquare:
- Session Replay data collection: this includes your sampling rate, retention period and what/how data is collected. Learn more about data collection here.
To be configured by you or your technical team:
-
Session Replay masking: by default, the Contentsquare SDK is configured to mask all content displayed on the user interface (UI) to prevent unnecessary data collection.
Having all UI content masked by default can make it difficult to analyze - and in this case, test - your app’s interface in a replay. For testing purposes we recommend using either of the following unmasking mechanisms:- Either unmasking all the content using the Default masking API (technical documentation): iOS | Android | Flutter | React Native | Capacitor
- Or unmasking non-sensitive content with the Text and Image unmasking configuration in the Contentsquare Console
Important
Please make sure your configuration excludes any personal data to protect your user’s privacy.
- Testing your replay configurations: Visit our technical documentation on testing and debugging: iOS | Android | Flutter | React Native | Capacitor
Additional configurations (optional)
To be configured by you or your technical team:
- Tracking Webviews: if your app includes Webviews follow the implementation steps below:
- Adding custom iOS fonts: ensure UIKit elements are rendered exactly as they appear in your app. Visit our guide on managing iOS fonts in the player.
A paid add-on feature, to be activated by Contentsquare:
- Event-triggered replay add-on (ETR): allows you to selectively collect specific screens or sessions for Session Replay, based on predefined custom events. Learn more about ETR data collection.