Cookie Consent and Mobile & CTV/OTT App Consent Terminology Guide

Application (app)

Mobile application which contains SDKs.

Geolocation rule

A rule specific to a geographic region that determines the consent model, behaviors, and content that will be shown to users from certain locations.

Geolocation rule group

Geolocation rules to be used together.

Autoblocking

A feature used to automatically block cookies from being installed on visitor devices. Autoblocking automates the process of setting end user cookies, scripts, and tags to respond to the preference selected by site visitors.

Categorization

Defined by the two major categories of cookies: First-party and third-party cookies. Many large organizations with subsidiaries in multiple countries utilize the same cookies but for different purposes. This may lead to subsidiaries of the parent organization being unable to comply without multiple categorizations for the same cookie. To address this problem, OneTrust provides the option to characterize the same cookie differently depending on how the cookie functions on the domain and the applicable privacy laws.

Consent models

Cookie consent models for each category of cookie set up in the application. There are five cookie consent models:

Notice only

: The cookie categories (except Strictly Necessary) will be set to Always Active and cannot be turned off by website visitors.

Opt-Out

: The cookie categories (except Strictly Necessary) will be set to Active but can be opted out of.

Opt-In

: The cookie categories (except Strictly Necessary) will not be set on the visitor's device unless they choose to accept them in the preference center.

Implied Consent

: The cookie categories (except Strictly Necessary) are not set until the website visitor clicks the OK button on the cookie banner or continues browsing the website. The website visitor can turn off cookie categories in the preference center.

Always Inactive

: The cookie categories (except Strictly Necessary) will set to Inactive and cannot be accepted by website visitors.

Custom

: If you select this option, you can set a different default status for each category of cookie on your site.

Domain

Website where cookies will be scanned.

First-party cookies

A first-party cookie is set by the publisher's web server or any JavaScript loaded on the website. Cookies that contain a pattern are categorized by pattern. Unique cookies (without a pattern) are categorized either by cookie contribution or through the Cookiepedia database.

Functional cookies

These cookies provide enhanced functionality and personalization on the website. They may be set by OneTrust or by third-party providers whose services we have added to our pages. If you do not allow these cookies, then some or all of these services may not function properly.

Performance cookies

These cookies allow users to count visits and traffic sources so they can measure and improve the performance of their site. They help users to identify which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If end users do not allow these cookies, site owners will not know when end users have visited their site and will not be able to monitor its performance.

Scanning

Feature that scans domains for cookies being dropped to website visitor's devices. These provide information about all cookies and tracking technologies present on a website site and categorize them based on function.

Scripts

The code script based on a completed template and applied geolocation rule group. These must be published to reflect the changes on a website. Every website scanned in the Cookie Consent tool will generate two sets of scripts: testing and production CDNs. The testing and production script tags are the snippets of code that you use to implement the Banner and Preference Center created in Cookie Consent for the website. Once the script tag is implemented on the website and republished in the application, any changes to the associated template, geolocation rules, or categorizations will be pushed to the site automatically.

Social media cookies

Cookies set by a range of social media services added to the website to provide a means to share content on social networks. These cookies can track end users' across other sites and build up a profile of their interests. This may impact the content and messages found on other websites they visit. Not allowing these cookies prevent the use of these sharing tools.

Strictly necessary cookies

These cookies are necessary for the website to function and cannot be switched off. These are usually only set in response to an end user’s actions which amount to a request for services, such as setting privacy preferences, logging in, or filling in forms. Users can set their browser to block or alert them about these cookies, but this causes some parts of the site to not work properly. These cookies do not store any personally identifiable information.

Tag manager

These third-party tag management systems can integrate with OneTrust scripts to manage the blocking of cookies. They can be used to inject cookies on a website and manage site content. They can be set up so that the scripts are controlled by the visitor’s consent preference choices. Google Tag Manager is a popular example.

Targeting cookies

These cookies may be set through a website by advertising partners. They may be used by those companies to build a profile of a visitor’s interests and show them relevant adverts on other sites. They do not store directly personal information but are based on uniquely identifying their browser and internet device. If end users do not allow these cookies, they will experience less targeted advertising.

Templates

Templates control the look and feel of a cookie banner, preference center, and cookie list to seamlessly match the style of a website and comply with applicable consent frameworks.

Third-party cookies

A third-party cookie can be set by a third-party server, such as an AdTech vendor, or via code loaded on the publisher's website. Cookies with a pattern and Cookiepedia-known host are categorized by pattern. Cookies with a known host and no pattern are categorized based on host-cookie matching, or by host categorization if a match is not found. Cookies with no pattern and that cannot be found in cookie contributions are categorized by their host's categorization.