Google Ads Conversion Tracking for Odoo

ECOSIRE builds a dedicated Odoo module that closes this gap end to end. On the client side we inject the global site tag (gtag.js) through a QWeb template inheriting the website layout, so it loads on every storefront page — including the OWL-driven checkout steps — without you editing source on each deploy. Conversion IDs and labels live on res.config.settings, backed by ir.config_parameter, never hard-coded, so staging and production stay isolated. The heart of the build is a server-side event layer: we extend sale.order and the website_sale controller so that when an order is confirmed, a compute-derived, deduplicated purchase conversion is emitted with the real order total, currency, tax handling, and a stable order-reference transaction ID. This is measured against paid state, not a fragile thank-you-page render, so it survives ad blockers and page reloads.

Technically, the module is a proper addon: __manifest__.py declaring website_sale and sale dependencies, ORM models with @api.depends computed fields for conversion value, ir.model.access.csv plus record rules so tracking configuration is admin-only and organization-scoped, and XML/OWL views for the settings panel. We wire enhanced conversions (hashed, consent-gated email/phone) where you enable them, add optional server-to-server delivery via an automated action on state change, and expose a JSON-RPC/XML-RPC-safe method so headless or POS-adjacent flows can report conversions too. Multi-currency stores get per-order currency conversion; multi-website stores get per-site conversion labels. On Enterprise we can extend the same events into subscriptions and helpdesk-driven upsells; on Community everything runs on the standard eCommerce stack.

Delivery is build-to-order. After a short scoping call we confirm your Odoo version (17.0/18.0/19.0), Community vs Enterprise, which conversion actions matter (purchase, add-to-cart, lead, begin-checkout), and your consent and enhanced-conversions requirements. We build and test on a staging copy, run UAT with you against real Google Ads Tag Assistant traces, then install to production with a rollback plan and a git repo handover. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); additional integrations (server-side tagging endpoint, GA4 alignment, multi-website or multi-company conversion labels, and consent-platform depth) increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise on the invoice.