New RUM Experience settings
- Latest Dynatrace
- Reference
- 2-min read
- Published Aug 07, 2025
- Preview
You can view and edit settings of the New RUM Experience via two main apps:
- In
Settings, all settings are accessible. - In
Experience Vitals, the most frequently used settings are integrated, and you can review and edit them for individual frontends.
In general, some changes in configuration such as cost control or most privacy-related settings may impact both the Classic and New RUM Experience. Others, such as the new session and event properties setting, impact only the New RUM Experience.
Prerequisites
To use the New RUM Experience, make sure that you have:
- Classic RUM enabled.
- OneAgent version 1.301+ if you want to enable it at the environment level.
Enablement and cost control
Cost control is applied to RUM experiences in both the previous and latest Dynatrace.
To enable New RUM Experience on an environment, open Settings and go to Collect and capture > Real User Monitoring > Traffic and cost control > Frontend - web or Frontend - mobile, depending on your tenant, and turn on Enable New Real User Monitoring Experience.
For individual frontends, you can also enable new RUM through Experience Vitals. Since the New RUM Experience is still in preview, you might encounter problems if not carefully configured.
Session Replay
Session Replay isn't enabled yet within the New RUM Experience, which is why you can only use the Enable Session Replay Classic option.
Experience Analytics
Experience Analytics is a Real User Monitoring (RUM) package that provides deep visibility into user behavior and experience. It includes User Interactions, capturing clicks, taps, scrolls, and inputs to reveal how users engage with your application. Coming soon, the new Session Replay will allow teams to visually replay real user sessions for faster troubleshooting and UX validation. Together, these capabilities help teams optimize journeys, reduce friction, and make data-driven decisions to improve digital experiences.
Frontend configuration
Changing the frontend name in RUM settings affects both RUM classic and New RUM Experience as well. After you change it, you'll need to use the name name in your DQL queries.
Privacy
All data privacy settings are respected by the New RUM Experience as well, including:
- Masking personal data in URIs
- Using persistent cookies for user tracking
- Data collection and opt-in mode
- Complying with "Do not Track" browser settings
- IP masking
You can use our new event modification API to mask certain user event fields on capture. We're planning to introduce additional privacy features.
Frontend detection
Frontend detection (application detection) rules are also respected by the new RUM experience. Within Experience Vitals, we also show the detection rules on the frontend level, allowing you to get an understanding of which rules apply to a specific frontend. However, as a rule higher up in the list already determines where the traffic is routed to, we recommend always reviewing the environment setting as well.
XHR Settings
Exclude XHR requests from monitoring
Specify a regular expression to match all URLs that should be excluded from becoming XHR request events. Dynatrace supports the JavaScript regular expressions syntax. The separation between different protocols of the URIs is not supported, so every protocol of the URI will be excluded.
Session and Event properties
Session and event properties reported by the RUM agent.
The new RUM experience introduces support for reporting user event and session properties, enabling enrichment of user events and sessions with additional context. Only explicitly allowed properties will be accepted and stored in Grail. The configuration supports up to 20 entries in total, shared between event and session properties. String, number, and boolean values are supported for both event and session properties.
Capturing must be configured via the SDK APIs. To read more about the available APIs, see New RUM APIs.