Targeted Replay Capture

Targeted Replay Capture (TRC) is an advanced feature in Amplitude Session Replay that lets you selectively capture session replays based on specific criteria, rather than capturing all sessions or relying solely on random sampling. This helps you focus your replay quota on the most important user behaviors, workflows, or segments.

Targeted Replay Capture lets you customize capture criteria using specific conditions like multiple events, event properties, or user properties. You can combine these criteria within a single filter or across filters using OR logic. The Session Replay SDK fetches targeting configurations from a remote config service and evaluates them at runtime to decide whether to capture a session.

Key capabilities

TRC enables you to define the criteria that Amplitude uses to decide to capture a session, and more efficiently manage your Session Replay quota.

Custom capture criteria

Define rules to capture replays only when certain conditions are met:

  • Specific events: For example, Checkout Started.
  • Event properties: For example, plan = Pro.
  • User properties: For example, country = US.
  • Combinations: Combine the above using OR logic.

Configuration and quota management

Manage TRC through the Session Replay settings page, where you can add, edit, and manage your targeting conditions. The UI provides an estimate of how much quota each condition uses, based on historical traffic. You can set different sample rates for different conditions, giving you granular control over which sessions you capture and how much of your quota you use.

Use cases

  • Capture replays only for users who encounter errors or drop off at key points.
  • Focus on high-value user segments or critical product flows.
  • Reduce noise and cost by avoiding unnecessary replay capture.

Prerequisites

Before you configure Targeted Replay Capture, ensure you meet these requirements:

Configure Targeted Replay Capture

To configure Targeted Replay Capture:

  1. Navigate to Settings > Organizational Settings > Session Replay Settings. For more information, review Session Replay settings page.
  2. Select the project. Each project has its own settings.
  3. Configure your targeting conditions using the UI.

You can add multiple conditions and combine them using OR logic. Each condition can include:

  • Event types.
  • Event properties.
  • User properties.

Note

You must capture and send events, event properties, and user properties to Amplitude during the session for targeting conditions to work properly.

SDK support

Targeted Replay Capture requires the Amplitude Browser Analytics SDK with the Session Replay Browser SDK Plugin. To use TRC, ensure you have both the Amplitude Browser Analytics SDK and the Session Replay Plugin integrated into your setup.

Standalone SDK not supported

Targeted Replay Capture doesn't support the standalone SDK. Use the Session Replay Browser SDK Plugin instead.

Evaluation timing

The SDK fetches the targeting configuration at session start and uses it for the entire session. If an event matches later in the session, the SDK evaluates it against that original configuration. Updates to targeting rules only take effect for new sessions.

Capture timing

Session replay capture begins only after the target event occurs. TRC has no "lookback" period—replays don't capture events that happened before the targeting condition triggers. The replay starts from the point when the target event triggers, not from the beginning of the session.

Was this page helpful?

December 24th, 2024

Need help? Contact Support

Visit Amplitude.com

Have a look at the Amplitude Blog

Learn more at Amplitude Academy

© 2025 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.