Set up your bannerConfigure Your ToolsMonitoring and Performance

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.

  1. Implement the service as described below.
  2. Map the implementation in the Consenter Manager.
  3. 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 areaFixed behaviour / required action
Processing purposesImprove the service (performance monitoring)
Consent gatingSet window["adrum-disable"] = true until Consenter consent, or load the agent only after consent
Cookie domainOptionally restrict to the exact current domain
ContractSplunk / Cisco DPA

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesImprove the service—
Tracking methodFirst party tracking (single session)Short-lived cookies deleted after reading
IdentifierNo identifier—
Data categoriesAggregated site statistics, Browsing and interaction data, Device characteristicsTiming, Ajax and error data
Legal role of data recipientProcessorProvider DPA
Personalisation modelNo personalisation—
Maximum storage durationUntil read (cookies); retention per account—
Processing locationPer controller/EUM region; United StatesUS 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

On this page