Additional information

Session replay and your app's performance

Before enabling session replay, consider the following impact on your app and users:

• App performance: Session replay captures and transmits viewport data, which may impact app performance on older devices.
• Data consumption: Replay data transmission will consume user data, especially when images are captured.
• Storage requirements: Captured data requires adequate storage capacity on user devices between transmission cycles.
• Network optimization: All data is compressed client-side before transmission to minimize network usage.
• Sampling strategy: Consider your sampling rates carefully to balance data collection needs with performance impact.

Data consumption

Session replay follows the same consumption pricing as your other mobile bytes. The amount of bytes produced depends on the count, length, and user activity levels of sessions, as well as the complexity of your app.

The most accurate way to project your cost per replay is to enable the feature for a short test period and measure your actual consumption. A simple formula to project approximate costs is:

sessions x sampling_rate x gb_per_replay x cost_per_gb

For example:

1 million (sessions) × 5% (sampling rate) × 0.0053 (GB per replay) × $0.40 (cost per GB) = $106 for 50,000 replays

To control your consumption, adjust your sampling rates.

User privacy and security concerns

We prioritize data privacy and built session replay with strong default settings to minimize the potential exposure of sensitive customer information. You can further customize privacy settings to meet your specific needs.

Session replay doesn't capture videos and by default, images are blocked and replaced with placeholders of the same size. Instead, it records and reconstructs user interactions. This significantly reduces the amount of data stored.

Compliance with data privacy laws

New Relic acts as a data processor under GDPR and a service provider under CCPA. This means we process data according to your instructions. Ultimately, compliance with these laws depends on how you implement session replay within your application.

By default, all text and user inputs, including personal data, are masked within the recordings. You can selectively unmask specific elements if needed, but the default ensures that no personally identifiable information is readily visible.

Supported UI frameworks

Session replay is currently supported for select UI frameworks for iOS, Android, and React Native apps. We are actively working on supporting more UI and hybrid frameworks.

Currently supported:

• iOS UIKit
• iOS SwiftUI
• Android XML layouts
• Android Jetpack Compose
• React Native Views

Planned support:

• WebViews
• Flutter
• Cordova
• Capacitor
• MAUI