Transition from RUM Classic to the New RUM Experience

• Latest Dynatrace
• Explanation
• 1-min read
• Updated on Feb 20, 2026

If you already monitor your web and mobile frontends with RUM Classic, upgrading to the New RUM Experience is straightforward. Learn how the New RUM Experience relates to RUM Classic and how to enable it.

Enable the New RUM Experience

Upgrading from RUM Classic to the New RUM Experience requires only a configuration change. The following guides outline the necessary steps.

Web Android iOS React Native Flutter .NET MAUI

Relationship between the New RUM Experience and RUM Classic

The New RUM Experience currently relies on certain RUM Classic functionalities. Here’s what this means for you.

Enabling the New RUM Experience

You can currently enable the New RUM Experience only if RUM Classic is active. At this time, disabling data ingestion into RUM Classic and fully migrating is not possible.

Configuration

Most configuration settings for the New RUM Experience are based on those already used by RUM Classic. This means that:

Event and session properties are an exception—they have a separate configuration from user action and session properties in RUM Classic.

Monitoring traffic

When the New RUM Experience is enabled, RUM beacons in a new format are sent alongside RUM Classic beacons to the same endpoint.

Infrastructure requirements

At this point, the New RUM Experience relies only on the HTTP headers and cookies already covered by the firewall constraints for RUM Classic. If your firewalls and other infrastructure components are already configured to let these headers and cookies pass through, no further changes are required when you enable the New RUM Experience.

Built-in metrics

The New RUM Experience provides numerous built‑in metrics. Due to its different underlying data model, these are not direct equivalents of the RUM Classic metrics. Still, many metrics have functional replacements, which are listed in RUM metrics migration.