Inspect errors in a session replay

Inspect console logs and network requests alongside a session replay to identify technical failures during a user's interaction. Use the replay to locate a failure in one session, then analyze error events in charts to measure its impact across users.

Prerequisites

Error Analytics requires these SDK versions:

Enable console tracking in Session Replay settings to capture console messages, warnings, and errors.

Error Analytics covers JavaScript console logs, failed network requests and API calls, and runtime JavaScript errors. Network error capture uses the Analytics Browser SDK listed in the requirements table.

View console logs in a replay

1. Open a session replay from a chart, User Look-Up, or the Session Replay list.
2. Select the console icon to expand the console log view.
3. Select a log entry to jump to that moment in the replay.

The console panel shows logs, warnings, and errors in chronological order alongside the session timeline. Network errors display at the bottom of the replay modal.

Inspect network requests

Open the Network tab in the viewer's DevTools section. Each request shows its URL, HTTP method, status code, and response time. Select a row to open its detail panel.

To capture request and response bodies, configure requestBody and responseBody capture rules in networkTracking. Follow Track network requests in the Analytics Browser SDK reference.

Use the Network and Console tabs together to correlate user actions with API calls and JavaScript logs. For example, if checkout fails, check whether the payment API call returned a non-200 status code at that moment.

Analyze error events

Error events appear in the event stream. You can:

• Use Event Segmentation to measure error frequency and trends.
• Include error events in Funnel Analysis to measure their impact on conversion.
• Filter session replays by error events to investigate affected sessions.