Provisioning Manager

Provision your clients in Sampling Administration after you have migrated them to the Bazaarvoice Portal.

To customize your client’s cookie consent banners, sign in to the Bazaarvoice Portal and go to Sampling Administration > Provision.

The client must implement our recommended privacy management software to enable this customizing option. We recommend OneTrust.

This topic describes the steps your client must complete to set up and customize their OneTrust cookie consent banner. The topic also provides instructions on how your client can publish their production content delivery network (CDN) script, which you need to integrate with Google Tag Manager.

Step 1: Create a OneTrust account

To create a OneTrust account:

  1. Request a free account to create a cookie consent banner for one website.
  2. Go to Free Edition OneTrust and fill in the tool registration form.
  3. The account takes up to 48 hours to become available. You will receive an email with a confirmation link when it is ready.

Step 2: Add your website to your OneTrust account

To add your website to your OneTrust account:

  1. Sign in to your OneTrust account.
  2. Select the Cookie Compliance tile.
  3. Select Websites > Add Website and enter the website details.
Note: Enter the main domain name without https or www (for example, analyticsmania.com). By entering the main domain, you enable the GDPR cookie notification consent to work on all subdomains. If you enter www.analyticsmania.com, consent cookie settings will be saved only on www.analyticsmania.com. If you also have, for example, support.analyticsmania.com, that subdomain won't be able to access cookie settings.

To customize the cookie consent banner and preference center for your website:

  1. Select the website name that you just added.
  2. Select Branding from the menu.
  3. Select Template and ensure the Overwrite Template Styling option is enabled.
  4. Select Templates in the left navigation menu.
  5. Select GDPR Template.

Use the menu on the left to select different customizing options. You can change the layout, colors, content, and behavior. Under Content, select the Edit buttons on the right to open more menu options. Here are some of the options you can change within the menu to customize the banner:

  • Title & description to change the text that is displayed
  • Cookie policy to insert a link to your cookie policy
  • Button Set to edit which buttons are displayed
  • Under the Behaviour option, you can enable Require banner interaction to ensure a visitor must interact with the banner before continuing to use the website.

Step 4: Categorize your cookies

This step involves adding different types of cookies that you want your website to use. The visitor can choose which cookies they consent to in the website’s cookie preference center.

On the left navigation menu, select Cookiepedia > Categorizations and select Add Cookie.

By default, OneTrust offers a range of different types/categories of cookies. However, the specific types that you require for OneTrust integration are:

  • Strictly necessary
  • Performance (analytics)

To publish the changes and implement the new consent banner in your website:

  1. From the left navigation menu, select Websites and then choose your website from the list.
  2. In the top right-hand corner, select Publish.
  3. From the left navigation menu, select Scripts and then select Production Scripts.
    Your production CDN script is displayed. This script is required for integration with Google Tag Manager.
  4. Copy the CDN script and begin the Google Tag Manager setup.

Google Tag Manager setup

This section describes how to integrate OneTrust for a client in production. To proceed with the Google Tag Manager (GTM) setup, you need the client’s OneTrust production CDN script.

Step 1: Download the JSON file and import it into GTM

This step involves downloading the JSON file and importing it into GTM. GTM automatically creates a dedicated folder called GDPR Cookie Consent Notification containing the following 11 assets:

  • cHTML — cookie consent tag
    This is the tag into which you paste the OneTrust consent script. Without it, GDPR cookie consent notifications won’t work.
  • Custom — OneTrustLoaded trigger
    This asset is activated every time a consent banner script is loaded or consent preferences are updated.
  • Blocking — functional cookies not allowed trigger
  • Blocking — performance cookies not allowed trigger (analytics tags should be used with this trigger)
  • Blocking — social media cookies not allowed trigger
  • Blocking — targeting cookies not allowed trigger (marketing cookies)
  • dlv — OnetrustActiveGroups variable
    This is a data layer variable that returns all the cookie/consent groups to which a visitor has consented,
  • Regex — functional cookies allowed variable
    Returns true if a visitor has agreed to functional cookies. Otherwise, returns false.
  • Regex — performance cookies allowed variable
    Returns true if a visitor has agreed to performance/analytics cookies. Otherwise, returns false.
  • Regex — social media cookies allowed variable
    Returns true if a visitor has agreed to social media cookies. Otherwise, returns false.
  • Regex — targeting cookies allowed variable
    Returns true if a visitor has agreed to targeting/marketing cookies. Otherwise, returns false.
Note: If there are assets you don’t need, delete them (for example, if your website doesn't use social media cookies, delete the social media blocking trigger and regex assets).

To download the JSON file and import it to GTM:

  1. Go to the cookie consent file .
  2. Download the contents of the file into a JSON file on your local computer.
  3. Sign in to the GTM container and go to the Admin section.
  4. Under Container options, select Import Container.
  5. Select JSON file you downloaded to import to GTM.
  6. Select the workspace. Usually this involves selecting existing workspaces and then choosing a default workspace.
  7. Select the Merge import option.
  8. Select Overwrite conflicting tags, triggers and variables.

Step 2: Update the cHTML tag

After the client has finished creating and customizing their OneTrust cookie consent banner, they publish the consent banner and receive a production CDN script on OneTrust.

You need the following two pieces of script:

  • Link of the script
  • Value of the data-domain-script

To add the pieces of script:

  1. In GTM, go to the Workspace section and select tags from the left navigation menu.
  2. Select the cHTML - Cookie Consent tag.
  3. Paste the two pieces of information from the production CDN script into the tag.

Step 3: Update tags with triggers

This step describes how to update the tracking tags for personal data on GTM. You do this by adding one of the following four blocking triggers to each tracking tag as an exception. An exception blocks a trigger from firing under certain conditions.

  • Blocking functional cookies
  • Blocking performance cookies
  • Blocking social media cookies
  • Blocking targeting cookies

Example 1:
If a tag has a trigger to fire on all pages and a trigger exception that is set to “Page URL equals thankyou.html”, the tag will not fire on the page “thankyou.html”.

Example 2:
If a tag is related to analytics (such as a Google Analytics Event tag), then assign Blocking - performance cookies not allowed trigger as an exception. In the case of Google Ads tag, use Blocking - targeting cookies not allowed trigger.

To add a blocking trigger to a tag:

  1. Go to the Workspace section and select tags from the left navigation menu.
  2. Select the tracking tag to which you wish to add an exception.
  3. Under the Triggering section of the tag, select the pencil icon in the top right-hand corner to begin editing.
  4. Select Add Exception.
  5. Select the blocking trigger you want to add as an exception.
  6. Repeat this process for every tracking tag, such as Heap analytics and SessionStack.
Note: To add a blocking trigger to tags that fire on Page view, DOM ready, or Window Loaded Events, you need to delete the following triggers:
  • Page view
  • DOM Ready
  • Window Loaded
After you delete these triggers from your tracking tags, replace them with Custom—OneTrustLoaded firing trigger. This stops tracking tags from firing until a visitor gives consent to be tracked.

Step 4: Preview and submit the changes

To preview and submit changes:

  1. To view the changes in debug mode in your web browser, select Preview at the top of the screen.
  2. Enter the website URL and select Start.
  3. View the changes and verify that the tracking tags are fired on the OneTrustLoaded event when the cookies are accepted.
  4. To save the changes in GTM, select Submit at the top of the screen.