Options to manage the main text content of your banner.
Content: Text content (supports HTML formatting and links).
Font color: Text color.
Background color: Background color of the content area.
In this section, you will find information about Consent configuration on Platform Commanders Act
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Management of Commanders Act Consent vendors.
Data Governance > Consent Management > Vendors
In this section you can manage your Commanders Act Consent vendors. These vendors will be used by your privacy center to provide users with detailed privacy management options.
To enable native vendors go to Data Governance > Consent Management > Settings and activate the custom vendors option.
For customers still using the v1.0 privacy center template (deprecated as of 2019) Vendor activation will automatically upgrade your privacy center to version 2.0.
Click ADD VENDOR to add vendors to your Commanders Act Consent installation. You can select vendors available on Commanders Act TMS (Predefined Vendors) or add custom vendors (Custom Vendor) by selecting the respective tab. A Commanders Act vendor is available by default.
Each vendor can be mapped to Consent categories with the respective dropdown. This allows users to provide consent to all vendors of a category at once in the privacy center. A PEN icon allows to edit information of the vendor that is displayed in the privacy center. Following fields are available per vendor. A TRASH icon allows to remove the vendor.
Option
Description
Name
Name of the vendor. Privacy centers will display this name.
ID
ID of the vendor. This ID is used in raw data exports and for technical setup of certain functionalities. It is possible to manually provide an ID. In case the field is left empty a category ID will be assigned automatically.
Description
Description of the vendor. Privacy centers use this description as the default description for this vendor in case no localisation was provided in the banner editor.
Policy URL
Privacy Policy Link of the vendor. Privacy centers display this URL for each vendor.
It is possible to map vendors to multiple categories for stand-alone installation of Commanders Act Consent. Tags in your Web Container can only be mapped to one category and vendor.
It is necessary to generate and deploy new version of Consent banners to deploy updates in the vendor section.
Commanders Act is compliant with IAB TCF 2.2 (Link to official listing). To enable IAB vendors go to Data Governance > Consent Management > Settings and activate the IAB option.
Click ADD IAB TCF 2.2 VENDORS to manage the IAB vendors with your Commanders Act Consent installation. You can either select all vendors or select specific vendors that are relevant for your setup.
The description of IAB TCF 2.2 vendors is automatically loaded from the IAB TCF 2.2 framework.
Commanders Act Consent will automatically configures purposes, special purposes, features and special features in the CATEGORIES tab depending on the selected vendors.
To enable Google ACM vendors go to Data Governance > Consent Management > Settings and activate the IAB option and the Google ACM vendors.
Google Additional Consent Mode (ACM) allows to manage consent for Google Ad Technology Providers (ATP) (that are not part of the IAB TCF Global Vendors List) alongside IAB TCF vendors.
Add Google ACM vendor allows to add Google ACM vendors to add a Google ATP to your Commanders Act Consent installation. Each vendor has to be mapped to a TrustCommander category.
Descriptions for the ATP that are shown in the Consent banner (into the privacy center) are automatically loaded from the Google ACM list.
Google ACM vendor management only works with IAB TCF 2.0 & 2.2 banner templates.
Here are the articles in this section:
A list of available banner templates in Commanders Act Consent
Commanders Act offers multiple banner templates for different kind of privacy workflows.
Template
Description
Header (with Privacy Center)
Floating overlay banner (is layered on top of the website), positioned at the top of the page. This banner includes a text message and customizables buttons. You can add a link to another page (e.g. privacy policy).
This template exists with and without an optional privacy center.
Popin (with Privacy Center)
A floating modal dialogue (pop-up), positioned in the center of the page. This banner includes a text message and customizable buttons. It supports links to another page (e.g. privacy policy).
This template exists with and without an optional privacy center.
Footer (with Privacy Center)
Floating overlay banner, positioned at the bottom of the page. This banner includes a text message and customizable buttons. It supports links to another page (e.g. privacy policy).
A variation of this template exists with extended accessibility support.
Popin with categories
This template directly opens the privacy center that allows visitors to select Commanders Act Consent categories and sub-categories they want to activate/deactivate.
Footer / Popin / Header
Floating information banner, no buttons to refuse or accept. Not compliant for GDPR & CCPA
Footer without button
Floating overlay banner, positioned at the bottom of the page. This banner includes a text message and cross icon to close the banner. It supports links to another page (e.g. privacy policy). Not compliant for GDPR & CCPA
IAB TCF 2.2 Popin
Template available if IAB TCF compliancy option is activated in the Data Governance > Consent Management > Settings section.
A floating modal dialogue (pop-up), positioned in the centre of the page. This template offers consent controls following the IAB TCF 2.2 standard.
IAB TCF 2.2 Footer
Template available if IAB TCF compliancy option is activated in the Data Governance > Consent Management > Settings section.
Floating overlay banner, positioned at the bottom of the page. This template offers consent controls following the IABTCF 2.2 standard.
IAB TCF 2.0 Popin (deprecated)
Template available if IAB TCF 2.0 option is activated in the Data Governance > Consent Management > Settings section.
A floating modal dialogue (pop-up), positioned in the centre of the page. This template offers consent controls following the IAB TCF 2.0 standard.
IAB TCF 2.0 Footer (deprecated)
Template available if IAB TCF compliancy option is activated in the Data Governance > Consent Management > Settings section.
Floating overlay banner, positioned at the bottom of the page. This template offers consent controls following the IABTCF 2.0 standard.
Footer with privacy center (accessibility)
Floating overlay banner, positioned at the bottom of the page. This banner includes a text message and customizable buttons. It supports links to another page (e.g. privacy policy). Includes standards for WCAG 2.0 for more details, look at
Popin with privacy center (accessibility)
A floating modal dialogue (pop-up), positioned in the center of the page.This banner includes a text message and customizable buttons. It supports links to another page (e.g. privacy policy). Includes standards for WCAG 2.0 for more details, look at
Among the available templates, one is dedicated to accessibility. It ensures compatibility with RGAA and WCAG 2.0 level AA standards.
Web Content Accessibility Guidelines (WCAG) is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a single shared standard for web content accessibility that meets the needs of individuals, organizations, and governments internationally.
More information here : https://www.w3.org/WAI/standards-guidelines/wcag/
When websites and web tools are properly designed and coded, people with disabilities can use them. However, currently many sites and tools are developed with accessibility barriers that make them difficult or impossible for some people to use.
Making the web accessible benefits individuals, businesses, and society. International web standards define what is needed for accessibility.
Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. More specifically, people can:
perceive, understand, navigate, and interact with the Web
contribute to the Web
With this template the main key point is to offer a privacy fully functional for people with disabilities.
The Accessibility template provides an automatic translation of different labels. This translation is based on navigator language. Currently, it supports : Italian, English, German, French and Russian.
Banners
You can either add new translation or override aria labels by using the function tC.privacy.addTranslation() in the custom JS.
Labels available :
iframeTitle : Title attribute of the iframe
privacyLabel : Aria Label of the footer
acceptAria : Aria Label of the accept button
refuseAria : Aria Label of the refuse button
showPcAria : Aria Label of the “Show Privacy Center“ Button
Exemple :
Privacy Center
⚠️ To translate the privacy you must use another function: pc.addTranslation()
Available keys and their values :
Some of the translation accept a label as {label}. The label here is always the label of the category.
The last keys with SrPrefix/SrSuffix have empty translation by default. These keys are used for “sr-only” text which are prefixing and suffixing the category name. These text are only readable by a screen reader.
cookieSr are used when the category isn’t locked
cookieAlwaysOnSr replaces cookieSr if the category is blocked to on
Example:
By default, texts provided to screen readers is translated depending on the navigator language. In some case you may want to display a privacy in english for example even if the navigator language is another one. ie : with an ISO language code in the url
You can force the privacy to take a language by using the function setLocale in the Privacy Center > Custom JS field > JS Block Before :
Value can be : fr, it, de, ru or en
Note : this function must be placed after the translation declaration.
The focus trap is an accessibility option designed so that keyboard user have their navigation locked to the banner. Pressing the TAB key would cycle between the different navigation elements of the banner without going on your website. This is an accessibility recommendation when using modal on a webpage.
You can deactivate the focus trap by adding the following JavaScript snippet to the custom JS of the accessibility template banner:
Assign Web Container tags to Consent categories.
Data Governance > Consent Management > Categories (tab ASSIGN TAGS)
Commanders Act TMS tags can be assigned to Consent categories & vendors in following locations.
In ASSIGN TAGS tab of Data Governance > Consent Management > Categories.
In the EDIT tab of TMS Commanders Act.
This section is only available in case you use Commanders Act Consent with TMS Commanders Act (Web Container).
Categories & Vendors are managed separately for each web container. You can select a Web Commander container in the left column. Then you can manage following Consent setting per tag on the right side of the interface.
This option enables Commanders Act Consent to block a tag depending on a visitors privacy setting.
It is possible to activate or deactivate this setting for all tags via the all and none buttons on top of the column.
You can assign one Consent category to each tag. This allows visitors to block tags by deactivating the related categories in the privacy center.
You can assign one Consent vendor to each tag. This allows visitors to block tags by deactivating the related vendor in the privacy center.
This option allows you to bypass the default behaviour of tags that are managed with Commanders Act Consent. e.g. Consent will blocks tags that are included in the privacy scope until a visitor provides his consent in case the default account configuration is set to Optout. Bypassing this option would allow you to therefore load tags before the visitor provided his privacy settings (e.g. on the first page). In case such tags are included in the privacy scope they can still be deactivated by the user depending on his privacy settings.
It is possible to activate or deactivate this setting for all tags via the all and none buttons on top of the column.
Additionally you can also manage these Consent settings for following elements:
Containers have to be re-generated and deployed to apply these changes.
For convenience it is also possible to directly assign Commanders Act Consent categories & vendors inside the Edit tab of TMS Commanders Act (Web Containers). Assigning a category & vendor also includes the tag in the privacy scope.
In case a new vendor is added to the account the tag will not be fired when a user provided an optin for the corresponding category. Therefore it is necessary to activate the "Re-activate privacy" option during the generation of a new banner version to re-ask consent. The option "Don't re-ask the consent to trigger this tag" will change this default behaviour so that the vendor will receive an automatic optin based on the corresponding category.
In case you choose to manage tags with IAB 2.2 you do not need to assign IAB compliant tags in the category assignation tab. IAB compliant tags are automatically controlled by the IAB framework.
It is still possible to assign tags to categories to allow Commanders Act Consent to manage them directly with TMS Commanders Act.
Administration > Copy management
Commanders Act copy management allows to copy privacy banner. Privacy banners can be copied within the same account or transferred to another account.
Steps to copy a banner with copy management.
Select Privacy banner(s) in the Elements to copy dropdown.
Use the Site containing the privacy banner(s) to copy dropdown menu to select the site where the privacy banner is located that you want to copy.
Select one or more privacy banner that you would like to copy in the Privacy banner(s) to copy dropdown menu.
Choose one or multiple target sites where you want to copy the selected privacy banner with the Destination site(s) dropdown menu.
You can copy your privacy banner to a new template by selecting Yes in the Copy the privacy content to a new template option.
After this you will be able to select the new template in the Destination template dropdown menu.
This will keep the content (text, selected color, etc.) of the banner and change the template.
This option might not work for customized privacy banner templates. Please contact your Commanders Act consultant or support in case you are unsure if your banner was customized before using this option.
Click on blue buttonCOPY at the top right corner of the interface to copy the banner with the selected options.
Options to create and edit banner templates.Sources > Privacy banners
Click ADD PRIVACY BANNER in the top right of the interface to add a new banner to your account. Each template has following options:
Example: Configuring options of a privacy banner.
You can open and edit the privacy banner settings via the gear icon on the top left of the interface.
Changing banner templates might not work for customized privacy banner templates. Please contact your Commanders Act consultant or support in case you are unsure if your banner was customized before using this option.
Sources > Privacy banners (tab EDIT BANNER)
All banner templates can be customized with a WYSIWYG editor. Following options are available for all banners (except IAB TCF and Popin with Categories templates).
Options to manage the main text content of your banner.
Content: Text content (supports HTML formatting and links).
Font color: Text color.
Background color: Background color of the content area.
Custom CSS that can be used by advanced users to customise the banner style. This CSS is applied globally to your website, avoid to use global selectors and use the HTML ID attribute of the banner elements instead.
Advanced customization options. Please contact your Commanders Act consultant or support before using these.
Changes have to be saved with the SAVE button.
Following options are available for the privacy center and "Popin with categories" templates.
Options to manage the header text of your privacy center.
Title: Text content.
Font color: Text color.
Background color: Background color of the header area.
Options to manage the main text content of your banner.
Categories introduction: Introductory text of the category tab (supports HTML formatting and links)
Vendors introduction: Introductory text of the vendor tab (supports HTML formatting and links, only visible in case IAB TCF 2.0 or custom vendors were activated)
Font color: Text color.
Background color: Background color of the content area.
Options to manage the privacy categories of the privacy center. These categories are based on the categories managed in the Categories & Tags part of the interface.
Order: Drag and Drop sorting of Categories.
edit icon that allows to overwrite the default name and description of categories and sub-categories that have been provided in the
Categories & Tags section of the interface for this banner (used for localisation).
Checkbox that allows to hide a category (below edit icon).
Categories Blocked On: Checkbox that permanently enables a category that can not be deactivated by visitors (e.g. for an "essential cookies" category)
IAB TCF 2.0 option: IAB purposes, special purposes, features and special features are automatically displayed on the basis of selected vendors in Categories & Tags / Manage vendorssection. The categories translation is done automatically depending on the user’s browser language settings. Non-IAB categories will be displayed after the official IAB categories in the banner.
Options to manage and translate descriptions of custom vendors. IAB TCF 2.0 vendor descriptions and translations are managed automatically by the IAB TCF 2.0 framework.
Vendor Description: Description displayed in the vendor tab.
Hide Vendor: Options to hide the vendor from the banner.
Order of vendors can be changed via drag & drop. (IAB TCF 2.0 vendors are always displayed before custom vendors).
Custom CSS that can be used by advanced users to customise the banner style.
Advanced customisation options. Please contact your Commanders Act consultant or support before using these.
Changes have to be saved with the SAVE button.
Option to manage the publisherCC field of the IAB TCF API.
Consent banners sets this value to "FR" by default in the IAB response. The publisher country code field can be customised with following JavaScript snippet (should be implemented in the first container on the website.).
tC.privacy.iabPublisherCC = "<country_code>";
Example to set the publisher country code field to a German country code:
tC.privacy.iabPublisherCC = "DE";
Option to manage the purposeOneTreatment field of the IAB TCF API.
IAB TCF offers this field to specify how purpose one should be treated in specific scenarios.
true: Purpose 1 not disclosed at all. CMPs use publisherCC to indicate the publisher's country of establishment to help Vendors determine whether the vendor requires Purpose 1 consent.
false: There is no special Purpose 1 treatment status. Purpose 1 was disclosed normally (consent) as expected by TCF Policy
Consent banner sets this value to false by default in the IAB response. The purpose one treatment field can be customised with following JavaScript snippet (should be implemented in the first container on the website.).
tC.privacy.iabPublisherCC = (true|false);
You can change the vendor button type to neutral if you choose the neutral position as the default status.f
You can't choose a neutral position for IAB categories (purposes) as it's not allowed by the framework policy
You can choose to synchronize vendors status with categories, choosing to do it only for neutral buttons or always. If you use an IAB TCF template, this option will not have any effects on TCF vendors, as the TCF framework doesn't allow this.
BetaRight now IAB TCF Stacks are in beta in Commanders Act Consent. They are activated with a JavaScript command that needs to be added to the privacy center CUSTOM JS field JS BLOCK BEFORE.Example: Activating Auto Stacks
Commanders Act Consent offers two options to activate Stacks:
This option uses an algorithm to automatically find the tightest Stack combination for the configured vendors. This option is the recommended approach.
Purposes may only be included in one Stack. In case of a bad configuration Commanders Act Consent ignores IAB Stack configuration and provides an error in the browser console.
Per default IAB Purpose controls are placed above native category controls. It is possible to display native categories above IAB TCF Purpose controls by adding following JavaScript snippet to the CUSTOM JS field JS BLOCK BEFORE of the privacy center.
pc.tc.categoriesSectionTop(true);
The "Other" headline of the native category controls can be translated by adding following configuration snippet to the CUSTOM JS field JS BLOCK BEFORE of the privacy center.
pc.addTranslation({en: { others: 'My Headline' }});pc.setLocale('en');
The Commanders Act Consent Analysis dashboard provides insights into critical KPIs of your consent management setup.
The dashboard provides KPIs for each individual Commanders Act Consent banner. You can customize the dashboard by adjusting filter settings at the top left of the interface. Commanders Act Consent Analysis provides the following filters:
Configures which privacy banners are displayed in the dashboard table.
Allows to filter dashboard metrics for typical device types. Depending on the browser settings of your website visitors, device recognition might not be 100% accurate.
Allows to filter dashboard metrics for data inside and outside the EU.
Now the top 10 banners that have at least 1,000 views are displayed. To view other banners, use the PRIVACY selection menu
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.
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 "Data Governance > Consent Management > Settings" page).
Commanders Act Consent Analysis measures privacy banner interactions to calculate consent KPIs.
All metrics are visitor/ traffic based and not user based. Commanders Act Consent Banner 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. Commanders Act identifies visitors as new visitors in case they delete this cookie.
To understand dashboard metrics it is important to understand how Commanders Act Consent Analysis 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).
An optout action occurs when a visitor...
clicks the reject button of the privacy banner.
saves the privacy center with all categories off.
Following examples outline a hypothetical scenario with only one website visitor to explain the measurement approach:
A new visitor arrives at a website with a Commanders Act Consent 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. Commanders Act Consent Analysis 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%.
A new visitor arrives at a website with a Commanders Act Consent 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 Commanders Act Consent banners templates. In case of a banner customization or custom workflow, part of the metrics might have a different meaning.
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.
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.
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 Commanders Act Consent Analysis 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 Commanders Act Consent Analysis the no choice rate is expected to be close to your bounce rate. The metrics will then start to differ over the following time.
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.
Commanders Act Consent Analysis 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 Commanders Act Consent setup.
Options to generate and deploy banner.
Sources > Privacy banners ( tab GENERATE & DEPLOY)
To deploy a new or updated banner it is first necessary to generate a new version of the banner. Click GENERATE to open the modal dialogue.
You will have following option when generating a new container version.
You can preview and test new banner versions by clicking the TEST option on the right site of the banner version in the banner version list. This will preview the banner on a demo website.
It is recommended to test new banner on a test environment of the real website before deploying it.
The deployment process of a new banner version varies depending on the selected hosting method of the privacy banner. You can select the hosting method of a banner in the privacy banner settings that can be accessed with the gear icon on the top left of the interface (beside the privacy banner name).
Commanders Act CDN ensures a reliable and performant hosting of your banner. It allows to deploy banners automatically and in real-time.
Click DEPLOY to deploy a banner to the Commanders Act CDN.
This option allows to self-host privacy banner. It therefore requires manual effort on each update. For on premise hosting it is necessary to provide the URL of the folder where the on premise banner is hosted. Example:
http(s)://www.mydomain.com/myfolder/
Click DOWNLOAD to download on the right side of the new banner files and manually update them on your server.
In case both TMS and Consent Commanders Act are used to manage tags it is important to understand what needs to be generated and deployed for different update scenarios. Following table lists the elements that needs a generation and deployment for common scenarios.
On your website, don't forget to integrate a button or a link to allow your users to modify their consent choices
"Neutral position": The default status of vendors is "Undecided". When a new visitor accepts consent categories in the privacy center for the first time the vendors activate based on their linked categories (see ).
of the country that determines the legislation of reference. Normally corresponds to the country code of the country in which the publisher's business entity is established.
Commanders Act Consent offers IAB TCF Stacks to reduce the size of the purpose list in the privacy center. IAB TCF Stacks group purposes and special features in a foldable panel and allows visitors to configure consent for all purposes and special feature in a Stack at once. More information on IAB TCF Stacks can be found in the .
This option allows to manually activate IAB TCF Stacks by providing a list of Stack IDs. The Stack IDs can be found in the .
Use our Onsite API, command
Element
Description
COMMANDERS ACT HITS
Commanders Act related hits that are initiated from the container (this includes hits for functionalities like tag deduplication, tag hierarchy, and other). A separate category is available for the cookie sync option. This setting is synced between all client-side TagCommander container.
STATIC AND DYNAMIC JAVASCRIPT CODE
Custom JavaScript that can be implemented in TagCommander container (found in ADVANCED section of the Edit tab).
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.
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.
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.
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.
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.
Option
Description
Comment
You can provide a comment to document the changes of the new banner version (e.g. change text of accept button).
Reactivate privacy
In case you check this option all visitors of the website will be re-asked for consent, they will again see the banner when visiting the website the next time.
Scenario
Affected Web Container
All Web Container
Consent Banner
Global options change (Data Governance > Consent Management > Settings)
Yes
Yes
Yes
Category or vendor is added, deleted or updated on a used banner
Yes
Yes
Yes
Tag is added to a container (Source > Web Containers)
Yes
No
No
Tag is assigned to a category or vendor in the used banner (Data Governance > Consent Management > Categories (Tab ASSIGN TAGS))
Yes
No
No
Banner text or style change
No
No
Yes
Banner button actions change
No
No
Yes
Field
Description
Name
Label of the banner used in the interface.
Template
Dropdown to select a template for this banner.
Hosting
Hosting method used for this banner (see Deploy Banner).
Consent duration
Duration how long the consent cookie is valid. After this duration the consent cookie is not valid anymore and a new banner will be presented to the user. It is possible to configure a duration in full months between 1 and 13 month. This has no impact on the storage duration of the consent in the Commanders Act Consent database.
Use the new privacy center
This option allows to use the old privacy center template of Commanders Act Consent Banners. This option allows to use custom CSS and custom JS that was created for old banner templates. In case you are not sure if a banner was customized please check with your Commanders Act consultant or support contact before creating a new template. This option is not available on all templates.
You can export the raw consent data in the Options menu.
You can download consent data once, or schedule a recurrent export, by email or FTP.
The export includes the following fields:
Field
Description
id_hit
ID of the hit (autoincrement id)
id_tagcommander
ID of the TagCommander container that installed the privacy banner that initiated the consent hit.
id_privacy
ID of the privacy banner that initiated the consent hit.
version
Version of the privacy banner at the time the consent hit was initiated.
cookie
Consent categories that were accepted in the privacy center.
tcpid
cookie ID of the consent (hashed).
date_hit
Timestamp of the consent hit.
privacy_action
Action that initiated the hit.
V: View of the banner
1: Opt-In click
0: Opt-out click
-1: User refused all consent (only on deprecated version 1.0)
type_action
Type of action that generated the hit.
Ex of possible values:
banner : click in the banner
pc : action in the privacy center
device
device type identifier (1=phone, 2=tablet, 3=desktop, 0=other)
In case vendors are activated for the account, it is possible to include vendor optins in the export by switching the "Include Vendors in Export" toggle. This will increase export size considerably.
IP address is not stored
The option "Consent storage duration in database" allows to set a duration (in month) the consent data is stored in the consent database (which is used to prove consent). Be careful when changing the setting to not lose old consents by accident! You will be shown a prompt after changing the value to confirm the new duration. The maximum storage duration is 13 months. In case you need a longer storage duration, please contact your Commanders Act support or consultant.
Data Governance > Consent Management > Categories
In this section you can manage your Commanders Act Consent categories and sub-categories. These categories will be used by your privacy center to provide users with detailed privacy management options.
Each Commanders Act Consent category has following options:
In case you use Consent module with TMS Web Container you can select a default category with a drop down on the top left of the interface. New tags in TMS client-side will automatically receive the default category as their privacy category. The default category has a * in the category list.
To add a new category press ADD CATEGORY on the the top right of the interface.
You can edit a Consent category by pressing the pencil icon to the right of the category.
You can delete Consent categories by pressing the x icon to the right of the category.
You need to regenerate your consent banners after adjusting pconsent categories. In case you install Consent module with TMS Web Container you will also need to regenerate your Web Container so that your tags have access to the updated categories.
IAB TCF 2.2 purposes, special purposes, features and special features are automatically added to the CATEGORIES tab depending the vendors you add in the MANAGE VENDORS tab. You can still add custom categories that you can use side by side with the predefined IAB categories.
The description of IAB TCF 2.2 categories is automatically loaded from the IAB TCF 2.2 framework.
Data Governance > Consent Management > Settings.
Only administrators can view and change these account configurations.
This setting allows you to handle how tags should be handled in case no consent was yet provided by a user.
Your tags are not loaded when a user visits your site. They will be fired when the user continues browsing, unless they refuse cookies beforehand.
With the General Data Protection Regulation (GDPR), this is the default setting you should choose.
Your tags are loaded when a user visits your site. They are only disabled if the user explicitly refuses cookies.
This setting is not compatible with the General Data Protection Regulation (GDPR).
By default, accounts are configured in optout mode since it is the most popular and is GDPR compliant.
This option enables the IAB TCF 2.0 framework for your account. This will enable IAB TCF 2.0 banner, categories and vendors.
This option activates vendors. This will enable vendor management options in the Categories & Tags section and enables a vendor management screen in your privacy centers that allows users to manage consent per vendor (requires re-deployment or banners).
This option allows to select country codes (e.g. fr for French) that are used to localise the cookie notice of the cookie scanner feature. It is possible to add default country codes by clicking in the white area and selecting a country code from the dropdown. Additionally custom country codes can be added by clicking in the white area and typing the custom country code. The custom country code is saved after pressing Enter.
It is recommended to use the default country codes listed in the auto-complete dropdown. This allows to localise the cookie notice based on language settings of browsers.
These settings allow you to modify the default name, separator and subdomain of your privacy cookie.
Changing the cookie name, separator or subdomain can have unwanted side-effects depending on your Commanders Act consent setup. Please contact your Commanders Act consultant or support before applying changes.
Commanders Act Consent module is compliant with IAB TCF 2.2 (). To enable IAB categories go to Data Governance > Consent Management > Settings and activate the IAB option.
You can also have a look on
Commanders Act Consent module is compliant with IAB TCF 2.2 () and can use predefined IAB TCF purposes instead of manually configuring categories. Go to Data Governance > Consent Management > Settings tab to activate IAB TCF 2.2 option for your account.
This option enables the (ACM) for Google Ad Technology Providers (ATP) for your account. This will enable Google ACM vendor management in the Categories & Tags section and extends the IAB TCF API according to the ACM specification.
See dedicated documentation .
Option
Description
Name
Name of the category (e.g. "Analytics", "Advertising", etc.). Privacy centers use this name as the default label for this category in case no localisation was provided in the banner editor.
ID
ID of the category. This ID is used in raw data exports and for technical setup of certain functionalities. It is possible to manually provide an ID. In case the field is left empty a category ID will be assigned automatically.
Description
Description of the category. Privacy centers use this description as the default description for this category in case no localisation was provided in the banner editor.
Sub-categories
It is possible to provide sub-categories for each category (e.g. "Universal Analytics", "Matomo", etc. for an "Analytics" category). Each sub-category has a name and an ID. Privacy center use this name as the default label for this sub-category in case no localisation was provided in the banner editor. The ID is used in raw data exports and for technical setup of certain functionalities. It is possible to manually provide an ID. In case the field is left empty a sub-category ID will be assigned automatically.
