Review recording controls and the retention period available to your workspace. The recording dialog displays the effective retention policy; contact Userorbit to arrange an Enterprise custom window.

Plan requirement: Session Replay requires Scale or Enterprise. It is also available during an active trial. A workspace-specific Session Replay override can make it available on another plan.

Open the Session Replay settings

  1. Confirm that you are working in the correct workspace and project.
  2. Open Analytics, then Replays.
  3. Select Recording settings. An owner or administrator manages these settings. If the control is missing, ask them to check your access and the controls available in your deployed version.

Session Replay settings showing recording, retention, audience, and volume controls

The Session Replay configuration covers privacy modes, sampling, quota, targeting, recording access, and retention. Review these settings for the selected workspace before turning on recording for a paid plan.

Turn recording on

  • Active trials record automatically and do not require a separate opt-in.
  • Scale, Enterprise, and legacy Pro workspaces must turn on Session Replay before new sessions are recorded.

Plan access and recording status are separate for paid workspaces. A workspace can have access to Session Replay without recording being turned on.

Choose who can be recorded

Under Audience, choose one option:

  • All users allows identified and anonymous users to pass sampling.
  • Saved segment limits eligibility to identified users in the selected segment.

Audience eligibility is evaluated before sampling and the daily quota.

Control recording volume

  • Sampling is the percentage of eligible analytics sessions that load the recorder. Set it from 0% to 100%.
  • Daily quota is the maximum number of logical sessions accepted for the project in one UTC day. The quota is the final ceiling after sampling.

Use a lower sampling percentage when you need representative coverage without recording every eligible session. Use the daily quota to cap the maximum daily volume.

Examples: audience, sampling and daily quota

The audience decides who is eligible. Sampling chooses a proportion of eligible sessions before the recorder loads. The daily quota limits the logical sessions accepted for each project on each UTC day.

Goal Example configuration Expected result
Review a smaller sample of general usage All users, Sampling 10%, Daily quota 500 If 2,000 sessions are eligible, about 200 pass sampling. The actual number varies, and the quota still applies.
Limit collection to an approved group Saved segment, select the approved segment, Sampling 100%, Daily quota 100 Identified users in the segment can pass sampling. No more than 100 new logical sessions are accepted per project that UTC day. Anonymous users are not eligible for this audience.
Put a ceiling on a busy project All users, Sampling 25%, Daily quota 500 With 10,000 eligible sessions, about 2,500 would pass sampling, but the daily acceptance limit is 500. This does not guarantee a sample spread evenly across the day.

The default sampling rate is 100% and the default daily quota is 500. A quota is a ceiling, not a target or a promise of that many playable recordings. Browser support, network delivery and other recording conditions still apply.

When browser storage is available, the SDK remembers its random sampling decision for the analytics session. Reloading the same session does not necessarily select a different result, and changing the percentage does not replace an already stored decision. Validate a change with a fresh test session. A 0% rate excludes new sampling decisions; do not use it as a promise to stop every recording already in progress.

Choose values that fit the collection you have approved. Sampling and audience controls do not mask sensitive content; configure privacy controls separately.

Choose a privacy mode

Privacy settings apply to new recordings and do not rewrite existing replays.

  • Selective masking records interface text, masks form values, and redacts the selected PII types using pattern matching. This is the default mode.
  • Mask everything masks form values and page text. An explicit .uo-unmask class can exempt page text; form values stay masked in this mode.
  • Record everything records visible text and form values. Passwords and elements matched by your mask selectors remain protected. A show-password control can change an input type and needs a stable mask selector.

With Selective masking, choose whether to redact email addresses, phone numbers, payment card numbers, and IP addresses from page text. Form values remain fully masked in this mode.

Mask or block specific elements

Use comma-separated CSS selectors for either control:

  • Always mask these elements replaces matching text and form values with asterisks.
  • Do not record these elements replaces matching regions with an empty box.

Test selectors in a non-production environment before relying on them for sensitive data. Review unmasking, password-reveal controls and data outside replay in Protect personal data with pseudonymous IDs and replay masking.

Select Save settings after reviewing recording access, audience, volume, privacy, and retention.

Understand retention

Workspace access Retention
Active trial 30 days
Scale or legacy Pro 90 days
Enterprise 90 days by default, or a custom period from 1 to 3,650 days

Custom retention is available only on Enterprise.

What happens when retention changes

A replay receives its expiry when recording begins. Changing the retention setting affects new recordings; it does not recalculate the expiry of replays that already exist.

Troubleshooting

You cannot open Session Replay settings

Check the selected workspace under Settings → Billing. Session Replay requires an active trial, Scale, Enterprise, legacy Pro access, or a workspace-specific override.

New replays are not being recorded on a paid plan

Open the privacy settings and confirm that Session Replay is turned on. Paid plan access alone does not enable recording.

Existing replays still use the previous retention period

This is expected. Existing replays keep the expiry assigned when recording began; the updated retention period applies to new recordings.

Was this helpful?