October 2020: Consent Control with Granular Support

[jwheeler]

Today’s release enhances Consent Control, updates the TagControl UI, and extends No-Code autoblocking capabilities. 

UI Update:

We have added indicators to show that the Omni-Tag has been added and is working on your sites.

At the top of the main Sites page, there are metrics that breaks down what your sites are seeing from the Omni Tag. It shows:

1.  Number of sites observing records with Real Time Scanning
2. Sites enforcement from Tag Control or Autoblocking
3. New tags observed in the last 7 days that aren’t in a Whitelist.  These are tags that you may need to move to an appropriate list.

Within this same screen we have updated the table to include Wild Card Search and Mode Filter.  We have also included the following columns: Site Name, URL, Policy Enforcement and Last Modified by.

Policy Enforcement will tell you if the URL is Observing, in Tag Control Only, Prior Consent (GDPR), or Opt-Out CCPA.

Additionally, users can now add sites more quickly with the new “+ Add Site” button in the top right corner.  This will open a model where you will enter the site information.  If you need to add more than one new site simply click the check box for “Add Another”

Note: 6the delete site button has been removed from the Site List screen and has been moved to Site Details page of each URL.

In the previous UI you had separate pages for site settings, policies and configurations.  This has been moved to a single page.  On this page are 3 tabs to navigate between the 3 settings.

Tag Policy

This page remains the same as before with a few small tweaks of colours.  From here you manage your white list and observed resources.  You also can move views of the Observe and Approved tags to a side by side or top and bottom experience.

We also added Latency and Prevalence columns to the tables to help users make decisions about whether or not to add a tag to their white list and added a new “Injectable” vendor category:

• Latency:  Average speed of the resource seen in the scans over the last 7 days.
• Prevalence:  How often the Resource is seen over the scanned pages.
• New Category - Injectable:  These represent vendors we know are not typically on pages but injected via things like Browser Extensions (i.e. Ghostery or Google Translate).

Site Settings

This new page is a combination of previous pages that can be broken out into 4 sections.

• Site Details
  • Site information, URL, and description
• Policy Enforcement (can only be changed by engineering)
  • Allows you to turn on enforcement of auto blocking or observing of tags.
    • Only one setting can be toggled per site
  • Console Logging
    • Enabled to better debug your site with enforcement on (this is typically used for a developer).
  • Advanced
    • Site Deletion

Site Settings

This section is managed by Crownpeak engineering and control the amount of data collected during observation.  This is typically done at a smaller percentage and adjusted depending on site traffic.

Granular Autoblocking

Now that the UI is up to date using the new granular feature of autoblocking is simple.  Like before, once the Omni-Tag is implemented correctly you want to ensure a few things are in place.

1. The UCP notice is set up
2. Your whitelist is created with the proper tags approved and essentials are marked
3. The vendors in your UCP setup and whitelist match, including essentials
4. You have submitted a support ticket to enable enforce mode

Once these steps are completed your notice will start auto blocking. Autoblocking works for all or nothing, category-level, or vendor-level consent, based on how your UCP notice is setup.