Dashboard
The TrustCommander performance dashboard provides insights into critical KPIs of your consent management setup.
Interface
Filter options
The dashboard provides KPIs for each individual TrustCommander banner. You can customise the dashboard by adjusting filter settings at the top left of the interface. TrustCommander provides the following filters:
Configures which privacy banners are displayed in the dashboard table.
Time selection
On the top right you will find options to filter data for a specific time range by specifying a start and end date. The dashboard will show metrics including the selected start and end date.
To select only one day, the day has to be clicked twice in the date picker so that both the start and end date are set to the needed day.
Export options
It is possible to export CSV reports via the EXPORT option on the top right in the interface. Reports will only include data for the selected timeframe.
Data collection is done in real-time, but metrics calculation is updated overnight, therefore no data is available in the dashboard for the current day (if you need immediate data, you can export the raw consent data via the "Options" page).
Measurement approach
TrustCommander measures privacy banner interactions to calculate consent KPIs.
All metrics are visitor/ traffic based and not user based. TrustCommander therefore sets a 1st party cookie TCPID on website visitors. It deduplicates certain metrics (e.g. opt-in actions) of a visitor based on this cookie. TrustCommander identifies visitors as new visitors in case they delete this cookie.
Optin vs. optout action
To understand dashboard metrics it is important to understand how TrustCommander measures optin and optout actions.
An optin action occurs when a visitor...
clicks the accept button of the privacy banner.
saves the privacy center with at least one category set to "on".
navigates to a second page (only in case implicit "on navigation" consent was installed).
scrolls on the landing page (only in case implicit "on scroll" consent was installed).
clicks any element on the website (only in case implicit "on click" consent was installed).
Examples
Following examples outline a hypothetical scenario with only one website visitor to explain the measurement approach:
Example 1
A new visitor arrives at a website with a TrustCommander privacy banner.
He accepts the privacy banner and immediately navigates to the privacy policy page.
There he re-opens the privacy center and revokes his prior consent.
This would lead to one optin action and one optout action and two banner views. TrustCommander deduplicates action and therefore only uses the last action of a visitor to calculate the consent KPIs per day. Additionally it deduplicates the banner views per visitor per day therefore only counts one banner view in this scenario. This user journey leads to an optin rate of 0%, a no choice rate of 0%, and optout rate of 100%.
Example 2
A new visitor arrives at a website with a TrustCommander privacy banner.
He does not interact with the banner and leaves the site immediately.
On the next day he returns to the website.
He accepts the privacy banner and immediately navigates to the privacy policy page.
There he re-opens the privacy center and revokes his prior consent.
On the first day this would lead to no action and one deduplicated banner view. On the second day this leads to one deduplicated optout action (see Example 1) and one deduplicated banner view.
For a selected timeframe that only includes the first day this would result in a no choice rate of 100%. For a selected timeframe that only includes the second day this would result in a optout rate of 100%. For a selected timeframe that includes both days this would result in an optin rate of 0%, a no choice rate of 50%, and an optout rate of 50%.
This measurement approach and the following metrics are based on the standard usage of TrustCommander banner templates. In case of a banner customisation or custom workflow, part of the metrics might have a different meaning.
Dashboard metrics
Following you will find detailed descriptions of each metric in the dashboard. When available you can expand the line to get the break down by categories.
Global
Metrics are deduplicated each day. On 23/09/2021 the calculation method has changed to take into account both banner displays and Privacy Center displays (previously, only banner displays were taken into account). When displaying the dashboard after this date, every date range will take into account Privacy Center display.
Metric | Description |
Visitors exposed to CMP | The number of visitors viewing a screen of the CMP for the requested time period. It includes visitors viewing the first layer as well as visitors opening the privacy center. |
Give consent | The number of visitors who at least consent to one category. It includes consent collected via the first layer (accept all, reject all buttons) as well as consent collected via the privacy center. In case several consent actions are collected during the same day (consent, no consent), only the last one is taken into account. |
Do not give consent | The number of visitors who consent to no category. It includes visitors who explicitly don’t give consent (e.g. click reject all button) and “no choice visitors” with no action recorded. In case several consent actions are collected during the same day (consent, no consent), only the last one is taken into account. |
Consent methods
Metric | Description |
Banner button | The number of visitors who explicitly consent to all categories by clicking the accept button on the first layer. |
Privacy center | The number of visitors who explicitly consent to at least one category by clicking the save button on the privacy center. |
Implicit > Continue browsing | The number of visitors who implicitly consent to all categories by navigating to a second page on the website. |
Implicit > Page click | The number of visitors who implicitly consent to all categories by clicking any element on the page. |
Implicit > Page scroll | The number of visitors who implicitly consent to all categories by scrolling down on the page. |
How engaged visitors react to CMP?
Metric | Description |
Visitors making an explicit choice | The number of visitors saving a consent choice. It includes choices made by clicking consent or refuse buttons on the first layer as well as choices saved via the privacy center. |
Explicitly consent (at least 1 category) | The number of visitors who at least consent to one category. It includes consent collected via the global layer (accept all, reject all buttons) as well as consent collected via the privacy center. |
Explicitly reject | The number of visitors who consent to no category. It only includes visitors who explicitly don’t give consent (e.g. click reject all button). It excludes “no choice visitors” with no action recorded. In case several consent actions are collected during the same day (consent, no consent), only the last one is taken into account. |
How visitors interact with the CMP banner?
Metric | Description |
Interaction rate | The number of visitors who at least interact with one element of the CMP first layer. It includes clicks on accept button, reject button, configure button (opening the privacy center) and text links. |
How visitors use the privacy center?
Metric | Description |
Visitors exposed to privacy center categories | The number of visitors viewing the category section of the privacy center for the requested time period. |
Visitors exposed to privacy center vendors | The number of visitors viewing the vendor section of the privacy center for the requested time period. |
Visitors saving a configuration | The number of visitors clicking the privacy center save button. It includes visitors using the save button as well as the accept all or reject all buttons. |
Visitors not saving a configuration | The number of visitors viewing the privacy center and not saving a configuration. It includes visitors using the closing cross to go back to the first layer and visitor leaving the website from the privacy center. |
Understanding metrics
No choice vs. Bounce rate
In an optin configuration (no tracking before a user provides consent), bounce rate tracking is not possible anymore as bouncers usually won't interact with the website and therefore won't provide consent for analytic services. The no choice metric of TrustCommander can help to get an idea on your bounce rate, but it is not the same metric!
In a default optin configuration, the "no choice" is expected to include:
Normal cases:
Visitors who do not provide an optin and leave the website (bounce)
Visitors who do not provide an optin and continue to browse the website without closing the privacy consent message (possible with header/ footer banner templates, less likely with a popin template that blocks website navigation)
Visitors who do not provide an optin who continue browsing the website after closing the privacy consent message with the closing cross
Special cases:
Visitors that are redirected by an internal redirect of the website (for example due to a language redirect on the landing page)
Mobile visitors who are redirected to the mobile app when arriving on the landing page in a mobile browser
Visits of bots like web crawlers. Common bot traffic is excluded but industry specific crawlers might increase "no choice" percentage
At the time of the first release of TrustCommander the no choice rate is expected to be close to your bounce rate. The metrics will then start to differ over the following time.
AB testing
The performance of privacy banner is crucial for the success of any data driven marketing activity. Therefore it is especially important to perform AB tests of your privacy banner to improve the user experience of your website visitors and to improve your consent KPIs. For AB tests it is common to set a goal to minimise the no choice and optout KPIs.
TrustCommander dashboard makes it very easy to compare metrics of two banners set up for AB test side by side by adding the AB test banners via the PRIVACY filter option.
Please contact your Commanders Act consultant in case you need support in setting up AB tests for your TrustCommander setup.
Last updated
