Dynatrace Real User Monitoring relies on browser cookies to correlate user interactions in the browser (i.e., user actions) with general page and backend performance metrics.
Cookies are used to:
- Monitor site performance
- Analyze website usage
- Track user behavior
HTTPOnly flag. Cookies must be included with each request so that user actions can be correlated with backend performance.
You can use the
Secure cookie flag, however this leads to loss of visibility into any unencrypted HTTP communication.
The following table provides an overview of cookie usage in Dynatrace. These are all first-party cookies.
|dtCookie||<randomValue> | <encoded application info>||session||100B||Technical session ID for PurePath correlation|
|dtLatC||<numeric value>||session||5B||Measures server latency for performance monitoring|
|dtPC||<serverID>$<randomValue>_<currentMillis>v<randomValue>||session||54B||Required to identify proper endpoints for beacon transmission; includes session ID for correlation|
|dtSa1||<URL-encoded action name>||session||max URL length||Intermediate store for page-spanning actions|
|rxVisitor||<visitorid>||permanent||45B||Visitor ID to correlate sessions|
|rxvt||<timestamp> | <timestamp>||permanent||27B||Session timeout|
dtSa cookie is used to save user action names, such as
Cookie opt-out capability
The cookies listed above are required for proper function of Dynatrace Real User Monitoring. If you use Dynatrace to monitor your websites and you provide an opt-out option that allows your users to decline the use of Dynatrace cookies, then Dynatrace Real User Monitoring won't work or deliver the expected results.
To provide your end users with a cookie opt-out capability, Dynatrace must be configured appropriately. Usually Dynatrace creates tracking cookies automatically. When using cookie
Note: To configure Cookie opt-out mode please see How do I configure Real User Monitoring for privacy?.
sessionStorage to store a backup of
dtCookie because certain browsers delete random cookies when too many cookies are used. Dynatrace sets the following two keys (see the table above for examples):
localStorage. The following table gives an overview of the key/value pairs that Dynatrace writes to local storage.