Management of TrustCommander privacy vendors.
TRUST> Categories & Tags (tab MANAGE VENDORS)
In this section you can manage your TrustCommander privacy vendors. These vendors will be used by your privacy center to provide users with detailed privacy management options.
To enable native vendors go to TRUST > Options and activate the custom vendors option.
Click ADD VENDOR to add vendors to your TrustCommander installation. You can select vendors available on TagCommander (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 TrustCommander 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.
It is possible to map vendors to multiple categories for stand-alone installation of TrustCommander. Tags in TagCommander can only be mapped to one category and vendor.
It is necessary to generate and deploy new version of privacy banners to deploy updates in the vendor section.
TrustCommander is compliant with IAB TCF 2.0 (Link to official listing). To enable IAB vendors go to TRUST > Options and activate the IAB option.
Click ADD IAB TCF 2.0 VENDORS to manage the IAB vendors with your TrustCommander installation. You can either select all vendors or select specific vendors that are relevant for your setup.
The description of IAB TCF 2.0 vendors is automatically loaded from the IAB TCF 2.0 framework.
TrustCommander 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 TRUST > Options 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 TrustCommander installation. Each vendor has to be mapped to a TrustCommander category.
Descriptions for the ATP that are shown in the TrustCommander privacy center are automatically loaded from the Google ACM list.
Google ACM vendor management only works with IAB TCF 2.0 banner templates.
Management of TrustCommander privacy categories.
TRUST> Categories & Tags (tab MANAGE CATEGORIES)
In this section you can manage your TrustCommander privacy categories and sub-categories. These categories will be used by your privacy center to provide users with detailed privacy management options.
Each TrustCommander privacy category has following options:
In case you use TrustCommander with TagCommander you can select a default category with a dropdown on the top left of the interface. New tags in TagCommander 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.
TrustCommander supports up to 10 categories.
You can edit a TrustCommander category by pressing the pencil icon to the right of the category.
You can delete TrustCommander categories by pressing the x icon to the right of the category.
You need to regenerate your privacy banners after adjusting privacy categories. In case you install TrustCommander with TagCommander you will also need to regenerate your TagCommander container so that your tags have access to the updated categories.
TrustCommander is compliant with IAB TCF 2.0 (Link to official listing). To enable IAB categories go to TRUST > Options and activate the IAB option.
TrustCommander is compliant with IAB TCF 2.0 (Link to official listing) and can use predefined IAB TCF purposes instead of manually configuring categories. Go to TRUST > Options tab to activate IAB TCF 2.0 option for your account.
IAB TCF 2.0 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.0 categories is automatically loaded from the IAB TCF 2.0 framework.
Assign TagCommander tags to TrustCommander categories.
TRUST > Categories & Tags (tab ASSIGN TAGS)
TagCommander tags can be assigned to TrustCommander categories & vendors in following locations.
In ASSIGN TAGS section of TrustCommander.
In the EDIT tab of TagCommander.
This section is only available in case you use TrustCommander with TagCommander.
Categories & vendors are managed per TagCommander container. You can select a TagCommander container in the left column. Then you can manage following TrustCommander setting per tag on the right side of the interface.
This option enables TrustCommander 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 TrustCommander category to each tag. This allows visitors to block tags by deactivating the related categories in the privacy center.
You can assign one TrustCommander 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 TrustCommander. e.g. TrustCommander 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 TrustCommander 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 TrustCommander categories & vendors inside the Edit tab of TagCommander. 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.0 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 TrustCommander to manage them directly with TagCommander.
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.
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.
Element
Description
EVENTS
TagCommander events that are implemented with the deprecated tc_events_xxx functions (events are now handled with TagCommander Trigger and therefore managed with normal tags).
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).
