Facebook Pixel Integration for Odoo

Name: Facebook Pixel Integration for Odoo
Brand: ECOSIRE
SKU: facebook-pixel-integration

Key Features

Pixel ID stored in configuration (`res.config.settings` backed by `res.company`), editable by marketers with no code changes

Base pixel loader plus guaranteed `PageView` event injected via QWeb template inheritance into the website `<head>` layout

Consistent firing across all front-end pages regardless of QWeb template, avoiding per-page snippet drift

`ViewContent` events on product, course, or content pages with `content_ids`, value, and currency sourced from the ORM

eCommerce events — `AddToCart`, `InitiateCheckout`, `Purchase` — wired to real `website_sale` and confirmed `sale.order` flows

`Lead` / `CompleteRegistration` events on website form and contact submissions

Multi-website and multi-company routing so different sites can carry distinct pixel IDs

Optional Conversions API server-side relay from Odoo via JSON-RPC / automated actions for deduplicated signals

Consent-aware loading so the pixel respects the visitor's cookie/consent state

`ir.model.access.csv` and record rules restricting who can view or edit pixel configuration

Standard vs advanced matching options with careful handling of user data fields

Version-correct front-end asset bundling for Odoo 17.0 / 18.0 / 19.0, Community or Enterprise

Debug/test mode toggle so you can validate events in the browser event tester before go-live

Clean `__manifest__.py` with explicit dependencies, upgrade-safe so it survives Odoo point releases

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2–4 weeks from confirmed scope, depending on how many events and integrations you need. Pricing starts from $249 (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.

What you get

Installable module source code built for your exact Odoo version (17.0 / 18.0 / 19.0, Community or Enterprise)

Installation and configuration on your environment, with pixel ID and event mappings wired to your live flows

Technical documentation covering models, config fields, template inheritance points, and event payloads

User guide plus a live training session for your marketing/admin team

UAT on a staging database with the Facebook event tester, plus a documented rollback plan

Post-go-live support window for defect fixes and configuration adjustments

Full git repository handover so you own and can extend the code

Who this is for

Marketing / Growth Lead

Runs paid social and needs reliable PageView and conversion signals from the Odoo website to power retargeting, lookalike audiences, and accurate ad ROI reporting — without begging IT to re-paste a script every quarter.

eCommerce Manager

Operates an Odoo `website_sale` store and needs AddToCart, InitiateCheckout, and Purchase events firing with correct value and currency so campaign optimization and ROAS measurement actually work.

Odoo Administrator / IT Owner

Wants pixel tracking implemented as a proper, upgrade-safe module with access controls and version compatibility, rather than fragile inline snippets that break on the next Odoo upgrade.

Digital Agency / Consultant

Manages the client's Odoo site and needs a documented, handed-over module with a git repo they can maintain and extend across multiple websites or companies.

How Facebook Pixel Integration for Odoo Compares

Criterion	ECOSIRE	Custom Build	Competitor
Delivery model	Built to your scope, installed and supported by us	Built once by an in-house/freelance dev	Instant download, generic build
Pixel configuration	Marketer-editable config on `res.company`, no code	However the dev chose to store it	Usually a settings field, generic
Event coverage	PageView plus your chosen ORM-wired events	Only what you brief and pay for	Fixed event set, may not map to your flows
Odoo version fit	Built for your exact 17/18/19, Community or Enterprise	Depends on the developer	Targets common versions, edition gaps possible
Upgrade safety	Template inheritance, clean manifest, upgrade-friendly	Varies with code quality	Varies, vendor-dependent
Support & ownership	Support window plus full git repo handover	You own it, you maintain it	Vendor support, no source ownership typically
Consent & multi-site	Consent-aware, multi-website/company routing optional	Only if scoped and built	Limited or single-pixel
Cost profile	From $249 indicative, fixed quote after scoping	High dev time and QA cost	Low sticker price, generic fit

Frequently Asked Questions about Facebook Pixel Integration for Odoo

How long does delivery take?

This is a build-to-order module, so it is built after you request a quotation. Typical delivery is 2–4 weeks from confirmed scope, depending on how many events and integrations (base PageView only, full eCommerce events, Conversions API relay, multi-website routing) you need. The exact timeline is confirmed in your written quote after the scoping call.

Is this an existing app I can download right now?

No. We do not sell an instant download. ECOSIRE builds the module to your requirements and your Odoo version, then installs and configures it on your environment. You receive the full source code and git repository at handover.

How does pricing and scoping work?

Pricing starts from $249 (indicative, single-company base scope covering pixel injection and PageView). After a short scoping call we send a fixed written quote. Additional event mappings, eCommerce and Conversions API relay, multi-website/multi-company pixel routing, and consent-mode depth increase the quoted scope — there is no firm fixed price until scope is confirmed.

What about support and future Odoo upgrades?

Every build includes a post-go-live support window for defect fixes and configuration tweaks. Because the module is delivered as a proper addon with a clean manifest and template inheritance (not inline snippets), it is upgrade-friendly; we can quote a separate migration if you later move to a newer Odoo major version.

Which Odoo versions and editions do you support?

We build for Odoo 17.0, 18.0, and 19.0, in both Community and Enterprise. We account for the front-end asset-bundle and website-layout differences between versions so the pixel and events fire correctly on your specific setup.

Can it track eCommerce conversions, not just page views?

Yes. Beyond the base PageView, we can wire structured events — ViewContent, AddToCart, InitiateCheckout, and Purchase — to real Odoo `website_sale` and `sale.order` flows, with value, currency, and content IDs pulled from the ORM. For deduplicated server-side signals we can add a Conversions API relay from Odoo.

Do you handle consent and multiple websites?

Yes. The pixel can be made consent-aware so it respects the visitor's cookie/consent state, and multi-website / multi-company setups can route distinct pixel IDs per site. Both are scoping options confirmed in your quote.