Marketing teams running Odoo Website want reliable audience tracking so they can retarget visitors, build lookalike audiences, and measure ad ROI — but Odoo core gives you no place to drop a Facebook Pixel. You end up pasting raw script tags into individual page headers or a website-wide <head> snippet, which is fragile: the pixel fails to load on some templates, PageView fires inconsistently across QWeb-rendered pages, and there is no clean way to add structured events (ViewContent, AddToCart, Purchase, Lead) that map to real Odoo actions. Consent handling and multi-website setups make the hand-pasted approach even messier, and every Odoo upgrade risks silently breaking the snippet.

We build a dedicated Odoo module that manages your Facebook Pixel properly. The pixel ID lives in a configuration model (extending res.config.settings, stored on res.company for per-company/per-website control) instead of being hard-coded, so marketers can update it without a developer. The module injects the base pixel loader and a guaranteed PageView event via a QWeb template inherited into the website <head> layout, so tracking fires consistently on every front-end page regardless of the template used. On top of the base PageView, we wire event hooks to genuine Odoo events — for example ViewContent on product/course pages, AddToCart and InitiateCheckout on eCommerce flows, Purchase on confirmed sale orders, and Lead/CompleteRegistration on website form submissions — each firing with the right parameters (value, currency, content IDs) sourced from the ORM.

Technically, the module ships a clean __manifest__.py declaring dependencies (website, plus website_sale when eCommerce events are in scope), config fields via a compute/inverse pattern where needed, and ir.model.access.csv entries so only appropriate users can edit pixel settings. Front-end injection is done through template inheritance rather than brittle in-page scripts, and event payloads are rendered server-side or passed to a small OWL/JS asset so values stay accurate. Where you want deduplicated server-side signals, we can add a Conversions API relay from Odoo using the JSON-RPC/automated-actions layer. We respect consent state, support multi-website and multi-company routing of different pixel IDs, and build for your exact Odoo version — Community or Enterprise, 17.0, 18.0, or 19.0 — accounting for the front-end asset-bundle differences between them.

Because this is build-to-order, delivery follows a short scoping call, a fixed written quote, then development against your confirmed event list, UAT on a staging database, and go-live with a support window. Typical delivery is one working week from confirmed scope, depending on how many events and integrations you need. Pricing starts from $999 (indicative, single-company base scope); additional event mappings, eCommerce and Conversions API relay, multi-website/multi-company pixel routing, and consent-mode depth increase the quoted scope. You receive the full source code and git repository for your version — nothing is locked behind a black box.