The Interaction Analytics system tracks a defined set of user interactions and CMP-triggered events to help you understand how users engage with your Consent Management Platform (CMP). These events allow you to monitor when the CMP is shown, how users respond, and how consent decisions are recorded across different regulatory environments.
Because opt-in and opt-out frameworks behave differently, the events captured also differ between GDPR (Opt-In) and US Opt-Out configurations.
To make this distinction clear, the following documentation is divided into two tabs:
GDPR (Opt-In) – Events based on explicit user consent actions, such as accepting, denying, or saving preferences.
US (Opt-Out) – Events focused on CMP display eligibility, automated opt-outs, and explicit denials.
Each tab lists the events tracked in that regulatory model, along with their descriptions and usage within the analytics dashboards or downloadable reports.
These events reflect interactions with the CMP only and do not measure website traffic, pageviews, or bounce behavior.
Use these reference tables to understand how CMP behavior is logged, how user choices are reflected in your analytics dashboards, and how specific user actions translate into system events.
🇪🇺 | GDPR (Opt-In) — Tracked Interactions & Events
For GDPR and other opt-in environments, Interaction Analytics tracks explicit user actions within the CMP. These events help you understand how users interact with your banner, which choices they make, and how often the CMP is displayed. All events are sent to the backend together with additional context for analysis.
The following sections list all events captured for GDPR setups, along with their definitions and usage.
📊 Primary Events Used in the Dashboard
These events appear directly in the Interaction Analytics dashboard.
Event | Description |
|---|---|
CMP_SHOWN | The CMP was displayed to the user. |
ACCEPT_ALL_L1 | User clicked “Accept All” on the first layer. |
DENY_ALL_L1 | User clicked “Deny All” on the first layer. |
SAVE_L1 | User clicked “Save” on the first layer. |
ACCEPT_ALL_L2 | User clicked “Accept All” on the second layer. |
DENY_ALL_L2 | User clicked “Deny All” on the second layer. |
SAVE_L2 | User clicked “Save” on the second layer. |
These events represent the core consent interactions and are used to calculate dashboard KPIs such as Interaction Rate, Accept Rate, and CMP Displays.
🔎 Additional Events (Downloadable Report Only)
These events are not shown in the dashboard but are included in downloadable reports for detailed analysis.
Event | Description |
|---|---|
CCPA_TOGGLES_OFF | User clicked “OK” while the CCPA toggle was set to Off. |
CCPA_TOGGLES_ON | User clicked “OK” while the CCPA toggle was set to On. |
PRIVACY_POLICY_LINK | User clicked the Privacy Policy link. |
IMPRINT_LINK | User clicked the Legal Notice / Imprint link. |
MORE_INFORMATION_LINK | User clicked the “More Information” link. |
🧠 How Events Are Recorded
Whenever the CMP is displayed, a CMP_SHOWN event is logged.
When the user makes a consent choice (Accept All, Deny All, Save), a corresponding consent event is recorded.
If the user interacts with the CMP without making a consent choice (e.g., reopening privacy settings), only the relevant display or link-click event is logged.
Interaction Analytics only tracks actions within the CMP. It does not measure website views, page visits, or bounce behavior.
📝 Examples
1. First-time visit — user accepts all
The banner is displayed
The user clicks “Accept All”
Events recorded:CMP_SHOWN,ACCEPT_ALL_L1(or L2 depending on design)
2. Returning visitor — CMP not shown
The user already made a choice previously
The CMP does not appear
Events recorded: None
3. User opens privacy settings and closes without making changes
User clicks a Privacy Button to open the CMP
User closes the CMP without saving
Events recorded:CMP_SHOWN
4. User opens privacy settings and chooses “Save”
User opens CMP
User updates settings and clicks “Save”
Events recorded:CMP_SHOWN,SAVE_L1orSAVE_L2
🇺🇸 US (Opt-Out) — Tracked Interactions & Events
In US opt-out environments (e.g., CCPA, GPC, UOOM), Interaction Analytics tracks a focused set of events that describe when the CMP could appear, when it was actually shown, and how users or browser signals reject or accept tracking. These events form the basis of all KPIs in the Opt-Out Analytics Dashboard.
Below is the complete list of tracked events for US opt-out CMP configurations.
📊 Tracked Events
Event | Description | |
|---|---|---|
CMP_ELIGIBLE | Counts the total number of times end users land on the website. Returning users are counted again, regardless of any previous consent decisions. | |
CMP_SHOWN | The CMP was actually displayed to the user. This includes automatic displays and displays triggered by CMP surface settings. | |
CMP_REQUEST_DISPLAY | The CMP was manually opened by the user (e.g., via a Privacy Button or settings link). | |
ACCEPT_EXPLICIT | The user explicitly accepted tracking through a clear manual action (e.g., clicking “OK” or an acceptance button). | |
ACCEPT_IMPLICIT | Tracking was accepted automatically based on system logic (e.g., non-regulated region or implicit acceptance rules). | |
DENY_ALL_EXPLICIT | The user explicitly denied tracking through a clear action (e.g., clicking “Deny All”). | |
DENY_ALL_IMPLICIT_CMP_NOT_SHOWN | Tracking was denied automatically through a browser or device signal (e.g., UOOM/GPC) without the CMP ever being shown. | |
DENY_ALL_IMPLICIT_CMP_SHOWN | Tracking was denied automatically via a signal (e.g., UOOM/GPC), and the user dismissed the CMP (e.g., closing it) without providing consent. |
🧠 How These Events Work
CMP_ELIGIBLE marks an opportunity for interaction and may be triggered again on return visits.
CMP_SHOWN captures times when the CMP is visually displayed.
CMP_REQUEST_DISPLAY represents deliberate user-initiated access.
Explicit events record clear user consent actions.
Implicit events record automated outcomes caused by browser– or device-driven privacy signals.
Interaction Analytics tracks only CMP interactions, not general webpage traffic.
Usercentrics CMP deploys a local storage entity called: uc:analytics:firedEvents:SETTINGSID which is used to ensure the correct functioning of event tracking by preventing events from being triggered more times than intended.
🗓️ Event Availability
Note: US Opt-Out events (including CMP_ELIGIBLE, CMP_SHOWN, explicit/implicit accept/deny events) are available only for data collected on or after November 13, 2025.
No historical data is included before this date.