Dynatrace RUM
How to configure Dynatrace RUM at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service
Overview
This guide explains how to implement different privacy configurations for Dynatrace Real User Monitoring (RUM) and Session Replay on web frontends and how to reflect them in the Consenter Manager. Server-side monitoring is out of scope.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Dynatrace RUM JavaScript (latest Dynatrace and RUM Classic).
What the service does in this scope. RUM uses cookies, web storage and IndexedDB containing random IDs, timestamps, flags and configuration. Data privacy settings include masking personal data in URIs, masking user actions, user tracking, opt-in mode, Do Not Track and masking IPs and GPS coordinates. With opt-in mode, RUM is disabled and sets no cookies or storage until dtrum.enable is called; dtrum.disable stops it again. Opt-in mode is disabled by default. The rxVisitor cookie is stored for two years by default and can be shortened with rvcl=<months> (maximum 24).
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Opt-in mode on (Consenter calls dtrum.enable); user tracking off; IP masking on. |
| Configuration B — Higher risk | Opt-in mode on; persistent user tracking on with 12-month rxVisitor lifetime; Session Replay on. |
| Configuration C — Higher risk (default configuration) | Opt-in mode off; RUM sets cookies on page load. |
Step 1 — Configure Dynatrace
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Higher risk (default configuration) |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service | Improve the service |
| 2 | Opt-in mode | Data Privacy > General | On; dtrum.enable from Consenter | On; dtrum.enable from Consenter | Off |
| 3 | User tracking (persistent cookies) | Data Privacy > General | Off | On; rvcl=12 | Default |
| 4 | Mask IPs and GPS coordinates | Web → application → data privacy | On | On | Default |
| 5 | Session Replay | Application settings | Off | On | Default |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Dynatrace is a US-listed enterprise; list the United States. Managed deployments run in your environment.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Higher risk (default configuration) |
|---|---|---|---|
| Processing purposes | Improve the service | Improve the service | Improve the service |
| Tracking method | First party tracking (single session) | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers | Device identifiers, IP address |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, IP address anonymised | Browsing and interaction data, Device identifiers, Device characteristics, IP address anonymised | Browsing and interaction data, Device identifiers, Device characteristics, IP address, Non-precise location data |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | No personalisation | No personalisation |
| Maximum storage duration | Session | 12 months (rxVisitor) | 2 years (rxVisitor) |
| Processing location | Per tenant region / United States | Per tenant region / United States | Per tenant region / United States |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on