# TagCommander
TrustCommander and TagCommander are natively integrated with each other. This setup requires minimal technical knowledge and can be done entirely in the interface.
## Setup
Following you will find the required steps to implement a standard TrustCommander setup.
1. Choose the default account configuration mode for your account (see [Options](/trustcommander/user-guides/options.md#account-default-configuration)).
2. Setup your TrustCommander categories & vendors (see [Manage Categories](/trustcommander/user-guides/categories-and-tags/manage-categories.md)).
3. Assign your TrustCommander categories & vendors to your TagCommander tags (see [Assign Categories](/trustcommander/user-guides/categories-and-tags/assign-categories.md))
4. Create one or multiple banner templates (see [Manage Banner](/trustcommander/user-guides/privacy-banners/manage-banner.md))
5. Deploy your TrustCommander banner templates to the Commanders Act CDN or on premise target (see [Deploy Banner](/trustcommander/user-guides/privacy-banners/deploy-banner.md)).
6. Connect your privacy banner templates with TagCommander container and implement rules for which the banner should be played out (see below).
## Install TrustCommander banner with TagCommander container
To deploy a TrustCommander banner with TagCommander it needs to be linked to a container. TagCommander can then be use to implement detailed rules for which a TrustCommander banner is shown to visitors.
### Implement rules to show TrustCommander banner
`TAG > Tag Management > Edition (tab RULES)`
In TagCommander it is possible to provide exact conditions to decide when each of the linked privacy banners should be shown to visitors. Typical use cases consist of:
* Implement different banner for different languages or regions
* Avoid to deploy the banner on legal pages (privacy policy) so that users can read them before providing consent.
* Implement AB test for two banner designs.
You can create constrains under the `PRIVACY BANNERS` section to define under which conditions a privacy banner should be shown. Privacy banner constraint work the same way as tag constraints. Please reference constraints in the TagCommander documentation for more information.
{% hint style="info" %}
You have to first deploy a banner to the Commanders Act CDN or on premise location before being able to configure constraints (see [Deploy Banner](/trustcommander/user-guides/privacy-banners/deploy-banner.md#banner-deployment-options)).
{% endhint %}
### Link TrustCommander banner with TagCommander container
`TAG > Tag Management > Edition (tab GENERATE)`
TagCommander makes it easy to implement TustCommander banner on websites. To link a privacy banner with a TagCommander container it just has to be activated in the `GENERATE` tab with the `ACTIVATION` checkbox. This installs the selected privacy banner in the generated container version.
{% hint style="info" %}
You have to first deploy a banner to the Commanders Act CDN or on premise location before boing able to link it (see [Deploy Banner](/trustcommander/user-guides/privacy-banners/deploy-banner.md#banner-deployment-options)).
{% endhint %}
{% hint style="warning" %}
All containers of your website should be re-generated and deployed when installing a new privacy banner.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://community.commandersact.com/trustcommander/setup-guides/tag-manager/tagcommander.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.