AppDynamics Browser RUM
How to configure AppDynamics Browser 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 reflect Splunk AppDynamics Browser Real User Monitoring (RUM) in the Consenter Manager. Server-side APM is out of scope. Browser RUM has no visitor-facing privacy settings beyond the switch noted below, so this guide uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. AppDynamics JavaScript Agent (adrum) for Browser RUM.
What the service does in this scope. Browser RUM uses short-lived cookies to collect data and correlate events; AppDynamics states they contain no personally identifiable information and are deleted immediately after being read. ADRUM_BT cookies are written by the server-side agent to correlate browser data with business transactions. By default, the cookie is set on the broadest version of the originating domain. Setting window["adrum-disable"] = true before the agent loads disables browser monitoring.
Step 1 — Implement AppDynamics Browser RUM
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Improve the service (performance monitoring) |
| Consent gating | Set window["adrum-disable"] = true until Consenter consent, or load the agent only after consent |
| Cookie domain | Optionally restrict to the exact current domain |
| Contract | Splunk / Cisco DPA |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Improve the service | — |
| Tracking method | First party tracking (single session) | Short-lived cookies deleted after reading |
| Identifier | No identifier | — |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics | Timing, Ajax and error data |
| Legal role of data recipient | Processor | Provider DPA |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Until read (cookies); retention per account | — |
| Processing location | Per controller/EUM region; United States | US enterprise; CLOUD Act |
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