Google Tag Manager Enhanced Conversion Tracking

We build a dedicated Odoo module that owns the full enhanced-conversion pipeline. On the front end, the module injects a structured dataLayer at the right lifecycle moments (product view, add-to-cart, begin_checkout, purchase) using QWeb templates and OWL components hooked into the website checkout controllers, each event carrying a stable transaction_id derived from the order reference. On the back end, a new model (models.Model with fields, @api.depends computes, and ir.model.access.csv plus record rules for security) mirrors every marketing event and exposes a server-side dispatch layer: when an order is confirmed or paid, an automated action / server action queues a server-side conversion call so the sale is reported even if the browser event never fired. First-party identifiers (email, phone) are SHA-256 hashed and normalized before they ever leave your server, so enhanced conversions are matched without exposing raw PII. The shared transaction_id lets the tag manager deduplicate browser and server hits, ending double-counting.

Technically, everything lives in a proper Odoo module: __manifest__.py declaring dependencies (website_sale, website), models under models/, views and QWeb assets under views/, security under security/, and configuration surfaced through res.config.settings so container IDs, consent mode defaults, hashing keys, and per-event toggles are managed in Settings rather than hard-coded. Confirmed conversions and any transmission failures are logged to a queryable model with a QWeb report and a list/pivot view, giving marketing and finance a single reconciliation surface between analytics, the ad platform, and Odoo's own order data. Where you already push orders through the XML-RPC/JSON-RPC API from external systems, we expose a clean hook so those flows also emit conversions. We support Odoo 17.0, 18.0, and 19.0, and account for Community vs Enterprise differences (Enterprise's marketing-automation and subscription models get first-class event hooks where present).

Because this is build-to-order, nothing ships until we scope it with you. After a short scoping call we confirm your data layer, event taxonomy, consent requirements, and target Odoo version, then build, test on a staging instance with UAT and a rollback plan, and hand over installable source with a git repository and documentation. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); additional integrations (multiple ad/analytics platforms, server-side container hosting), multi-company or multi-website setups, and consent-mode/localization depth increase the quoted scope.