Cookie Consent Management
This topic covers how you can manage end-user cookie consent requirements in the Controller.
Splunk AppDynamics and Cookie Consent
The Splunk AppDynamics business transaction (BT) correlation with End User Monitoring (EUM) feature collects user data from base pages, reports the data to the Controller, and correlates the end-user activity with backend performance in the UI.
The base-page cookie consent setting requires cookie consent from users to correlate business transactions (BT) with EUM. In turn, the setting either activates or deactivates BT correlation based on how end users interact with your cookie consent requirements. When the setting is activated, you are requiring consent from your users to use cookies (on base pages) for business transaction correlation with EUM.
Configure the Base-page Cookie Consent Setting
You have two options for configuring the base-page cookie consent setting: at the account level (applies to all applications under an account) or at the application level (applies to one application).
Account-level Configuration
When you configure the base-page cookie consent setting at the account level, all applications under that account are affected; but you can still make application-level configurations, such as deactivating the setting for one application.
To configure at the account level:
- Go to Settings > Administration > Data Correlation.
- Under End User Monitoring, toggle Require cookie consent on base pages for Business Transaction Correlation on.
Application-level Configuration
To activate at the application level:
- Go to Applications > Configuration > User Experience App Integration > Business Transaction Correlation.
- Under Base Page Cookie Consent, toggle Require cookie consent on base pages on.
Default Settings
By default with compatible agent versions, business transaction correlation with EUM is activated.
- For existing applications in Controller < 21.11.0, by default the setting is deactivated at both the account- and application-level.
- For new applications created in Controller >= 21.11.0, by default, the setting is activated at both the account- and application-level.
End-user Interaction with Cookie Consent
The base-page cookie consent setting determines whether BT correlation with EUM is activated or deactivated (on base pages) based on how end users interact with your cookie consent requirements. The scenarios below demonstrate the interaction between the Controller settings and end-user responses to cookie consent.
When the Base-Page Cookie Consent Is Activated
When the base-page cookie consent setting is activated, BT correlation with EUM is activated only if the end user actively consents to cookies. If the end user declines or neither declines nor accepts cookie, BT correlation is deactivated.
| Cookie Consent toggle = On AND BT Correlation with EUM toggle = On | |
|---|---|
| User Action | BT Correlation Status |
| User accepts the cookie consent notice. | Activated |
| User rejects the cookie consent notice. | Deactivated |
| User neither accepts nor rejects the cookie consent notice. | Deactivated |
When the Base-Page Cookie Consent Is Deactivated
When the base-page cookie consent setting is deactivated, the application does not prompt the user to accept or reject the cookie consent notice.
- BT correlation is activated if the BT Correlation with EUM toggle is activated:
Cookie Consent toggle = OffAND BT Correlation with EUM toggle =OnUser Action BT Correlation Status Application does not display a cookie consent notice, thereby user action is not required. Activated - BT correlation is deactivated if the BT Correlation with EUM toggle is deactivated:
Cookie Consent toggle = OffAND BT Correlation with EUM toggle =OffUser Action BT Correlation Status Application does not display a cookie consent notice, thereby user action is not required. Deactivated