Assign Categories
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 TAGSsection of TrustCommander. - In the
EDITtab 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.
INCLUDE IN PRIVACY SCOPE
CATEGORY
VENDOR
BYPASS OPTOUT DEFAULT CONFIGURATION
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:
Other elements that can be managed by TrustCommander.
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). |
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.
Example: Assigning a Facebook tag to the SOCIAL NETWORKS 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.
Last modified 2yr ago