---
title: Manage Session Replay settings
description: "Control replay and heatmap capture, sampling, masking, and console tracking across your organization's projects."
product: session-replay
lang: en
token_estimate: 1031
---
# Manage Session Replay settings

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

Use Session Replay settings to control which projects capture replays and heatmap data, manage your capture quota, and choose privacy controls. Use these settings to adjust an existing implementation. To start capturing replays, first [install the Session Replay browser plugin](https://amplitude.com/docs/sdks/session-replay/session-replay-plugin#quickstart).

## Open Session Replay settings

Admins and managers can view or modify settings for projects they have access to.

1. Go to _Settings > Organizational Settings > Session Replay Settings_.
2. Review your organization's replay capture allowance and current usage.
3. Find the project you want to configure. The project list shows capture toggles, sample rate, instrumentation status, masking level, and masking overrides.
4. Select the project to open its sampling, masking, and console tracking controls.

## Control replay and heatmap capture

Use the project list to enable or disable session capture and heatmap capture for each project.

[Heatmaps](https://amplitude.com/docs/heatmaps) aggregate web Session Replay interactions into maps of clicks, element interactions, and scroll depth. Enabling heatmap capture controls data collection; to check SDK requirements and build a map, follow [Create a heatmap](https://amplitude.com/docs/heatmaps/create-a-heatmap). Replay sampling limits the interactions available to heatmaps, so consider heatmap coverage when choosing a sample rate.

After you change capture settings, [verify capture](https://amplitude.com/docs/session-replay/verify-capture). If the SDK sends replay requests but replays don't appear, use [Monitor replay ingestion](https://amplitude.com/docs/session-replay/ingestion-monitor) to check request statuses.

## Choose sampling and targeting

In the project's _Sampling_ control, choose how to distribute your replay capture quota:

- Use [manual sampling](https://amplitude.com/docs/session-replay/configure-sampling#choose-a-manual-rate-for-your-quota) to capture a fixed percentage of sessions.
- Use [dynamic sampling](https://amplitude.com/docs/session-replay/configure-sampling#dynamic-sampling) to adjust rates daily across participating projects.
- Use [targeted capture](https://amplitude.com/docs/session-replay/targeted-replay-capture) to capture sessions that match events, properties, or URLs.

For quota calculations and configuration requirements, follow [Configure Session Replay sampling](https://amplitude.com/docs/session-replay/configure-sampling). To check capture volume after changing rates, [measure captured replays](https://amplitude.com/docs/session-replay/measure-replay-capture).

## Configure masking

In the project settings, choose a masking level and define overrides for individual page elements. Follow [Manage privacy settings for Session Replay](https://amplitude.com/docs/session-replay/manage-privacy-settings-for-session-replay) for masking presets, CSS selectors, and precedence between SDK and organization settings.

Masking controls page text and form inputs. To protect sensitive content in URLs, [configure URL filter rules](https://amplitude.com/docs/session-replay/configure-ugc-filter-rules). To determine when to start capture based on consent, follow [Manage user consent](https://amplitude.com/docs/session-replay/best-practices-for-managing-user-consent).

## Configure console tracking

Capture console information when you need to investigate an error alongside the user's actions.

1. Go to _Settings > Organizational Settings > Session Replay Settings_.
2. Select the project you want to configure.
3. In _Console Tracking_, enable or disable console tracking.
4. Select the types of console information to capture: `Info`, `Log`, `Warn`, and `Error`.

To investigate the captured logs alongside network requests and replay activity, follow [Inspect replay errors](https://amplitude.com/docs/session-replay/inspect-replay-errors).