CookieYes, Google Tag manager and the N.Rich tag

Last updated: July 6, 2026

This guide walks you through creating a consent trigger in GTM using CookieYes. Once the trigger is in place, the N.Rich Standard tag will know exactly when a visitor has granted marketing consent — and activate accordingly.

Prerequisites: You have Google Tag Manager installed on your website and you use CookieYes as your Consent Management Platform. If you're not sure which CMP you use, see Pre-check: do you use cookies — and which CMP?

CookieYes has a detailed guide of their own on setting this up — Block third-party cookies with Google Tag Manager and CookieYes. The steps below follow the same approach in a more beginner-friendly format.

Step 1: Create a variable

  1. In GTM, go to Variables and click New under User-Defined Variables.

  2. Give it a name — for example, Cookie Consent.

  3. Click the brick icon and select 1st Party Cookie as the variable type.

  4. In the Cookie Name field, enter cookieyes-consent.

  5. Click Save.

Step 2: Create a consent trigger

  1. From the left-hand menu, go to Triggers and click New.

  2. Give it a name — for example, Marketing Consent Granted.

  3. Click the trigger type icon and choose Custom Event.

  4. Set This trigger fires on to Some Custom Events.

  5. In the condition row, select the Cookie Consent variable, set the middle dropdown to contains, and enter analytics:yes in the text field.

  6. Click Save.

GTM is now configured to detect when CookieYes passes a marketing consent signal. The N.Rich Standard tag will use this trigger to know when to activate.

What's next

Your CookieYes consent trigger is ready. Head back to Activating Standard mode (cookie consent) to add the Standard tag and complete the setup.

Need help? Reach out via the chat in the bottom-left corner of the N.Rich platform - our support team is happy to walk you through it.