What data does RUMvision collect?
RUMvision collects technical information that helps you understand how your website performs for real visitors.
The exact data depends on your configuration, but our baseline Real User Monitoring is focused on website performance, browser conditions and the context needed to diagnose issues.
Performance data
RUMvision can collect performance measurements such as:
- Core Web Vitals such as LCP, CLS and INP
- TTFB, FCP and other loading and rendering timings
- responsiveness and navigation timings
- resource, caching and delivery characteristics
These measurements help identify where visitors experience slow loading, layout shifts or delayed interactions.
Page and navigation context
Performance data is most useful when you know where an issue occurred. RUMvision can therefore process information such as the relevant page path, page or template classification and limited navigation context.
Query parameter values and URL fragments are not collected as ordinary RUM dimensions by default.
Website owners should avoid placing names, email addresses, authentication credentials or other sensitive information directly in URL paths. If your website does this, the relevant data should be excluded or transformed before it is sent to RUMvision.
Browser, device and network information
Website performance can differ significantly depending on the visitor's browser, device and network conditions.
RUMvision can therefore process technical information such as:
- browser and operating system categories
- device category
- viewport characteristics
- relevant device capabilities
- network characteristics
We focus on information that has a clear performance, compatibility or measurement-quality purpose.
Some additional browser or device information may be available through optional functionality. We cover those features separately.
Country-level location
RUMvision can associate measurements with country-level location information. This can help identify regional performance differences, for example when visitors in one country experience slower delivery than visitors elsewhere.
Raw IP addresses are not retained in the normal RUM measurement dataset.
Like other internet services, IP addresses may still be processed temporarily as part of normal network, infrastructure and security operations, including where needed to derive country-level information.
Limited visit and engagement context
RUMvision can process limited context that helps interpret a performance measurement, such as:
- timestamps
- pageview and navigation context
- time on page
- maximum scroll depth
- pageview counts
- limited same-site navigation context
This information is used to understand technical performance and website outcomes. It is not intended to recreate a visitor's complete browsing history.
Technical identifiers
RUMvision uses randomly generated technical identifiers where needed to associate measurements that belong together.
These can include request, pageview, navigation or visit identifiers. Where persistent browser storage is enabled, RUMvision may also use a first-party Browser Identifier for limited visit continuity.
These identifiers are not based on browser fingerprinting and are not intended to identify a visitor by name or recognise a browser across unrelated websites.
For more detail, see our separate article on browser storage and identifiers.
Measurement quality
RUMvision may also process technical information needed to identify automated traffic, measurement noise or unreliable measurements.
This helps prevent bots, browser behaviour or incomplete measurements from distorting your performance data.
Customer-configured data
Customers can configure additional dimensions to add useful technical or business context to their RUM data.
These fields should only contain information that is necessary for website performance analysis. They should not be used to send names, email addresses, account identifiers, authentication credentials, security tokens or sensitive personal information.
What changes when optional features are enabled?
Some RUMvision features can process additional categories of technical data.
For example, JavaScript error monitoring may process error messages and stack traces, while Business Metrics can process configured events or goals. Responsiveness diagnostics can add limited technical interaction information.
These features are modular and are not automatically part of every RUMvision deployment.
You can read more about them in our article on optional monitoring features.
In short
RUMvision collects the technical information needed to understand website performance in real-world conditions.
We aim to keep that data limited to what is useful for performance, reliability, responsiveness and measurement quality, while avoiding direct identifiers and unnecessary personal information.
