Does Dynatrace require cookie consent?

No. Dynatrace is an application performance monitoring tool collecting technical telemetry for site reliability. It performs no advertising tracking or behavioral profiling. Performance monitoring is supported under GDPR legitimate interest (Article 6(1)(f)), though the persistent rxVisitor cookie (1 year) warrants privacy policy disclosure.

What cookies does Dynatrace set?

Dynatrace sets rxVisitor (1-year expiry) as a RUM visitor identifier, dtSa (session) for sampling rate assignment, dtCookie and dtLatC (session) for session state and latency measurement, and rxvt (session) as a session timeout marker. Scripts load as ruxitagentjs_*.js from js-cdn.dynatrace.com or a first-party domain.

How does ConsentStack handle Dynatrace?

ConsentStack classifies Dynatrace as essential performance monitoring and does not block it. It is detected via ruxitagentjs script loads from js-cdn.dynatrace.com or customer environment domains. Because it serves site reliability with no advertising purpose, ConsentStack allows it under legitimate interest without requiring visitor consent.

What tracker domains does Dynatrace use?

ConsentStack has catalogued tracker domains for Dynatrace including js-cdn.dynatrace.com and dt-cdn.net. These are the network destinations Dynatrace's scripts contact, which a consent platform blocks until a visitor agrees.

Dynatrace - AI Observability & Browser Monitoring Info

Back to Vendor Library

Overview

Dynatrace is an AI-powered observability and Application Performance Monitoring (APM) platform. Its browser agent implements Real User Monitoring (RUM) to help engineering and operations teams detect, diagnose, and resolve performance issues affecting real users. Dynatrace is an infrastructure and reliability tool with no advertising or behavioral profiling purpose.

What This Script Does

Agent Injection Dynatrace's browser agent (ruxitagentjs_*.js) is injected via one of three methods: synchronous inline script in the <head>, asynchronous script tag, or server-side injection via the Dynatrace OneAgent. The agent file is served either from the customer's own CDN/domain (first-party delivery) or from Dynatrace's infrastructure at js-cdn.dynatrace.com.

Real User Monitoring (RUM) Data Collection The agent instruments the browser using the Navigation Timing API, Resource Timing API, and PerformanceObserver to capture:

Page load timing: DNS resolution, TCP connect, Time to First Byte (TTFB), DOM interactive, DOM complete, First Contentful Paint (FCP), Largest Contentful Paint (LCP)
Resource loading: load time and size for every JavaScript, CSS, image, and font asset on the page
XHR and Fetch request timings: URL, duration, HTTP status code, and response size for all API calls
Long tasks: main-thread blocking periods exceeding 50ms (identifying JavaScript performance bottlenecks)
Cumulative Layout Shift (CLS) and other Core Web Vitals

Error Tracking

Captures unhandled JavaScript exceptions with full stack traces, including the error message, source file, line number, and column number
Records failed XHR and fetch requests (4xx/5xx responses) with URL, status code, and duration

User Action Tracking

Instruments user interactions (clicks, form submissions, page navigations, XHR-triggered view changes in SPAs) to create "user action" performance traces
Associates each user action with its performance impact (e.g., how long a button click took to produce a visual response)
Does not record the content of form fields, keystrokes, or sensitive input values

Session Identification To correlate RUM data across page views and provide session-level analysis:

rxVisitor (first-party, 1 year) — Dynatrace RUM visitor identifier for correlating sessions over time
dtSa (first-party, session) — sampling rate and session assignment cookie
dtCookie / dtLatC (first-party, session) — session state and latency measurement cookies
rxvt (first-party, session) — session timeout marker

Domains contacted: {customer-environment-id}.live.dynatrace.com, js-cdn.dynatrace.com (if using CDN delivery), {customer}.dynatracelabs.com

Data transmitted: Performance timing values, error messages with stack traces, resource URLs, XHR/fetch API endpoint URLs, user action names, visitor and session identifiers. IP addresses are transmitted and may be used for geolocation but are not stored in raw form.

Consent & Compliance

GDPR/ePrivacy: Dynatrace collects technical telemetry data for site reliability and performance purposes. The data is technical in nature — performance timings, error messages, resource URLs — rather than behavioral profiles for advertising or marketing. Dynatrace acts as a data processor under the site operator's control. The rxVisitor cookie (1 year) is a persistent identifier that could require consent under strict ePrivacy interpretations, though performance monitoring is widely treated as essential for site operation under a legitimate interest basis (GDPR Article 6(1)(f)). Operators should document their legitimate interest assessment in a DPIA.

CCPA/CPRA: Technical performance data collected by Dynatrace is not personal information used for advertising purposes. Dynatrace processes data as a service provider under CCPA.

EU-US Data Transfers: Dynatrace LLC participates in the EU-US Data Privacy Framework (DPF) and offers Standard Contractual Clauses.

Consent category: Essential / Performance Monitoring (no advertising, no cross-site tracking, no behavioral profiling).

Should You Block This Without Consent?

No. Dynatrace is an application performance monitoring tool collecting technical telemetry data for site reliability purposes. It does not perform advertising tracking, behavioral profiling, or cross-site data sharing. Performance monitoring can be justified under legitimate interest without user consent, though the rxVisitor persistent cookie warrants disclosure in the privacy policy. Operators with the most conservative consent posture may choose to load Dynatrace conditionally, but regulatory guidance broadly supports performance monitoring as a legitimate interest use case.

Is Dynatrace GDPR compliant?

Dynatrace typically loads analytics trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Dynatrace can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Dynatrace, not on Dynatrace itself.

Visit website