Cookie Consent Banner: Container JSON Configuration Guide for Google Tag Manager

The key idea of the integration is that NextRoll pushes GDPR consent information into Google Tag Manager as variables of the data layer. You should then 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. 

In this document, we will explain the step by step instructions on how to use Google Tag Manager with NextRoll Cookie Consent Banner in order to be compliant with GDPR and ePrivacy Directive.

  • Please note this is not legal advice and we recommend you check with your legal team prior to implementing this solution.
  • This solution applies to ONLY the vendors in the IAB EU TCFv2 Global Vendor List 

We assume that you've already created a Google Tag Manager account, created a website container, and added the container snippet to your website as required

See the Official Google documentation for more information on Google Tag Manager. With that said, let’s start the tutorial!

Step 1 - Download the Container JSON  

  • You need to first enable the Google Tag Manager integration in your RollWorks dashboard settings. Simply go to settings->GDPR
  • Download the container JSON file and Save your settings.

Step 2 - Import the Container JSON in Google Tag manager

  • The Container JSON is a package of events, variables and triggers embedded in a JSON file that are required to manage your tags via Google Tag Manager.
  • Log into your own Google Tag Manager container and head to the Admin section of the site. Under Container options, select Import Container. Step_2_.png
  • Login to GTM -> Click on Admin -> Import Container 
    • You may choose to overwrite conflicting tags or rename conflicting tags. 
    • Select Import File - Import the nextroll-consent.json 
    • Select your desired workspace 
    • Merge workspace with content 
    • Click ‘Confirm’ to complete the import process. 

Step 3 - Classify your Tags

  • You now need to classify your tags and define what user consent is required for firing each of them.
  • In the "Tags" section of the manager, edit each tag and add a trigger corresponding to the vendor that owns the tag.
  • Moving forward, every time you add a new tag that requires a GDPR consent, you must categorize it by adding the adequate trigger.
  • Below are the details on the triggers and variables that are available as part of NextRoll container JSON you imported in Step-2.
    • Click on the Tag (example: RollWorks Smart Pixel) 
    • Go to triggering -> Click to Add Triggers Step_3_part_1.png
    • Select the trigger from the drop-down list (example: nextroll-consent) Step_3_Part_2.png
    • Save the changesStep_3_Part_3.png
  • You need to classify all the required tags and define what user consent is required for firing each of them. Learn more on the events, triggers, and variables we support.
  • In the "Tags" section of the manager, add the above-configured trigger to the required tags.

If you have any questions, please contact your Account manager OR our customer support team 

Was this article helpful?
0 out of 0 found this helpful