REAL USER MONITORING
See how your pages perform for real visitors
Sample Core Web Vitals, client errors and console diagnostics by domain. Review them in the console by route and release. Sampling is set per domain and can stay at zero.
WHAT IT DOES
Measure what visitors experience
RUM collects measurements from the visitor's browser for the domains and sample rate you choose.
Visits to your pages
- Sampled visit
- Not sampled
Sampling set per domain and can stay at zero
Console: measurements from the sampled visits
Web vitals
Loading, layout shift, interaction responsiveness and navigation timing.
Client errors
JavaScript errors and unhandled rejections, under a closed set of names.
Console diagnostics
Page console output as a diagnostic, with collection health by domain.
Review by
- Route
- Release
Web vitals from sampled visits
Collect loading, layout shift, interaction responsiveness and navigation timing from the visitor's browser. Collection follows the sample rate you set.
Client errors and unhandled rejections
Record JavaScript errors and unhandled promise rejections under a closed set of names. Raw error message text is not used as a name.
Console diagnostics
Capture page console output as a diagnostic. In consent-gated modes it follows the analytics consent category. The console shows collection health by domain.
Review by route and release
The Client RUM page in the console lets you compare measurements across routes and releases.
HOW IT WORKS
From browser to console
RUM uses the same browser collector as the rest of Noxtica.
Your page
Noxtica browser collector
The same collector as the rest of Noxtica. RUM needs no extra code.
Noxtica
Sampling and consent
Browser measurements
The sample rate is set for each domain and can stay at zero. In consent-gated modes the page reports analytics consent before collection starts.
Console
Vitals, errors and diagnostics
Sampled measurements
Read by route and release, within operator role and retention settings.
Load the collector
Add the Noxtica browser collector to your pages. RUM needs no extra code.
Set sampling and consent
Choose a sample rate for each domain. In consent-gated modes, the page reports analytics consent before collection starts.
Review in the console
Operators read vitals, errors and console diagnostics by route and release, within their role and retention settings.
WHERE IT FITS
Questions RUM helps answer
Use RUM to see where friction appears, then decide what to change.
Which routes feel slow?
Compare sampled web vitals across routes to find where loading or interaction lags.
Did a release add errors?
Compare client errors and console diagnostics across releases.
How do visitors move within a page load?
Where tracker collection is enabled, the console also offers journeys, funnels and heatmaps. A tracker session covers one page load, so they do not follow visitors across pages.
HOW TEAMS CONNECT IT
Connect it in your pages and console
RUM runs from the same browser script as the rest of Noxtica.
- Use the Noxtica browser collector on your pages. RUM needs no extra code.
- Set the sample rate for each domain in the Noxtica console. It can stay at zero.
- In consent-gated modes, connect your consent tool so the page reports analytics consent.
LIMITS
Boundaries and responsibilities
Measurements are samples from browsers that allow collection.
- Controlled availability. Capture and read access are configured separately for each tenant and domain, and access is agreed with Noxtica.
- Sampled data is not a census of traffic. A missing measurement does not mean a good or a bad visit. Browser support, privacy settings and consent change what is collected.
- You are responsible for notice, consent, sampling and retention. Console output and error detail can contain personal data that your page writes.
- Measurements and any alerts built on them can produce false positives and false negatives. Your team decides what to do. Native mobile app monitoring is not supported.
Monitoring and replay must follow your notices, consent and masking settings, and our acceptable use rules.Read the acceptable use policy
FAQ
Questions about real user monitoring
Is RUM the same as session replay?
No. RUM samples performance and error measurements. Replay records page structure and interactions and has its own consent category.
Can I follow a visitor across pages?
No. A tracker session covers one page load by design, so funnels and journeys do not span pages.
Can I turn RUM off for a domain?
Sampling is set per domain and can stay at zero. Capture and read access are configured separately.
Related products
REAL USER MONITORING
Ask about real user monitoring access
Access is agreed with Noxtica for each tenant. Contact the team to confirm eligibility and your consent setup.