NextRoll can push variables to the Google Tag Manager data layer to allow you to control when tags are loaded and to use the consent gathered by the NextRoll Cookie Consent Banner with other TCFv2.2 IAB vendors to trigger their pixels.
- Please note this is not legal advice and we recommend that you check with your legal team prior to implementing this solution.
- Using Google Tag Manager to help implement your Cookie Consent Banner simplifies the adoption of the Cookie Law requirements.
- This solution applies only to the vendors in the TCFv2.2 IAB Global Vendor List.
- You can use this solution for all analytics tools, but not for AdSense banners, YouTube videos, social buttons, or widgets of any kind.
- Learn more about the specific consent variables, vendor IDs, and events that NextRoll can push to the GTM data layer.
Before you start:
Before you begin you must have:
- A Google Tag Manager (GTM) account and container. Learn how-to here.
- Install the container on your website or mobile app. Learn how-to here.
To help you with the above the Google Support help center offers this Google Tag Manager Setup and installation video tutorial.
Step 1. Setup your Pixel using Google Tag Manager
- The RollWorks Pixel is a JavaScript code snippet that is uniquely generated for your RollWorks account when you sign up.
- Google Tag Manager (GTM) is a container for tags (scripts). Google Tag Manager makes it easy to add and manage multiple scripts like the RollWorks Pixel to your website.
Follow this step-by-step guide to activate your Pixel in GTM through a single GTM tag that triggers on all pages to track the visitor traffic on all your website pages.
Step 2. Setup your vendor Pixel using Google Tag Manager
- Follow the third-party vendor’s instructions on how to set up their Pixel as a tag in GTM.
- As a reminder, this solution applies only to the vendors in the TCFv2.2 IAB Global Vendor List.
Step 3. Implement a new trigger in Google Tag Manager
- Create a new trigger in GTM using this trigger configuration:
- Trigger type: Custom Event
- Event name: nextroll-consent
- This trigger fires on: nextrollVendorsConsent contains tcf:130
To help you with the above the Google Support help center offers this support article to learn how to create and edit triggers in GTM.
Step 4. Add the ‘nextroll-consent’ trigger to your vendor tags
In this last step, you need to classify your vendor tags and define what user consent is required for firing each of them. Moving forward, every time you add a new tag that requires consent, you must categorize it by adding the adequate trigger.
- Go to the ‘Tags’ section of GTM.
- Click on the Tag you want to edit (example: AdRoll Smart Pixel).
Go to ‘Triggering’ and click to ‘Choose a trigger to make this tag fire’.
-
Select the trigger ‘nextroll-consent’ from the drop-down list. This is the trigger you created in Step 2.
- Save changes
Variables pushed by NextRoll to GTM dataLayer
NextRoll pushes variables to the Google Tag Manager data layer to allow you to control when tags are loaded and to share the consent information with TCFv2.2 IAB vendors.
Below are the variables that NextRoll pushes:
|
Variable |
Type |
Description |
|---|---|---|
|
nextrollVendorsConsent |
Vendor/Partner |
List of vendors/partners the consumer has consented to. Wrapped by a comma. Takes into account the required purposes defined in TCFv2.2 |
|
nextrollVendorsConsentUnknown |
Vendor/Partner |
The list of vendors/partners the consumer did not consent to or is unknown. |
|
nextrollVendorsConsentDenied |
Vendor/Partner |
The list of vendors/partners the consumer denied consent. |
|
nextrollVendorsRawConsent |
Vendor/Partner |
List of vendors/partners separated by comma the consumer gave the consent to but does not take into account the purposes of each vendor/partner. |
|
nextrollVendorsRawConsentUnknown |
Vendor/Partner |
The list of vendors/partners wrapped by comma the consumer did not consent to or unknown and does not take into account the purposes of each vendor/partner. |
|
nextrollVendorsRawConsentDenied |
Vendor/Partner |
The list of vendors/partners wrapped by comma the consumer denied consent. It does not take into account the purposes of each vendor/partner. |
|
nextrollPurposesConsent |
Purposes |
List of comma-wrapped purposes the consumer gave consent to. |
|
nextrollPurposesConsentUnknown |
Purposes |
List of comma-wrapped purposes the consumer consent is unknown. |
|
nextrollPurposesConsentDenied |
Purposes |
List of comma-wrapped purposes the consumer denied consent. |
|
nextrollgdpr |
GDPR |
This is to determine if GDPR conditions apply to the consumer. Ex: 0 (Doesn’t apply) and 1 (applies). |
|
nextrolliab |
IAB |
IAB consent string with the purposes and consent information of each vendor and purpose. |
Vendor variables pushed by NextRoll to GTM data layer
Here are the vendor/partner ID notations that can be reported in the data layer as prefixes.
|
Vendor Variable |
Description |
|---|---|
|
tcf |
For the vendors in IAB TCFv2.2 |
|
c |
For vendors that are not part of the IAB TCFv2.2 framework |
Events
You have the option to create a list of events that decides when to load a particular vendor tag on Google Tag Manager. All the variables listed in this article can be called with every event listed below.
To learn more about Custom event triggers in GTM, Google Support offers this help center article.
🚨 At this time, NextRoll cannot support custom events.
|
Event |
Description |
Examples |
|---|---|---|
|
nextroll-consent |
This event is pushed to GTM when the page first loads (& subsequent page loads) and NextRoll cookie consent tool appears on the webpage. |
Suits best for the vendors/partners that require consent. |
|
nextroll-ready |
This event is pushed to GTM to fire the tags only once on the page. The consent status is unknown at this point |
Suits best for the vendors/partners that do not require consent. |
|
nextroll-consent-modified |
This event is pushed to GTM to whenever the consent status changes |
Suits for the vendors/partners that require consent and overriding the consent changes. |