Skip to main content

Configuration and Limits

Configure Recording Sampling Rate​

In the Statsig Console, you can configure your session recording sampling rate. This determines the percentage of all user sessions that are recorded. Since there is (currently) a limit of 10,000 session recordings every month, this can help ensure you space out running against that limit. The default sampling rate is 100% which is great for smaller companies and projects.

Click on the settings icon in the top right of the Statsig console to navigate to Project and Organization Settings. Under Project Settings, click on Session Replay and set the sampling rate. You must be a project admin to modify the sampling rate.

image

Advanced: Forcing a Recording on Demand​

You may have a use case where you need to make sure a session is recorded (based on a trigger, or a particular user that has interesting characteristics or behavior). To do this, we offer the forceStartRecording API which will begin recording as soon as you call it.

If you are just getting set up - just follow the installation guide on the previous page. But if there is a specific trigger in your app you want to force recording, you can do the following:

if (someCondition) {
  new SessionReplay(client).forceStartRecording();
}

Configure Recording Privacy/PII Options​

If your users may be entering or viewing sensitive information, you can prevent this from being recorded and displayed using CSS classes offered by the rrweb recorder (the open source recording tool we use).

  • input[type="password"] will be masked by default.
  • An element with the class name .rr-block will not be recorded. Instead, it will replay as a placeholder with the same dimensions.
  • An element with the class name .rr-ignore will not record its input events.
  • All text of elements with the class name .rr-mask and their children will be masked.

We plan to provide 1st class integration of privacy controls with the Statsig SDK as we roll out of beta.

Limits​

4 Hours Per Session or 30 Min Inactive Time​

Sessions will end after four hours total or if the user returns from inactive time greater than 30 minutes later.

10,000 Sessions Per Month​

Every Statsig project can store up to 10,000 sessions per month, after which time the SDK will stop further recordings from taking place by preventing clients from taking new recordings. You can check how many replays you have used in your org settings:

Replay Availability Time​

It can currently take about 1 hour from when the session is recorded to seeing it in your Statsig console. We are working to bring this time down in the next few weeks.

30 Day Retention​

While we are in beta, Sessions have a 30 day lifetime and will be deleted after 30 days.