Session Replay and Heatmap Settings

This page hasn't yet been translated into your language. We're working on it, so check back soon.

Use Session Replay settings to manage replay capture across your organization's projects. From these settings, you can control sample rates, enable or disable capture, and monitor quota usage.

The organizational settings also let admins and managers view or modify Session Replay settings for the projects they have access to.

The main settings page displays your organization's total session replay capture plan allowance and current use. The page also lists projects where you can toggle session capture and heatmap capture, and view the sample rate, instrumentation status, masking setting, and masking overrides.

On each project's settings page, find project-level controls for:

Sampling
Dynamic Sampling
Masking Level
Masking Overrides
Console Tracking

Sampling

View and set the sampling rate for any condition you define. The Sampling section shows a monthly estimate of sessions that match the conditions you define, and estimates how many sessions Amplitude captures. By default, Session Replay uses the Any Session condition. For more information about conditions, refer to Targeted Replay Capture.

Dynamic sampling

If you're unsure how to balance your sample rate against your monthly quota, dynamic sampling may help. Dynamic sampling adjusts the sample rate each day so you use your full quota by month end. Dynamic sampling helps you stay within your quotas, but Amplitude can't guarantee an exact 100% match or prevent overage. Choose which projects use dynamic sampling. Session Replay quota is org-wide, but the sampling rate is per project. If you enable dynamic sampling on multiple projects, those projects share the same sample rate.

How dynamic sampling sets the rate

Each day, Amplitude estimates your org's projected replay count by month end using analytics session counts across all projects with session capture enabled. For projects with a manual sample rate, Amplitude multiplies that rate by the project's session count to estimate each project's quota consumption. It then allocates the remaining quota to dynamic-sampling projects and sets their rates accordingly.

Because the estimate relies on analytics session counts rather than actual replay captures, discrepancies between the two can affect the result. For example, a project with a large analytics session count and a 100% manual sample rate may appear to consume most or all of the monthly quota, even if it isn't actively capturing replays. In this case, dynamic-sampling projects may receive a 0% rate early in the month.

To improve the accuracy of dynamic sampling:

Configure the sample rate in Session Replay settings for every project with session capture enabled. Dynamic sampling doesn't account for rates set only in the SDK, and projects with no rate configured in settings disable dynamic sampling for the entire org.
For projects that aren't capturing replays, set the sample rate to 0% or disable session capture so their session counts don't inflate the org-wide estimate.
Dynamic sampling works best when all projects in your org use it. You can mix dynamic and manual rates, but the estimate is less accurate when analytics session counts don't match actual replay captures.

Session Replay doesn't support dynamic sampling if any project in the org uses targeted session replay capture.

Masking level

Set the masking level for all captured sessions.

Masking overrides

Define overrides for the masking level you set. For more information, refer to Manage privacy settings for Session Replay.

Console tracking

Enable or disable console tracking, and set the types of console information you want to capture. Select one or more from Info, Log, Warn, and Error.

The Session Replay viewer also includes a Network tab in the DevTools section. Use the Network tab alongside console logs to inspect network requests captured during a replay. For details, go to Session Replay viewer.

Multi-tab behavior

Session Replay captures activity on the currently focused tab. When the user switches between tabs, the replay follows their focus and automatically switches to show the tab they're actively viewing.

When the user switches tabs, the replay cuts directly to the new tab with a fresh snapshot of the new tab's current state. Session Replay doesn't actively capture background tabs while out of focus. The event timeline captures and displays events from all tabs, regardless of which tab had focus at the time.

While viewing a Session Replay, you can't manually switch to view background tabs. The replay strictly follows the user's actual focus. If the user switches away from the browser entirely, the replay shows an inactive period while displaying the last focused tab.

Was this helpful?