NextRoll pushes GDPR consent information into Google Tag Manager (GTM) as variables of the data layer. It is recommended that you configure GTM to only fire tags after consent has been collected for every vendor via the NextRoll Cookie Consent Banner.
All the triggers, variables, and events are packaged into a container JSON file that customers could use to import (instead of manual configuring), facilitating an easy one-time setup process in Google Tag Manager.
Note the following:
- Using Google Tag Manager is highly recommended given that it drastically simplifies the adoption of the Cookie Law requirements. You can use this solution for all analytics tools, but not for AdSense banners, YouTube videos, or social buttons or widgets of any kind.
- This solution applies to ONLY the vendors in the IAB EU TCFv2 Global Vendor List.
- Disclaimer: This is not legal advice and we recommend you check with your legal team prior to implementing this solution.
Variables
NextRoll pushes variables to the Google Tag Manager dataLayer to allow you to control when tags are loaded and to share the consent information with TCFv2.0 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 comma. Takes into account the required purposes defined in TCFv2.0 |
|
nextrollVendorsConsentUnknown |
Vendor/Partner |
The list of vendors/partners the consumer did not consent to or 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 ID’s
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.0 |
|
c |
For vendors that are not part of the IAB TCFv2 framework |
Events
You have an option to create a list of events that decides when to load a particular vendor/partner tag on Google Tag Manager. All the Variables listed above can be called with every event listed below. Learn more about 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. |
Note:
- At this time, NextRoll cannot support your custom events.