A build-to-order Odoo module that wires Google Consent Mode v2 into your Odoo website, gating analytics and advertising tags behind a real consent state instead of firing them on page load. ECOSIRE scopes, builds, installs and supports it — typical delivery 2-4 weeks from confirmed scope. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
A build-to-order Odoo module that wires Google Consent Mode v2 into your Odoo website, gating analytics and advertising tags behind a real consent state instead of firing them on page load. ECOSIRE scopes, builds, installs and supports it — typical delivery 2-4 weeks from confirmed scope.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Odoo.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
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 2-4 weeks from confirmed scope. Pricing starts from $249 (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.
Needs conversion tracking and audiences to keep working under consent rules. Wants tags gated correctly so Google can still model conversions from consented traffic, without losing measurement to a blanket cookie block.
Answerable for how the website handles EEA/UK visitors. Needs demonstrable default-deny behavior, granular per-parameter consent, retained-but-anonymized consent logs, and an audit report they can produce on request.
Owns the Odoo website and doesn't want tracking snippets hand-edited into the theme. Wants a clean module with backend settings, proper security rules, and a git handover they can maintain and upgrade across Odoo versions.
Needs consent handled properly across multiple regions and Google products so ad spend keeps performing, with documentation and training so the client's team can operate it after handover.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Consent Mode v2 default-deny state | Built-in: denied defaults set before gtag.js, with wait_for_update | Possible, but you design and maintain the load order yourself | Often a generic default that may not match your product mix | |
| Fit to your Google product mix | Scoped to your GA4/Ads/tag-manager setup and regional policy | Whatever your developer builds, if scoped correctly | One-size configuration, limited to its assumptions | |
| Granular per-parameter consent | Each of the four v2 parameters mapped to banner choices | Depends entirely on in-house build effort | Varies; frequently accept/reject only | |
| Consent audit log & report | Anonymized consent model + QWeb audit report + API access | Must be designed and secured from scratch | Rarely included or backend-integrated | |
| Security & access control | ir.model.access.csv + record rules restrict consent logs | Your responsibility to define and test | Depends on the module's quality | |
| Odoo version/edition coverage | 17/18/19, Community or Enterprise, edition hooks handled | Whatever you build and re-test per upgrade | Tied to the versions the vendor chose to support | |
| Delivery & ownership | 2-4 weeks, staging UAT, rollback plan, git handover | Depends on internal capacity and priorities | Instant install but generic and self-supported | |
| Support after go-live | Support window + training + optional maintenance | Self-supported unless you retain a developer | Vendor ticket queue, no fit to your setup |
No. This is a build-to-order Odoo module. We build it against your confirmed Odoo version, edition, and Google product mix after a scoping call, then install and support it. There is no instant download — the value is that it is fitted to your exact tracking setup and regional policy.
Typical delivery is 2-4 weeks from confirmed scope. The clock starts once we've agreed your Odoo version/edition, Google products (GA4, Ads, tag manager), regional consent policy, and banner design. Multi-company, multi-website, or extra integrations can extend the timeline, and we confirm dates in the fixed quote.
Pricing starts from $249 as an indicative single-company base figure. After a short scoping call we give you a fixed quote. Drivers that increase scope include multi-company/multi-website setups, additional Google or third-party integrations, deeper regional-policy localization, and migrating existing consent data. The from-price is a starting point, never a firm price until scope is agreed.
Every build includes a post-go-live support window for defect fixes and consent-behavior adjustments, plus a training session. You also receive the git repository, so your team can maintain it. For ongoing changes, Google-product updates, or an Odoo version upgrade, we offer a support/maintenance arrangement quoted separately.
Yes. The module sets the Consent Mode v2 default state before your Google tags load, and we wire GA4, Google Ads, and (where used) a tag-manager container to inherit the same consent signals. We confirm your exact product mix during scoping so the load order and parameter mapping are correct for your stack.
Odoo core gives you a cookie bar and a place for tracking IDs, but it does not implement Consent Mode v2 — there's no default-deny state, no `gtag('consent', ...)` orchestration, no granular mapping to the four v2 parameters, and no persistent consent audit log. This module adds all of that as a proper backend-configured feature.
We build for Odoo 17.0, 18.0, and 19.0, on Community or Enterprise. We confirm your version and edition during scoping because a few website and asset-bundle hooks differ between them; the delivered module targets your specific environment.
A build-to-order Odoo module that wires Google Consent Mode v2 into your Odoo website, gating analytics and advertising tags behind a real consent state instead of firing them on page load. ECOSIRE scopes, builds, installs and supports it — typical delivery 2-4 weeks from confirmed scope.