CookieOfficer glossary

The same terms keep coming back in the panel and in the help articles. Below you'll find short definitions of them, grouped by topic. The terms project, domain and domain group are described in a separate article: What is the difference between a project, a domain and a domain group?.

Scanning and cookies

• Website scan: an automatic check of what a site stores on a visitor's device and which tracking tools it runs. The scanner opens the home page three times (before consent, after acceptance and after rejection) and each subpage once.
• Tracker: a tool that stores data on a visitor's device or tracks their behaviour, for example a cookie, an entry in browser storage or a pixel.
• Cookies (a section of the panel): a list of detected items with their category, lifetime and purpose. It is used to create the cookie declaration.
• Category: a group of trackers: Necessary, Analytics, Marketing, Functional or Unclassified. It determines whether consent is required.
• Unclassified: items that we haven't recognised automatically. Until a category is assigned, they aren't blocked, so they need your decision.
• Cookie declaration: a ready-made list of trackers to place in your privacy policy. It updates after a scan.
• Subpages: the number of addresses on a site. It affects the domain's pricing tier. We count them automatically after you add a domain, and you can start a missing count with the “Count subpages” button.

Banner and consents

• Consent banner: the window in which a visitor accepts or rejects categories. You configure it on the “Cookie banner” page.
• Consent: a visitor's decision, saved in the co_consent cookie, separately for each address.
• Consent validity: the period for which consent is valid. You set it on the “Settings” page.
• Consent version: a number that increases after a material change, that is, one concerning categories or scripts. An increase causes the banner to be shown again.
• Consent renewal: manual invalidation of consents, available from the Basic plan. You'll find it under Settings > Renew user consents.
• Consent Log: a record of visitors' decisions with the date, version and scope. It serves as evidence in the event of an inspection.
• Suspended project: a state in which the banner doesn't work and some features are unavailable.

Setup

• Installation code: a single line of code to paste into your site. You'll find it on the “Installation” page. It contains the project ID.
• Project ID: a unique string starting with co- that links the code on the site to the configuration in the panel.
• Automatic blocking: stopping scripts before they load. It requires pasting the code as the first script in the <head> section.
• Manual blocking: marking scripts with the data-co-cat attribute so that they run only after consent.
• Staging alias: an additional address of a test environment within a project, one per project, available from the Basic plan.
• Draft: changes to the banner saved in this browser and not yet published. Visible as a bar at the top of the editor.
• Organisation: a group of projects in your account, used to organise your portfolio. Not to be confused with a domain group.

Integrations and legal matters

• Google Consent Mode v2: a Google mechanism in which tools such as Analytics check for consent before they run. CookieOfficer passes visitors' decisions to it.
• Microsoft Consent Mode: the equivalent for Microsoft tools: UET and Clarity. You turn it on in Settings.
• Data controller: the entity that decides on the processing of visitors' data. In relation to us, that's you.
• Data processor (Processor): an entity that processes data on behalf of the controller. In relation to you, that's us.
• Data Processing Agreement (DPA): the agreement that governs our processing of data. You accept it together with the Terms of Service.