Domain settings
Once you have added the first domain, you can adjust the settings to your liking. To find these settings, navigate to one of the sections in the "Manage" subtree. For example "Tech stacks".
Settings
A few basic settings can be changed here, such as default percentile to be used in your dashboards as well as open tracking configuration settings. You can also specify if health checks should appear for this domain.
Available open tracking configuration settings:
- When to track
By default, we'll start tracking once our JavaScript has loaded. However, when CSS selectors were used as URL rules, elements that are identified via those CSS selectors might not have been constructed by the browser yet. In those cases, the value for "When to track" will auto-adjust to "interactive".
While you can't change it back to "instant", you can choose to let our script run slightly later after the "onload" event. - Track query string values
By default, our JavaScript won't store query string values, only parameters. For some parameter keys, you might want to make an exception. This can be convenient when you suspect that it's not specifically the keys, but their values that are resulting in anomalies in your data. Tracking values could then be of help. - Tracking anonymization rules
When tracking query string values, there's still a risk of mistakenly tracking Personally Identifiable Information (PII). You can specify anonymization rules to strip away possible PII information.
For example, by specifying the following:
{".*@.*..*":"email"}
Any email address pattern will be replaced byemailbefore it's ingested into your datasets.
Danger zone
When you cancelled your subscription and want to delete all domain-data, or when you want to start tracking a new domain but aren't ready to upgrade yet, you can delete a domain and all of its data and users.
On the Settings page, scroll to the very bottom of the page. You'll see a Danger Zone marked in red. When proceeding via the red button, the domain along with its URLs, URL categories, alerts, and scheduled reports will be deleted.
You'll first be prompted for your password.
Once this domain is deleted, all of its data will be permanently removed. This action cannot be undone.
Features
In the features panel, you'll find all available tracking options that you can either switch off or on. Available options are grouped into the following categories:
- Script loading
Control how and when the RUMvision tracking script is loaded and executed. - Privacy and Consent
Here you can manage privacy-related settings and consent behaviour for RUMvision tracking. - Page tracking
Allows you to configure how page context such as URLs, query parameters, and language are tracked. - User and device tracking
Allows you to configure what user behaviour and device conditions are tracked. - Browser diagnostics
Allows you to collect additional browser signals to help diagnose performance and browser-specific behaviour. - Metric configuration
Allows you to configure additional performance metrics alongside the default Core Web Vitals. - Developer settings
Allows you to access debugging tools, the RUMvision JavaScript API, and developer-focused features. - Single Page Applications
Enable tracking for soft navigations in Single Page Applications (SPA) and client-side rendered sites. - Experiments
Contains experimental and browser origin trial features
Quick search
This panel comes with a convenient search functions that allows you to easily find where settings are located. Additionally, it will depict if features are enabled or disabled using icon symbols.
Enabled by default
Features that comes with important RUM diagnostics are enabled by default, but can be switched of when not deemed necessary. The following settings are enabled by default but can be disabled at any time.
| Feature | Category | Reasoning |
|---|---|---|
| Track sub-parts | Metric configuration | Collects both involved elements (LCP, INP, CLS) and sub-parts (TTFB, FCP, LCP, and INP) that contribute to performance events and improves diagnostics. |
| User conditions | User and device tracking | Earlier outcomes show a high correlation between user´s device memory and performance issues, making it valuable to tracking this by default. |
| Track LoAF | Browser diagnostics | LoAF API allows RUMvision to collect exact scripts that are contributing to performance issues, directly pointing site owners into the right direction. |
| User FetchLater | Developer settings | The fetchLater API allows scripts to keep expanding a beacon and only send it once, minimizing the amount of request coming from a RUM tool. |
| Allow browser storage | Privacy and consent | Helps bucketing pageviewtype (warm vs cold pageloads) information more correctly and limits the amount of browser checks (brand, version, platform) to once per session. When some pages are blocked from being tracked, browser storage allows our inline script to do a pre-check, fully preventing our JS from being embedded on those pages. |
Snippet
You'll be able to copy your snippet or snippet ID to other sources. When using a plugin like Magento2 RUMvision by Elgentos, you'll only need the ID. When implementing via Google Tag Manager, you'll need to copy the full code snippet.
Content Security Policy
More sites are deploying a Content Security Policy. As a result, either the JavaScript file, our beacon endpoint or both might be blocked. In those cases, you'll need to add certain hostnames to certain directives. You'll find them in the "Explanation" section of the Snippet page.
Tech stack
The RUMvision Tech stack settings allows you to select which techstacks and categories applies to your website. This can be assigned on an individual website basis.
When registering, RUMvision will already attempt to automatically fetch information like CDN and platform. As a result, you might see some settings being assigned already.
Selecting tech stacks
For other categories like CMP or Caching, you will need to assign the labels that apply to your website.
Enabling tech stack features
Assigning items does not result in a change of tracking settings by itself. When items are selected, an info-box will show up alerting you about available tracking features. An example:
We have built in support for $techstack. Do you want to enable tracking additional tracking dimensions?
Enable additional tracking dimensions
You'll be able to activate items per techstack by toggling the checkbox to the right. Once saved, tracking features such as CMP consent tracking or Custom Timing per platform or CDN could start collecting additional information right away.
URLs
Here you'll be able to manage or restore deleted URL rules. URL rules can be added as absolute URLs, regular expressions or CSS selectors.
A deep-dive into URL rule management can be found in the adding pages chapter.
Users
You can manage users per organisation or per domain. In this section, you'll be able to manage users per domain.
A deep-dive into user management can be found in the invite users chapter.




