Use the Replay Captured event

Use [Amplitude] Replay Captured to identify sessions with a replay you can watch and measure how many distinct replays Amplitude captures. Amplitude sends the event automatically after a successful capture, so you don't need to instrument it yourself.

For example, after changing your sample rate, count distinct replay IDs to check how capture volume changes. Use the Ingestion Monitor to diagnose request failures; the capture event identifies successful captures rather than failed attempts.

Event identity and properties

The event may create anonymous users if Amplitude can't associate the device ID with an existing user. The event doesn't count toward event volume or MTU (Monthly Tracked Users).

Analyze captured replays

The capture event connects analysis to a replay through [Amplitude] Session Replay ID. Use it for these tasks:

• Investigate a user's experience: find the event in the user's event stream, then open the associated replay. Follow Find replays with User Look-Up for the workflow.
• Track capture volume: select [Amplitude] Replay Captured in an Event Segmentation chart, group by [Amplitude] Session Replay ID, and use PROPCOUNT(A) to count distinct replay IDs. Follow Measure replay capture for the steps.
• Focus analysis on captured sessions: use the event to identify sessions with replays when investigating behavior in charts. Follow Watch replays from a chart to open the replay behind a data point.

Count distinct replay IDs when you need a replay count. A raw event count can include multiple capture events in a user's timeline.

Multiple capture events in a timeline

Multiple [Amplitude] Replay Captured events can appear when multiple browser tabs have different active sessions. For how Amplitude associates analytics events with a replay, refer to Session matching. Timelines show events captured during the replay period, so events from different sessions may overlap.