If you run marketing on an Odoo website, your Google tags almost certainly fire before anyone has chosen to be tracked. A plain <script> snippet pasted into the theme, or a tag-manager container loaded on every page, sets analytics and advertising cookies the moment the DOM renders — with no default consent state, no regional gating, and no audit trail. That is exactly what EU/EEA and UK privacy enforcement now targets, and it is why Google's advertising and measurement products increasingly refuse to model conversions or build audiences from traffic that arrives without valid consent signals. Odoo core gives you a cookie bar and a place to drop a tracking ID, but it does not implement Consent Mode v2: there is no default-deny state, no gtag('consent', ...) orchestration, no mapping of banner choices to the four consent parameters, and no persistent record of what a given visitor allowed.

We build a dedicated Odoo module that implements Google Consent Mode v2 end to end on your Odoo-hosted website. The module ships its own __manifest__.py declaring a website-scoped asset bundle (web.assets_frontend) that loads the consent framework before any Google tag. It pushes a default consent state — ad_storage, analytics_storage, ad_user_data, ad_personalization all set to denied, plus wait_for_update — into the data layer ahead of gtag.js, then emits a single update call only after the visitor acts on the banner. Banner choices are captured in an OWL/JS consent widget and mapped granularly to each parameter, with region-aware defaults driven by server-side configuration so EEA/UK visitors start denied while other regions can follow your chosen policy. Where you use a tag-manager container, we wire the same signals through consent-initialization so downstream tags inherit the state rather than firing blind.

On the Odoo side, consent policy and per-visitor consent records are backed by real models (models.Model with typed fields, @api.depends computes for derived status, and an anonymized visitor/consent-log model). Access is locked down with ir.model.access.csv plus record rules so consent logs are readable only by the right groups, and settings live in a res.config.settings extension exposed through a clean backend view (XML views, optionally an OWL component). The consent state is retrievable over Odoo's XML-RPC/JSON-RPC API for downstream reporting, and a QWeb report can render a consent-audit summary for a given date range or visitor. The build targets Odoo 17.0, 18.0 or 19.0 and works on Community or Enterprise — we confirm your edition during scoping because a few website and asset hooks differ between versions and editions.

Because this is built to order, nothing is a black-box download. After a short scoping call we confirm your Odoo version and edition, your Google product mix (GA4, Google Ads, tag manager), your regional consent policy, and your banner design. We build the module against a staging copy of your site, you sign off through UAT, and we deploy to production with a rollback plan and a post-go-live support window. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company or multi-website setups, additional Google/third-party integrations, deeper regional-policy localization, and migration of existing consent data increase the quoted scope. You receive a fixed quote after the scoping call — the from-price is a starting point, never a firm figure until scope is agreed.