# Google Tag Manager (GTM)
Commanders Act provides a GTM template to connect your existing GTM implementation to our serverside endpoint, in a secured environment.
{% hint style="info" %}
If you use GA4, you may be interested by the [GTM ultra quick setup](/getting-started/integrating-your-data/gtm-tutorial.md) allowing to forward events from GA4. It offers less flexibility but can be installed in 2 minutes.
{% endhint %}
## Setup
Summarizing all recommended steps:
1. Create a GTM source in Commanders Act
2. Add our template to your GTM implementation
3. Configure your tag
## Create a source in Commanders Act
In your Commanders Act dashboard:
* In the left pane menu, click on **Sources** > **Overview**.
* Click on the **Add source** button.
* In the catalog, search for the **Google Tag Manager** source and click on it.
* Click on **Configure** and set its name, environment and bound destinations.
* Once you're done, click on the **Create** button at the bottom.
* The source key will then be displayed:
* Copy its value and keep it for later!
{% hint style="info" %}
**Hint**: If you have already created a GTM source, you can retrieve its key by browsing to its **Settings** tab.
{% endhint %}
## Add our template to GTM
First, access [GTM](https://tagmanager.google.com/) and then add our template "**Commanders Act | Serverside events bridge**" from the Google "[Community Template Gallery](https://tagmanager.google.com/gallery/#/owners/TagCommander/templates/Serverside-events-bridge)" in your workspace, then select `(1)` "**Tags**".
Click on `(2)` the "**New**" button.
Click on `(3)` the "**Tag Configuration**" area.
Click `(4)` the **magnifying glass** in the upper right corner.
Search for `(5)` the "**Commanders Act | Serverside events bridge**" custom template and click on it to start the configuration.
## Configure your tag
Start by filling `(6)` **a name for your tag** in the upper left corner.
{% hint style="success" %}
**Hint**: you may want to name your tag adding the event name you're going to implement in the end. (E.g. "*Commanders Act |* Serverside events bridge *- **Purchase***")
{% endhint %}
Input your `(7)` "**Commanders Act Site ID**" and `(8)` "**Commanders Act Source Key**" (refer to the first section on how to create a source and retrieve its key).
Select `(9)` the "**Commanders Act Event**" from the drop-down menu, which is the event you want to forward.
Depending on which event you select more (or less) fields will be presented. In case you don't input a mandatory field the template will highlight the missing entry so you can provide a proper mapping.
The "**Event Fields**" section contains fields that define the event itself and are mostly mandatory or highly recommended.
Events including the "**Product Fields**" section require [an array structure for your product information](https://community.commandersact.com/tagcommander/tips-and-tricks/best-practices/common-datalayer-variables#product-arrays). The first field will always be the `(10)` **base array** where the information is stored and all subsequent fields are the related properties - E.g. you can map the information about `(11)` the "**Product Id**" by filling the property name.
In the "**User Fields**" section you can set `(12)` the "**User Id**" and `(13)` "**User Email**" - Either one of them is required if you select the "Purchase" event. The `(14)` "**User Consent Categories**" is a mandatory field holding an array with the user's consent category identifiers.
It's important to define and map all category identifiers with their respective names. For example, you may have the following array: *\[1,2,4]* and you defined the following relationship:
* 1 **➜** Advertising category
* 2 **➜** Analytics category
* 4 **➜** Functionality category
You also share with Commanders Act that the "Advertising category" must be enabled to activate the "Facebook CAPI." In this example, since the category identifier \[1] is included in the array we can activate the bridge and forward the event to Facebook.
{% hint style="info" %}
Ensure your category relationships are shared with Commanders Act.
{% endhint %}
{% hint style="warning" %}
Only with the agreed consent settings, we're allowed to bridge both the "Purchase" and "Refund" events to the "Facebook CAPI".
{% endhint %}
Complete your configuration by selecting the proper activation in the "Triggering" area / "Firing Triggers".
If you plan to setup [Facebook Conversion API](/features/destinations/destinations-catalog/facebook/facebook-conversions-api.md) through your GTM source, follow this extra step to update your Facebook Pixel tag:
{% content-ref url="/pages/2QXIPE4NknnWI8Dbjqg8" %}
[Facebook CAPI through GTM](/features/destinations/destinations-catalog/facebook/facebook-conversions-api/facebook-capi-through-gtm.md)
{% endcontent-ref %}
---
# 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://doc.commandersact.com/features/sources/sources-catalog/web/gtm.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.