> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://knowledge.clym.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# GTM template for Clym integration


# This documentation outlines integrating Clym with Google Tag Manager (GTM) using the Clym GTM Template.

This template automatically handles Google Consent Mode v2 and optionally can install the Clym widget on the website.

Before you begin, please make sure you have:

* A working **Google Tag Manager** container installed on your site
* Access to the [Clym Control Center](https://www.auth.clym.io)

### 1. Import the GTM Template

###### Step 1: Open Your GTM Container

1. Go to [https://tagmanager.google.com/](https://tagmanager.google.com/) and open your container.
2. Navigate to the **Templates** section on the left sidebar.

###### Step 2: Import the CMP Template

1. Click on the “Search Gallery” button
2. Search for “Clym CMP” and click on it
3. Add to workspace

#### 2. Configure the CMP Template

###### Step 1: Create a Tag Using the Template

1. Go to **Tags** → **New**.
2. Click on **Tag Configuration** → Choose the **Clym CMP template.**
3. Configure the following fields:
    a.  If you would like to use our default settings, there is no need to change anything from the pre-configured settings
    b.  If you would like to change the default settings, please add new rows and set them based on your preferences for each region
    c.  Clym Widget ID: If you would like to install the Clym Widget through GTM, you can do so by filling out your widget ID.


You can copy your widget ID from the **Integrate** tab > **Platform tools** > **Widget** > **HTML**.
![Widget ID location](https://storage.crisp.chat/users/helpdesk/website/-/a/e/3/8/ae38f50f15c00000/cc-widgetid_gm1w87.png)


###### Step 2: Choose a Trigger

Please use a **Page View** or **Consent Initialization** trigger. We recommend using the **Consent Initialization** trigger for earliest execution.