The N.Rich Tag

The entry point into the world of the N.Rich tag/pixel - how to install and configure it in order to get the most value out of the N.Rich platform

This article requires a little technical knowledge to understand.

The N.Rich tag or pixel is a piece of source code that, once added to your website pages, allows N.Rich to track visits to your website, monitor engagement, match clicks coming from our advertising platform to real users browsing your website and ultimately, help drive your account based marketing efforts to the next level.

In case you or your legal team need to do preform due diligence prior to installing a tracking tag and cookie into your website, here you can find our legitimate interest assessment sheet, our data privacy approach as well as our privacy notice.

In case you have an engineering team / webmaster / external agency responsible for building and maintaining your website, or you are comfortable with installing pixels onto your website and navigating your consent management platform, stop here and leverage this link instead: Technical Guide

If you are responsible for maintaining your own website and tech is not your strong-suite, continue following this guide - we'll do our best to guide you through this process step-by-step.

In order to get started, it is important to understand what set of tools you use to run your website, as well as any landing pages from which you wish to use in advertising. Any web page from which N.Rich should be able to extract engagement data from must have the N.Rich tag installed on it. If all of your landing pages are hosted on the same platform, then installing the tag there will suffice. In case you use additional tools to power your landing pages, you may need to install the N.Rich tag into multiple platforms.

Tip: Not sure if both your landing pages and marketing pages are on the same platform? See this link on how to find out - How do I know if all of my marketing and landing pages are hosted on the same platform?

Additionally, it is important to understand whether your website asks visitors for consent before applying cookies to their browsing session. This is mandatory in some jurisdictions, like the European Economic Area, California or Brazil.

Tip: Not sure if your website uses cookies? See this link on how to find out -
How do I know if my website uses Cookies and if so, how can I identify my Consent Management Platform?

Depending on your circumstances, select one of the guides bellow:

Step 1 - The Google Tag Manager

In case you don't have the Google Tag Manager installed on your website already, we highly recommend that you do, as it makes managing multiple tags a lot simpler - this guide from Google does a great job at explaining how to go about installing it into your website:

https://support.google.com/tagmanager/answer/14842164

In case you need help with this, reach out to support via the chat in the bottom-left corner of this page.

Step 2 - Consent Management Platform specific guides

Depending on the CMP you use, pick a guide bellow:
(not sure which platform you use? - then check this article out)

I don't (want to) use Cookies	Installing the N.Rich tag in Cookieless/Bootstrap mode
I use CookieBot	Installing the N.Rich tag via CookieBot
I use HubSpot's CMP	Installing the N.Rich tag via Hubspot CMP
I use Iubenda	Installing the N.Rich tag via Iubenda
I use CookieYes	Installing the N.Rich tag via CookieYes
I use Osano	Installing the N.Rich tag via Osano
I use TrustArc	Pending
I use UserCentrics	Pending
I use Didomi	Pending
I use CookieFirst	Pending
I use OneTrust	Pending
Oh no! My CMP is Pending or not on the list!	Don't worry - we got you! Drop us a message via the chat in the bottom left with the name of your CMP and we'll create a guide for you :)

Step 3 - Testing your tag installation

Before publishing your changes, we strongly recommend testing your setup using Preview Mode in Google Tag Manager. This helps ensure that everything works as expected and prevents issues caused by misconfiguration or conflicts.

Enable Preview Mode.

In GTM, click Preview in the top-right corner to activate Preview Mode.
Verify the tags.

1) Navigate to your website while Preview Mode is active.

2) Use the GTM debugging panel to confirm that:

3) The N.Rich Cookieless Tag fires on all pages.

4) The N.Rich Standard Tag fires only when analytics consent is granted.
Check for conflicts or errors.

Ensure both tags load without errors or conflicts with other scripts on your website.
Publish the changes.

Once you’ve verified the setup, return to GTM and click Submit to publish your container.
Finally, make sure that N.Rich is receiving both cookieless and standard signals from your website. You can check this in the Setup section of your N.Rich account - it should have a table that looks like this:

It can take several hours after adding the tags to your website before we start seeing data on our end.

Has it been longer than 6 hours since you have added the tags to your website and they are still showing as Inactive? Chat with support via the bottom-left chat bubble.