Facebook Conversions API for Odoo

ECOSIRE builds a dedicated integration that emits conversion events straight from your Odoo backend to Meta's Conversions API over the Graph endpoint, so events fire from your server regardless of what happens in the shopper's browser. Technically, we add a new configuration model (typically meta.capi.config) holding the dataset ID, encrypted access token, test-event code, and environment toggle, secured with ir.model.access.csv plus record rules so only marketing/admin roles can read the token. Business triggers — sale.order confirmation, crm.lead creation, website.visitor activity, POS orders, or e-commerce checkout steps — are wired through @api.depends computes and Odoo automated actions/server actions to build a normalized event log model. Customer identifiers (email, phone, external ID, city, zip) are SHA-256 hashed before they ever leave the instance, and each event carries an event_id so the same conversion sent by both the browser pixel and the server is deduplicated by Meta rather than double-counted. Delivery uses Odoo's outbound HTTP layer with retry/backoff, and every send is recorded with its Meta trace ID and HTTP response for auditing in a dedicated view.

The build maps cleanly onto Odoo's architecture: an event-log model (models.Model with state, fbtrace_id, payload_json, and a sent/failed lifecycle), OWL/XML backend views and a QWeb-friendly summary, a scheduled ir.cron to flush queued and retry failed events, and consent gating so events are suppressed when a contact has not granted marketing consent (respecting GDPR/data-use rules). We support Community and Enterprise on Odoo 17.0, 18.0, and 19.0 — noting that some triggers (e.g. subscription or certain marketing-automation hooks) exist only on Enterprise, and we scope around your edition. Optional pieces include Advanced Matching enrichment, offline/CRM event mapping, multi-pixel routing per company or per website, and a JSON-RPC/XML-RPC hook so external systems can push custom events through the same validated pipeline.

Because this is build-to-order, nothing ships until we have agreed the scope. After a short scoping call we confirm which Odoo events map to which Meta standard/custom events, your edition and version, and any multi-company or localization needs; you then receive a fixed quote and a delivery plan. Typical delivery is 2-4 weeks from confirmed scope, on a staging instance first, with UAT against Meta's Test Events tool before go-live. Pricing starts from $399 (indicative, single-company base scope); additional pixels/datasets, multi-company routing, offline-conversion and CRM event mapping, and heavier historical data backfill increase the quoted scope.