This section details filter options and how to review and export dashboard data.
Important
It can take up to an hour for the user transaction data to be available in the tab of the menu.
Filtering Options
The entire consent rate dashboard may be filtered using the filter icon 
to display consent stats dynamically based on the criteria provided. This enable you 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—allows you to analyze consent in a variety of ways.
The default filter options include the following:
-
Source
To filter by a singular domain, enter a name to search and select the collection points containing that domain name. This allows for a wholistic view of the consent interactions for all locations where website visitors interact with the Banner and Preference Center.
-
Template
Enter a name to search and select the collection points you want to view in the dashboard. Filtering by template provides insight into how verbiage and layout may affect website visitor opt-in rate.
For example, you can deploy a different template layout and change the text presented for Accept All to I Accept. After a week, you can check to see if you saw a higher or lower consent rate. This can be best tested using Consent Rate Optimization’s A/B testing that is available as an add-on service. For more information, see Consent Rate Optimization: Configuring A/B Testing.
Note
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.
-
Time Windows
You can filter the dashboard by time intervals of 1 week, 1 month, 3 months, and 6 months and click Apply to enable the filter.
Analyzing Results
The shows various pieces of information that are extremely valuable in understanding how a website visitor consents. Below, review what information is displayed for each widget 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 .
Note
Total New Visitors data includes the number of transactions received on the Banner or Preference Center based on filters applied.
For example, if a user interacts with the OneTrust Banner and then revisits your website and changes their preferences, this would show up as two total visitors and includes the details of each transaction made.
Another example: a user visits a website without a Banner and only a link to the Preference Center in the footer. When the user goes to another page on the site, or closes the tab or browser, this accounts for one transaction. When the user comes back, opens the Preference Center and changes consent, this is recorded as a second transaction and two total new visitors now display since there were two transactions.
Website Interactions
Every time a website visitor interacts with the Banner or Preference Center, the interaction is recorded.
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. This means the user has accepted the cookie category.
-
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 on a site where the OneTrust script is implemented, regardless of whether a Banner is displayed or only a Preference Center link has been implemented.
Note
This leaves the category state as-is, which means the consent is saved as it corresponds to the default settings configured in your geolocation rules. If the consent model is set to opt-out, the cookie category is allowed or accepted; if the consent model is set to opt-in, the cookie category is disabled or rejected.
-
No Choice is sent when the visitor is unable to make a selection as the category, special purpose, or feature is set to Notice Only.
Note
Colors do not dictate the consent transaction type. You can hover on each option to view the consent type and the number of transactions with a given status.
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 (deny or reject) 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.
Note
New Visitors by Device Type, Country, and Browser data are only available for users who have consented or allowed the category selected in the Advanced Analytics section in Geolocation Rules. All other users' data for the three groups will be listed as Unknown.
To integrate and test on a website
When a user gives consent through the Banner or Preference Center, you will see a consentreceipts network call. This can be viewed on any website where OneTrust scripts are implemented by searching for consentreceipts in the Network tab of a browser's developer tools.
Note
Users must make a preference selection on the Banner or Preference Center for the consentreceipts network call to be available.
Enabling the Capture Records of Consent setting 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 tab on the menu.
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 “identifier” 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
You will be able to find the user transactions from their CONSENT ID found in the OptanonConsent cookie or retrieve the id using this in the console: OneTrust.getDataSubjectId().
