Enabling Consent Logging and the Cookie Consent Dashboard

« Go Back
Enabling Consent Logging and the Cookie Consent Dashboard

Cookie banners and Preference Centers can be set up to log records of consent and consent preferences from site visitors.

By enabling logging for a geolocation rule, you can log and view consent transaction receipts for visitors to your site. Site visitors are identified by the unique and anonymous cookie set on their devices after expressing consent preferences. The cookie does not contain any personal identifiable information at this point.

Once the cookie is set on their device, each interaction the data subject has due to the banner or Preference Center will be logged individually and associated with the identifier assigned to the cookie on their device.

To configure cookie banners and Preference Centers to start sending consent interactions, enable the setting below in Geolocation Rules. This must be done for every rule for which you would like to collect consent transactions. This is done to account for any scenarios where you may not want to send interactions for a particular audience. After enabling, you will need to republish the domain for which you want to start tracking consent.


By default, OneTrust scanner consent receipts are filtered out of consent logging.

To enable records of consent for a geolocation rule group

  1. On the Cookie Consent menu, select Geolocation Rules. The Geolocation Rule Groups screen appears.

  2. Click on the name of the rule group you want to edit. The Geolocation Rule Group Details screen appears.

  3. Click the Edit icon edit_icon.png for the rule you want to edit.

  4. Enable the Capture Records of Consent setting.

  5. Click the Save button.


    You must publish the Production CDN followed by the Testing CDN to apply this configuration change.

Publishing the Production CDN will create a Collection Point for each combination of domain, rule group, rule, and template in the Consent & Preference Management module, with purposes mapped for each category, purpose, and special feature. Once the collection point is created, the Testing CDN will also collect consent data and display in the Cookie Consent dashboard.


If you want to display user ID consent logging information related to your end users, see the User ID section in Customizing the Preference Center Template.

Advanced Analytics

Advanced Analytics allow you to collect additional data on a purpose of processing. Enabling this for a category sends browser type, device type, and country where the user consented. You can only select one processing purpose for Advanced Analytics per geolocation rule. This information will be shown in the dashboard.

  1. On the Geolocation Rule Group Details screen, select a processing purpose for Advanced Analytics.

  2. Click the Save button.

  3. Publish your changes.

When a user gives consent through the cookie banner or Preference Center, you will see a "consentreceipts" network call. The data collected from enabling Advanced Analytics can be viewed there and in the Cookie Consent dashboard.



Advanced Analytics will only be recorded if the user gives consent for the category that you have assigned advanced analytics to. If the user does not consent to the category that you have assigned, you will see "Unknown" in the Advanced Analytics pie charts. If you would like Advanced Analytics to always be recorded, we suggest assigning the Strictly Necessary category or a category that is set to Notice Only in your geolocation rule.

To integrate and test on a website

Enabling this feature means that there will be a collection point created against the domain the next time that you publish the Production CDN the consent and consent preferences will be collected. Once the script is placed on a domain, you will have two different API calls available after the user makes a selection on the cookie banner or Preference Center.

  • An OPTIONS call that checks to ensure the portal to capture consent is available.

  • A POST call to log the visitor’s preferences. You can use this call to confirm that the correct consent preferences were logged in the payload.


Performing a receipt search

A particular consent can be viewed by performing a Receipt Search within the Universal Consent module.

This allows you to search for specific receipts via a receipt GUID or data subject identifier. The receipt GUID can be captured through the payload sent in the request as shown above. The data subject identifier can also be captured through the request payload or within the OptanonConsent cookie as shown below.

  • Cookie Name: OptanonConsent

  • Cookie Value: isIABGlobal=false&datestamp=Thu+Jan+09+2020+16%3A10%3A27+GMT-0500+(Eastern+Standard+Time)&version=5.9.0&landingPath=NotLandingPage&groups=req%3A1%2Csm%3A1%2Csmv%3A1%2CBG139%3A1%2Cad%3A1%2Cadv%3A1%2CBG137%3A1%2Cpf%3A1%2Cpfv%3A1%2CBG138%3A1%2Cpzv%3A1%2Cpz%3A1%2CBG140%3A1%2Cbb%3A1%2Cbbv%3A1%2CBG141%3A1%2Csa%3A1%2Csav%3A1%2CBG136%3A1&hosts=&geolocation=NL%3BNH&consentId=2d0993a8-8956-4a76-b11b-f47bd335b785&interactionCount=2&AwaitingReconsent=false

Website Interactions

Every time a website visitor interacts with the cookie banner or Preference Center, the interaction is recorded.



Accept All

Cookie Banner

Reject All

Cookie Banner


Cookie Banner

Accept All

Preference Center

Save Settings

Preference Center

Reject All

Preference Center


Preference Center

Navigating to a new site

Closing the browser

Each interaction records the Transaction Type for a category, purpose, or special feature. Transaction types tell the state (active/inactive) and provide some information on the website visitor.

Transaction types include:

  • Opt-in (“CONFIRMED”) is sent when the visitor has a choice (consent model not equal to Notice Only) and the status of the category, purpose, or special feature is active.

  • Opt-out is sent when the visitor rejects all or disables a category, purpose, or special feature and saves settings.

  • Not Given is sent when the visitor clicks close, navigates to a different website, or closes the browser tab.

  • No Choice is when the visitor is unable to make a selection as the category, special purpose, or feature is set to Notice Only.

Dashboard Overview

Transactions are aggregated hourly and can be accessed in the Dashboard section of the Cookie Consent menu.

Time Windows

You can filter the dashboard by time intervals of 1 week, 1 month, 3 months, and 6 months.


Filtering Options

The entire consent rate dashboard may be filtered using the filter icon in the top right of the interface to slice consent stats dynamically based on the criteria provided. This presents you with the ability to filter based on the Collection Point and, because the Collection Point is created as a combination of the domain, rule group, rule, and template, this allows you to analyze consent in a variety of ways.

A few of the ways this may be leveraged are:

  • Domain

    To filter by a singular domain, type ahead to search and select the collections points with that domain name in it. This allows for a wholistic view of the consent interactions for all locations website visitors interact with the Cookie Banner and Preference Center.

  • Rule

    Type ahead to search and select all Collection Points with a particular rule name. For example, these are usually named ‘Global’, ‘CCPA Rule', or ‘GDPR Rule’. You may want to select multiple Collections Points to see the consent rates broken down for multiple domains using that rule, or you may want to choose just a single collection point on which to focus. This is useful when trying to determine things such as how a certain audience responds to the information and setting present on the Cookie Banner and Preference Center.

  • Template

    Type ahead to search and select the collections points you which to view in the dashboard. Filtering by template, allows you to start to understand how verbiage and layout may affect website visitor opt-in rate. For example, you may want to try a different template layout for a week and change the text presented for ‘Accept All’ to ‘I Accept’, then check in a week to see if you saw a higher or lower consent rate.


    If you change your Template selection in the Geolocation Rule associated with your domain script and re-publish, the previously collected consent data will appear in the filtering tab under Not Tracked.

Analyzing Results

The Dashboard shows various pieces of information that are extremely valuable in understanding how a website visitor consents. Below, each widget is explained with what is being displayed and how this information may be used.

Total New Visitors

Total Receipts shows the total counts of interactions or impressions that a visitor has with the banner and preference center. This does not remove duplicates but tracking the number of visitors who have multiple interactions can be gathered by Reporting.

  • Red: Opt-out

  • Blue: Not Given

  • Grey: Opt-in

  • Green: No Choice


New Visitors Opt-in

New Visitors Opt-in shows the Opt-in by consent group. This is due to the site visitor choosing to Accept All or if the site visitor chooses to enable certain consent groups in the Preference Center.


New Visitors Opt-out

New Visitors Opt-out shows the Opt-out by consent group. This is due to the site visitor choosing to Reject All or if the site visitor chooses to disable certain consent groups in the Preference Center.


New Visitors Not Given

New Visitor Not Given shows when the user declined to interact with the Cookie Banner or Preference Center. This could be due to the site visitor closing the Cookie Banner, navigating away from the page, or closing the browser.


New Visitors By Device Type

New Visitor By Device Type will display the different device types recorded when enabling Advanced Analytics.


New Visitors By Country

New Visitor By Country will display the countries recorded when enabling Advanced Analytics.


New Visitors By Browser

New Visitor By Country will display the browser types recorded when enabling Advanced Analytics.


Troubleshooting: Page reload causes failed consent receipts

If your consent receipts fail because of page reload, implement the following script:

<script>window.addEventListener('OTConsentApplied', function () { location.reload();});</script>

Powered by