N.Rich website tag installation


In order to support situations in which cookie consent is not available, N.Rich tag has two modes; cookieless and standard that uses cookies. When installing the tag, it’s most important that Standard mode works properly after consent has been given. Cookieless mode should always be supported in order to avoid losing a lot of valuable data.

Supporting the standard mode is simple and can be done by anybody with basic knowledge of tag managers. Supporting the cookieless mode requires understanding of the technical functionality of the Consent Management Platform used on the website as well as a thorough understanding of Javascript and concepts like cookies and the data layer. This guideline is meant for people with such understanding.


This is a draft instruction of how to install N.Rich website tag using the Google Tag Manager. The tag also could be installed directly, or via a tag manager tool using similar logic. It is essential to note that this guideline needs to be applied to the technical mechanics of the specific Consent Management System used on your website. This means, you need to apply the framwork laid out in this document to your specific technical setup.

N.Rich tag could be configured to be used in 2 ways:

  • Cookieless, means that the tag will skip all 3rd party syncs and will not generate any cookies

  • Standard mode, which is more functional, and should be used if cookie consent was granted, because it could provide much more analytics.

Both versions are practically the same tag, but with a different configuration section:

var config = { // it means standard version cookieless: false, };

Installation via tag manager (GTM)

Logic for tag installation is the following:

  1. Wait for Cookie consent management system initialization

  2. Pass cookie consent status to some variable

  3. Fire N.Rich website tag and configure it using a variable from the previous step

Same logic could be used in any other tag management system.

In GTM you can use the following steps:

  1. Go to “Variables“

  2. Click “New“ in “User-Defined Variables“

  3. Variable type is depends on your consent management system, but most probably it will be “
    Data Layer Variable

  4. Go to “Triggers“ and create a trigger for the N.RIch website tag. Tag should be fired after cookie consent initialization. Usually consent management systems provide some way to understand that consent status was initialized and you can create a custom event, to catch it and use as a trigger.

  5. Go to “Tags“ and create a new tag for the N.Rich. You need to choose “Custom HTML” type and paste code from the https://app.nrich.ai/setup to “HTML“ field. Code should be changed, to use a variable from (3) for standard vs cookieless configuration. You also need to choose a trigger from a (4) as a trigger for the tag. See screenshot as an example of a typical setup:

  6. here we are using ConsentGranted == 0 condition, to calculate cookieless status of the tag, so if ConsentGranted is 0 tag will be cookieless, and standard version in all other cases. You can use another logic, which is suitable in your particular case