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.
Options to create and edit banner templates.
Last updated
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.
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.
Changes have to be saved with the SAVE
button.
Option to manage the publisherCC
field of the IAB TCF API.
Country code 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 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.
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 IAB TCF Policy.
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.
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.
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.