---
title: "Features (Help Center / Settings / Domain settings)"
ai_context: "Use this article for questions about RUMvision domain tracking features, feature toggles, tracking configuration and where to enable or disable monitoring capabilities. It covers Script loading, Privacy and Consent, Page tracking, User and device tracking, Browser diagnostics, Metric configuration, Developer settings, Single Page Applications and Experiments, plus the built-in feature search. Relevant for questions about enabling browser storage, JavaScript API access, soft navigation or SPA tracking, LoAF diagnostics, FetchLater, additional metrics, user conditions, Core Web Vitals attribution and which tracking features are enabled by default versus optional."
canonical: "https://www.rumvision.com/help-center/settings/domain/features/"
---

Breadcrumbs: [Home](https://www.rumvision.com/?format=md) > [Help Center](https://www.rumvision.com/help-center/?format=md) > [Settings](https://www.rumvision.com/help-center/settings/?format=md) > [Domain settings](https://www.rumvision.com/help-center/settings/domain/?format=md) > Features

# 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](https://www.rumvision.com/blog/a-step-in-to-the-future-of-the-web-what-are-origin-trials/?format=md) 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.

[![rumvision-domain-features-search.png](https://www.rumvision.com/file/upload/img/help-center/domain-settings/rumvision-domain-features-search.png)](https://www.rumvision.com/file/upload/img/help-center/domain-settings/rumvision-domain-features-search.png)

## 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](https://www.rumvision.com/blog/introducing-fetchlater-api-a-new-way-to-collect-core-web-vitals/?format=md) 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.