.png?height=120&name=Primary%20Logo_3%20(1).png)
Configuring Google Tag Manager and Cookiebot for the N.Rich Tag Installation
Prerequisites: You use Google Tag Manager and the Cookiebot Consent Management Platform
In this guide we will go through the steps needed to configure Google Tag Manager and Cookiebot CMP in order to be able to install N.Rich Cookieless and Standard tags.
In case you have just set up Google Tag Manager, it is important to create a new trigger that will inform the tags you install (like N.Rich) whether or not a user visiting your site has given consent to cookies (and which kind of cookies did they consent to).
This article from Cookiebot does a good job at explaining how to go about setting this up.
Do you already have a trigger in Google Tag Manager tracking whether a visitor to your website has given marketing consent?
Then skip this guide entirely and return to the primary article.
Here, we'll do a slightly more beginner friendly version of the above article:
1. Start off by navigating to the correct container in Google Tag Manager and from the left-hand menu, choose Templates.
2. On the right-hand side, you will see a Search Gallery button under Variable Templates - click on it, give it a bit to load and then find and select "Cookiebot Consent State"
3. Once selected, choose Add to Workspace and confirm by clicking on the Add button. 
4. With the template added, we can now head to Variables from the left-hand menu, and under User-Defined Variables, choose New
5. Give the variable a name, for example "Cookie Consent" and click on the Lego-like brick icon in the center of the screen to choose a variable Cookiebot Consent State and click Save.
6. We have a Template and Variable ready, now, we get to leverage these to create a Trigger. From the left-hand menu, choose Triggers and New on the right-hand side.
7. Give your trigger a name, for example, "Marketing Consent Granted" and click on the icon in the center to begin setting up your trigger - from the list that appears on the right, choose Custom Event
8. Set the Event Name to cookie_consent_marketing
9. Set This trigger fires on: to Some Custom Events and from the first drop-down on the left, choose the Cookie Consent variable we have created earlier. Keep the middle dropdown to Contains and input marketing into the text box on the right: 
10. Finally, click Save.
Well done!
Your Google Tag Manager is now configured to pass whether or not your users have granted consent to your website via Usercentrics's Cookiebot - N.Rich can leverage this to determine when to load the Cookieless and Standard versions of our tag.
Return to the main article to complete the installation.