Marketing teams running an Odoo eCommerce site keep hitting the same wall: the ad platform reports thin, unreliable signal because browser-side pixel snippets pasted into the website theme fire inconsistently, miss the real cart value, and break every time the storefront template or product page layout changes. Odoo core ships a basic tracking-ID field under Website settings, but it does not emit properly structured ViewContent, AddToCart, InitiateCheckout, or Purchase events with the product content_ids, value, and currency that ad optimization and catalog matching actually depend on. Without those, lookalike audiences, dynamic product ads, and return-on-ad-spend reporting all run half-blind.

ECOSIRE builds you a made-to-order Odoo module that wires standard eCommerce events into your shop the way the ad platform documents them. On the front end it injects the pixel base code and a normalized dataLayer push through QWeb templates that inherit the website shop, product, and category views (website_sale.products, website_sale.product), so events fire on the exact DOM points your theme actually renders — product impressions on category/collection pages, ViewContent on the product detail page, AddToCart on the cart button, InitiateCheckout at /shop/checkout, and Purchase on the confirmation page. Server-side, an Odoo model (models.Model) reads the confirmed sale.order and its order_line records to compute the authoritative purchase value and line-item contents via @api.depends computed fields, rather than trusting a number scraped from the page. Product identifiers are mapped to your catalog reference (internal reference / barcode / product.template id) so they match your product feed.

Because thin browser signal is now the norm, the build includes an optional server-to-server Conversions API path: a controller and queued job hash customer identifiers (email, phone) with SHA-256, attach the event ID for browser/server deduplication, and post to the graph endpoint using credentials stored in ir.config_parameter. Consent handling, test-event codes, and per-event enable/disable are exposed as res.config.settings fields under Website configuration, with access controlled through ir.model.access.csv and record rules so only marketing admins can edit pixel credentials. Everything is delivered as a clean, upgrade-safe module with its own __manifest__.py, no monkey-patching of core, and full support for Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise (Enterprise adds nothing mandatory here — this runs on Community website/eCommerce).

Delivery is build-to-order: we start with a short scoping call to confirm your Odoo version, theme, which events matter, whether you need the Conversions API, and your consent/GDPR posture. We then build on a staging copy of your database, run UAT against real test events using the platform's Test Events tool, and only deploy to production once you sign off — with a rollback plan and the git repository handed to you. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); adding the server-side Conversions API, multi-website or multi-company storefronts, deep consent-management integration, or a heavily customized theme increases the quoted scope.