Consent categories¶
Visitors accept or refuse the cookies by category:
Category |
Used for |
Effect on the Google signals |
|---|---|---|
Necessary |
Session, cart, language, and the cookie choice itself. Always on; visitors cannot disable it. |
Security storage is always granted. |
Functional |
Embedded content such as videos and maps, the live chat, the campaign cookies (UTM) and features that remember choices, such as recently viewed products. |
Functionality storage and personalization storage. |
Analytics |
Visit statistics: Google Analytics, Search Console links, GA4 Measurement Protocol. |
Analytics storage. |
Marketing |
Advertising: Google Ads, Meta Pixel, Conversions API, remarketing, Customer Match. |
Ad storage, ad user data, and ad personalization. |
No tracking script of an unaccepted category is loaded, and no server event of an unaccepted category is sent. The optional cookies of the website itself (embedded content, campaign and live chat cookies) follow the Functional category.
What visitors see¶
The preferences dialog¶
The dialog lists the categories: Necessary (always on), Functional, Analytics, and Marketing, each with a switch, a short description and, when the visitor unfolds it, the cookies of the category with their provider, duration, and purpose. The visitor clicks Save my choices, or Reject all or Accept all.
- menu
- (Website frontend) ‣ Customize
- shows
- The Cookie preferences dialog: the four categories with their switches (Necessary "Always on"), the Marketing category unfolded with its cookie table (Cookie, Provider, Duration, Purpose), and the Reject all, Save my choices and Accept all buttons.
- highlight
- The cookie table of the unfolded category (red frame).
- data
- Demo website with Google Analytics, Google Ads and the Meta Pixel enabled.
- notes
- English UI, light theme, 1440px width.
The choice is stored in the consent cookie of the website, with the policy version and the date.
Change or withdraw the choice¶
Visitors can open the preferences dialog again at any time:
with the floating cookie button in the bottom left corner (if Floating Settings Button is enabled);
with the Cookie policy · Cookie settings links added to the copyright line of the footer;
with the Change my cookie settings button of the cookie policy page;
by clicking the notice shown in place of blocked embedded content.
When a visitor withdraws a category, the cookies of that category listed in the cookie list are deleted from the browser, and the tracking tags stop using them.
Tip
To add your own link to the cookie settings, for example in a footer column or a menu, point it
to #cookie-settings.
External consent platform (CMP)¶
If you already use a consent management platform, let it collect the consent and hand the result to Odoo. Set Consent Source to External consent platform (CMP): the consent banner of the website is hidden, and the following fields appear.
Field |
Description |
|---|---|
Consent Platform |
Cookiebot, Usercentrics, Complianz, or Custom (JavaScript event). |
CMP Script |
The script tag(s) of the platform, copied from its administration. They are inserted at the top of the head of every page. Leave it empty if the platform is loaded another way, for example through Google Tag Manager. |
Odoo reads the choice of the visitor from the platform and maps its categories to the four categories above (for example, the Preferences category of Cookiebot to Functional, Statistics to Analytics, and Marketing to Marketing). Each time the visitor changes the choice, the tracking tags are updated, and embedded content follows the functional choice.
Custom platform
Choose Custom (JavaScript event) if your platform is not in the list. From your consent tool, dispatch this browser event whenever the visitor makes or changes a choice:
window.dispatchEvent(new CustomEvent("website_tracking_consent", {
detail: {functional: true, analytics: true, marketing: false}
}));
Tip
With a consent platform, the Google tags load at once with all the signals denied (in the default Advanced consent mode), and the platform’s choice updates them. Set Wait for Update (ms) in the Google settings if your platform needs a moment to answer.
Consent log¶
Go to (or click Consent Log in the Website settings). Every choice made in the consent banner or in the consent platform is a line, which cannot be edited:
Date, Website (with several websites), and the Consent ID, a random identifier stored in the visitor’s consent cookie.
Source: Consent banner or Consent platform.
Functional, Analytics, Marketing: what the visitor accepted.
Policy Version, the Page where the choice was made, the truncated IP address (the last part is removed), and the contact if the visitor was logged in.
Use the filters Marketing Granted, Analytics Granted, and All Refused, and group the lines by Policy Version or Day. To answer a data subject’s request, search by Consent ID or contact.
Consent log lines are deleted automatically after 36 months. A choice that is identical to the previous choice of the same visitor session is not logged again.
Retention and debug settings¶
The Tracking block of contains the Tracking Debug Mode setting and the retention options:
Field |
Description |
|---|---|
Tracking Debug Mode |
Logs every tracking event and the data sent to each provider in the browser console, and in the server log. Disable it in production. |
Customer Name Order |
How the name of a customer is split into first and last name when sent to the advertising platforms: First name, Last name or Last name, First name (useful for Hungarian names, for instance). |
Keep Sent Events (days) |
Sent, failed, and discarded server events are deleted after this
delay. |
Keep Visitor Identifiers (days) |
The IP address, the browser data, and the ad click identifiers stored on orders and leads
are cleared after this delay. |
A scheduled action runs every day to apply these delays.
See also