A build-to-order Odoo website cookie consent banner that blocks non-essential trackers until opt-in and wires Google Consent Mode V2 signals into your analytics and ad tags. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 site. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo website cookie consent banner that blocks non-essential trackers until opt-in and wires Google Consent Mode V2 signals into your analytics and ad tags. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 site.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Most Odoo websites start collecting visitor data the moment a page loads. Analytics scripts, ad pixels, chat widgets, and embedded media all fire before anyone agrees to anything. Under GDPR, the ePrivacy directive, and newer regional consent rules, that is a compliance gap: you are expected to obtain informed opt-in before non-essential cookies and trackers run, and to be able to prove that consent later. Odoo core ships with no cookie consent mechanism at all, and a typical off-the-shelf apps.odoo.com module usually renders a cosmetic "accept" bar that never actually blocks the scripts it claims to govern. The banner ends up legally decorative while the trackers keep firing regardless of the click.
Real script gating: non-essential tags are held pending and injected only after the matching category is granted, not merely hidden behind a cosmetic bar
Google Consent Mode V2 integration pushing default-deny state and an update event for ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage and security_storage into your dataLayer
Granular consent categories (necessary, analytics, marketing, functional, personalization) each mapped to specific tags and scripts
Proof-of-consent log model storing timestamp, hashed IP, policy version, and exact per-category choices for auditability
QWeb + OWL banner, granular preferences modal, and a persistent re-open control so visitors can change their choice at any time
Website settings panel for editing categories, copy, and policy links without touching code
ECOSIRE builds a consent banner that behaves the way regulators actually expect. We implement a script-gating layer inside your Odoo website theme so that non-essential tags (Google Analytics 4, Google Ads, Meta Pixel, LinkedIn, chat and heatmap tools, embedded video) are held in a pending state and only injected after the visitor grants the matching category. On top of that we wire Google Consent Mode V2, pushing the consent signals (ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage, security_storage) into your dataLayer with a correct default-deny state and an update event on the visitor's choice, so your tags run in cookieless/modeled mode until opt-in rather than dropping data silently.
Technically, the banner is delivered as a proper Odoo module. A __manifest__.py declares the theme assets and dependencies; a new model (models.Model with fields, and @api.depends computes where needed) stores the category taxonomy and, optionally, a per-visitor consent record with timestamp, IP hash, policy version, and the exact choices made, so you have an auditable proof-of-consent log. Access is locked down with ir.model.access.csv plus record rules so consent logs are readable only by the right groups. The front end is built with QWeb templates and OWL components for the banner, the granular preferences modal, and a persistent "cookie settings" re-open control; a website settings panel lets non-technical staff edit categories, copy, and links to your privacy and cookie policy pages without touching code. Consent records can be queried through the standard XML-RPC/JSON-RPC API for DSAR handling or exported to your data-warehouse. The module targets Odoo 17.0, 18.0, and 19.0 and works on both Community and Enterprise (Enterprise's extra website tooling is respected but not required).
Because this is build-to-order, we start with a short scoping call to confirm which trackers you run, which regions and consent frameworks you must satisfy, and your policy-versioning needs. We then build on a staging copy of your site, run UAT against your real tag stack, and deploy behind a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company or multi-brand deployments, additional tracker integrations, deeper regional/localization requirements (for example region-specific consent logic or IAB TCF alignment), and larger consent-log data-migration volumes increase the quoted scope. You receive a fixed quote after the scoping call, never a surprise on the invoice.
Needs demonstrable, auditable opt-in before non-essential cookies run, with a proof-of-consent log and policy-version handling that stands up to a regulator or DSAR request rather than a decorative banner.
Wants analytics and ad tags to keep delivering usable, modeled data via Consent Mode V2 instead of going dark, while staying compliant across the regions they advertise in.
Manages the site day to day and needs a settings panel to edit categories, copy, and policy links, plus a clean module that upgrades safely across Odoo versions.
Runs Odoo internally and needs source code, git handover, access-controlled consent data, and API access so consent records fit into existing data and audit pipelines.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Cookie Consent Banner-Moduls von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Cookie Consent Banner“ und klicken Sie auf „Installieren“.
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Actually blocks non-essential trackers | Yes, real server-aware script gating until opt-in | Possible, but depends entirely on your build effort | Often cosmetic, tags keep firing | |
| Google Consent Mode V2 | Full signal set, default-deny, update on choice | You must design and maintain the dataLayer logic | Partial or absent in many modules | |
| Proof-of-consent audit log | Access-controlled log with policy version and choices | Only if you scope and build it | Rarely included | |
| Fit to your exact tags and regions | Scoped to your stack during the build | Fully bespoke but on your resources | Generic, one-size configuration | |
| Odoo 17/18/19 upgrade path | Targeted and supported across versions | Your team owns every upgrade | Depends on the vendor's roadmap | |
| Source code and git handover | Full source plus tagged git repo | You own it by definition | Often obfuscated or license-locked | |
| Support and delivery | 2-4 weeks, UAT, rollback, support window | Depends on internal bandwidth | Self-install, ticket-based support | |
| Total cost of ownership | From $249 indicative, fixed quote after scoping | High developer time and maintenance | Low sticker price, hidden compliance risk |
This is a build-to-order module, not an instant download. After a scoping call to confirm your trackers, regions, and policy needs, typical delivery is 2-4 weeks from confirmed scope. We build on a staging copy, run UAT against your real tag stack, then deploy behind a rollback plan.
It genuinely gates scripts. Non-essential tags are held in a pending state and only injected after the visitor grants the matching category, and Consent Mode V2 signals default to deny until opt-in. Nothing non-essential fires during the pre-consent page load.
Pricing starts from $249 as an indicative single-company base figure. Drivers like multi-company deployments, extra tracker integrations, region-specific consent logic, and consent-log data migration increase scope. After the scoping call you get a fixed written quote before any build begins.
Every build includes a post-go-live support window for defect fixes and consent-behavior tuning. Because you receive the full source and git repository, you can maintain it yourself afterward, or we can provide an ongoing support/upgrade arrangement, including moving the module across Odoo 17/18/19 upgrades.
It works on both. The module is built with standard Odoo website, QWeb, and OWL primitives, so it does not depend on Enterprise-only features. If you run Enterprise, its extra website tooling is respected but not required.
Yes. An optional consent-log model records timestamp, hashed IP, policy version, and the exact per-category choices, secured with access rules and reachable through the XML-RPC/JSON-RPC API, so you can produce audit evidence or fulfil a data-subject request.
Yes. We push the full Consent Mode V2 signal set into your dataLayer with a default-deny state and an update event on the visitor's choice, so Google Analytics 4 and Google Ads run in cookieless/modeled mode until opt-in instead of losing data outright.
A build-to-order Odoo website cookie consent banner that blocks non-essential trackers until opt-in and wires Google Consent Mode V2 signals into your analytics and ad tags. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 site.