Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / Odoo / Odoo to Meta Offline CAPI

    Odoo sales opportunities into Meta, built for Meta's offline optimization.

    Connect Odoo and point Signals at your Odoo sales opportunities; it credits dealer, branch, and phone sales to the Meta campaigns behind them as records change, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    odoo -> meta-offline-capi :: live

    1. ● odoo → meta.capi :: live
    2. > read closed_deals rows=48,035
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 38,428 matched

    WHAT THIS ENABLES

    Odoo to Meta Offline CAPI

    Odoo to Meta Offline CAPI: your Odoo sales opportunities, hashed and consent-checked, feed Meta as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them as records change.

    • Offline and in-store sales from your Odoo sales opportunities activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, drawn from your Odoo sales opportunities by operations teams running Odoo CRM.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Meta, away from any pixel. Here is how Odoo closes the loop.

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta CRM record sync recorded in Odoo S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, with the records already in Odoo CRM leads, opportunities, and activities.

    Operations teams running Odoo CRM activating Meta's offline optimization straight from Odoo sales opportunities.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Odoo, reading only your Odoo sales opportunities to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      Signals reads your Odoo sales opportunities, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your Odoo sales opportunities, credits dealer, branch, and phone sales to the Meta campaigns behind them, and sends only the records that changed, with Meta's 62-day event window in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same Offline CAPI reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment Odoo records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: odoo.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=odoo.closed_deals
    3. event_name "Purchase" · event_time 2026-07-14T03:40:06
    4. value 34038.00 · currency GBP
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-48406"
    6. ✓ accepted match=80%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Odoo

    Odoo to Google OCI

    Odoo to Google Offline Conversions: your Odoo sales opportunities, hashed and…

    Learn more

    from Odoo

    Odoo to Google Store Sales

    Odoo to Google Store Sales: your Odoo sales opportunities, hashed and consent-checked, feed…

    Learn more

    same use case

    ActiveCampaign to Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Odoo Meta Offline CAPI sync run?

    The pace follows your Odoo sales opportunities: Signals sends changes from Odoo to Meta as records change. Because it sends only the records that changed, in-store and phone revenue joining Meta's optimization loop stays current while operations teams running Odoo CRM keep Meta's 62-day event window in view. Delivery needs no export and no manual upload.

    What match rate should a Odoo-sourced Meta Offline CAPI batch expect?

    Coverage of hashed identifiers across your Odoo sales opportunities decides it, and operations teams running Odoo CRM own that inside Odoo. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags Meta's 62-day event window, which operations teams running Odoo CRM then raise inside your Odoo sales opportunities.

    NEXT STEP

    Odoo to Meta Offline CAPI, in production this week.

    Talk to our team All Odoo use cases