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.
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:
Options to generate and deploy banner.
TRUST > 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.
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.
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 TagCommander and TrustCommander 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.
Scenario
Affected TAG Container
All TAG Container
TRUST Banner
Global options change (TRUST > Options
)
Yes
Yes
Yes
Category or vendor is added, deleted or updated on a used banner
Yes
Yes
Yes
Tag is added to a container (TAG > Edition
)
Yes
No
No
Tag is assigned to a category or vendor in the used banner (TAG > Edition
or TRUST > Categories & Tags (Tab ASSIGN TAGS)
)
Yes
No
No
Banner text or style change
No
No
Yes
Banner button actions change
No
No
Yes
A list of available banner templates in TrustCommander
TrustCommander offers multiple banner templates for different kind of privacy workflows.
Options to create and edit banner templates.
TRUST > 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:
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 customised privacy banner templates. Please contact your Commanders Act consultant or support in case you are unsure if your banner was customised before using this option.
TRUST > Privacy banners (tab EDIT BANNER)
All banner templates can be customised 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 customisation 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 vendors
section. 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.
TrustCommander 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.).
Example to set the publisher country code field to a German country code:
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
TrustCommander 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.).
You can change the vendor button type to neutral if you choose the neutral position as the default status.
You can't choose a neutral position for IAB categories (purposes) as it's not allowed by the framework policy
You can choose to synchronise 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.
Beta
Only available for IAB TCF 2.0 banner.
Right now IAB TCF Stacks are in beta in TrustCommander. They are activated with a JavaScript command that needs to be added to the privacy center CUSTOM JS
field JS BLOCK BEFORE
.
TrustCommander 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 TrustCommander 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.
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.
Options to copy privacy banner with the Commanders Act copy management.
Admin > 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 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.
Choose one or multiple target sites where you want to copy the selected privacy banner with the Destination site(s)
dropdown.
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.
This will keep the content (text, selected color, etc.) of the banner and change the template.
This option might not work for customised privacy banner templates. Please contact your Commanders Act consultant or support in case you are unsure if your banner was customised before using this option.
Click COPY
in the top right corner of the interface to copy the banner with the selected options.
"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.
TrustCommander 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 .
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 customisable 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 centre of the page. This banner includes a text message and customisable 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 customisable buttons. It supports links to another page (e.g. privacy policy).
This template exists with and without an optional privacy center.
A variation of this template exists with extended accessibility support.
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).
Popin with categories
This template directly opens the privacy center that allows visitors to select TrustCommander privacy categories and sub-categories they want to activate/deactivate.
IAB TCF 1.1 Popin
A floating modal dialogue (pop-up), positioned in the centre of the page. This template offers consent controls following the IAB TCF 1.1 standard.
IAB TCF 1.1 Footer
Floating overlay banner, positioned at the bottom of the page. This template offers consent controls following the IAB TCF 1.1 standard.
IAB TCF 2.0 Popin
Template available if IAB TCF 2.0 option is activated in the TRUST > Options
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
Template available if IAB TCF 2.0 option is activated in the TRUST > Options
section.
Floating overlay banner, positioned at the bottom of the page. This template offers consent controls following the IABTCF 2.0 standard.
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 TRUST consent database.
Use the new privacy center
This option allows to use the old privacy center template of TrustCommander. 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 customised please check with your Commanders Act consultant or support contact before creating a new template. This option is not available on all templates.