> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.consentmo.com/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).

# Integration for Tags and Pixels added via GTM

Below you can find a guide on how you can integrate the **Social Media Pixels** in your store if they are added via the **Google Tag Manager container** as separate tags. 

||| First and foremost, you need to make sure that the Consentmo app is already integrated with the GTM container which is running in the store. At the moment you have two options for this which you can use to integrate the service with our app, which are listed below:

* [Google Consent Mode V2 Integration](/en/article/google-consent-mode-v2-integration-1olxp4x/)
* [How to set the Google Tag Manager template for Consentmo GDPR CMP](/en/article/how-to-set-the-google-tag-manager-template-for-consentmo-gdpr-cmp-zlmfpg/)

If you decide on adding other Pixels this way, here is the settings you need to make sure are set in the Pixel tag:

# Creating a Consentmo Trigger

 First, start by creating the Trigger: 

1. Click on the **Triggers** button on the left menu

2. Click on the **New** button > **Trigger Configuration** > **Custom Event**

3. In the field **Event name** write our app's event - `consent_status`

4. Make sure that **All Custom Events** is picked and click on the **Save **button to save the changes.

A reference on the process can be checked in the following video:

${youtube}[Creating Custom Trigger for GTM Tags -  Consentmo GDPR app](Aar7I6pJTTk)


# Additional Consent Checks

After creating the trigger you should setup the consent settings for each of your tags. In order to do that click on the **Tags **button located on the left menu and follow these instructions for all of the tags that require consent:

1.  Open the tag's settings.

2. Scroll down to the **Additional Consent Checks** option, pick **Require additional consent for tag to fire** and in the field below it, set the required consent. (e.g.  analytics_storage for Analytics services, ad_storage for marketing services, etc.).

3. After setting up the required consent, scroll down to the **Triggering** section, **click on the plus icon** and **choose the trigger** we created (in our case, the name of the trigger is Consentmo trigger).

4. Click on the **Save** button to save the changes.

A reference on the process can be checked in the following video: 

${youtube}[Additional Consent Checks for GTM tags - Consentmo GDPR app](cV299PHtUxg)

|| Note: Please make sure to use out trigger without the Consent Initialization or the Consent Initialization - All Pages set for the same tag as well:

![](https://storage.crisp.chat/users/helpdesk/website/-/b/0/7/f/b07f7406951a4000/triggers-in-gtm_8cpmqs.png)

By following the above steps you will make sure that the Tags/Pixels will only be fired once consent is given by the visitor via the Cookie bar from our app. 

In order to make sure everything is working in complete sync with the app and the store, do not forget to set the rest of your compliance by following the guide here as well:

* [Setting your store's compliance](/en/article/setting-your-stores-compliance-1tqs8pn/)

# Need help?

In need of any assistance with the setup, do not hesitate to drop us a line at support@consentmo.com or via our Live chat.