Real User Monitoring (RUM) and Session Replay

What RUM helps you solve

See who is affected, replay what happened, and trace the responsible system

RUM gives frontend, product, development, and SRE teams a shared view of real sessions. Segment the impact, reproduce the user journey, and move from the browser request into the backend service that caused the experience.

01Frontend performanceTrack page loads, resource timing, requests, and Core Web Vitals from real traffic.
02Errors and Session ReplayConnect JavaScript errors and user actions to the visual session where they occurred.
03Frontend-to-backend correlationFollow an affected browser request into its API, distributed trace, logs, and dependencies.
04Experience and conversionCompare journeys by user, device, geography, version, and business attribute.

A real investigation path

From “the page froze” to a reproducible user journey and clear owner

RUM first quantifies who and what was affected, then replays the interaction and follows the browser request into backend services when needed.

Find the users, pages, and environments where the issue clusters

EvidenceCore Web Vitals, JavaScript errors, resource timing, version, device, and region

ConclusionQuantify the affected users and business journeys

Data path

Web RUM SDK → Views, resources, errors, and actions → Session Replay → APM traces and logs

Best for

For frontend, development, SRE, product, and operations teams improving web performance, critical journeys, and conversion.

Requirements

The web application requires the RUM SDK. Session Replay should follow privacy and sampling policies, and backend attribution requires trace context.

View setup guide

Tie experience quality to the journeys that matter to the business

Define important actions and workflows, then compare completion, latency, and errors by user segment, version, and channel. Prioritise fixes by the number and value of users affected, not only by aggregate averages.

View documentation

Tie experience quality to the journeys that matter to the business

Frequently asked questions

What is Real User Monitoring (RUM)?

Real User Monitoring captures the performance and behavior of actual web or mobile sessions, including page loads, resources, requests, errors, actions, devices, and locations. Guance correlates this evidence with Session Replay and backend telemetry.

How is RUM different from Synthetic Monitoring?

RUM measures real users on real devices and networks. Synthetic Monitoring runs controlled checks from selected locations on a schedule. Together they show both expected availability and actual user impact.

Can Session Replay be used with privacy controls?

Yes. Collection, sampling, masking, and privacy policies can be configured to reduce exposure of sensitive user content while preserving useful investigation evidence.

Can a frontend issue be connected to a backend trace?

Yes. With trace propagation and consistent service tagging, an affected browser request can be linked to its API, distributed trace, logs, and downstream dependencies.

Who uses RUM data?

Frontend and development teams use it to debug performance and errors; SRE teams use it to measure user impact; product and operations teams use it to understand journey quality and conversion.

Reliable, secure, and compliant

Visit the Trust Center