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

    CONNECTIONS / Odoo / Odoo to Meta Custom Audience

    Odoo sales opportunities into Meta, built for Meta lookalike and suppression seeds.

    Connect Odoo and point Signals at your Odoo sales opportunities; it keeps Meta audiences synced as adds and removals so lists never drift as records change, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    odoo -> meta-custom-audience :: live

    1. ● odoo → meta.audience :: live
    2. > read segments rows=17,468
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 14,673 matched

    WHAT THIS ENABLES

    Odoo to Meta Custom Audience

    Odoo to Meta Custom Audience: your Odoo sales opportunities, hashed and consent-checked, feed Meta as Signals keeps Meta audiences synced as adds and removals so lists never drift as records change.

    • Customer segments from your Odoo sales opportunities activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
    • Lookalike seeds and suppression lists that track your live customer base, drawn from your Odoo sales opportunities by operations teams running Odoo CRM.

    WHAT FLOWS WHERE

    Odoo to Custom Audience, mapped.

    Signals reads the customer segments from your Odoo sales opportunities; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    Signals reads the customer segments from your Odoo sales opportunities; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Performance teams running first-party suppression and lookalike seeds, with the records already in Odoo CRM leads, opportunities, and activities.

    Operations teams running Odoo CRM activating Meta lookalike and suppression seeds 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 Custom Audiences API, sized for audience refresh cadence.

    2. Map

      Signals reads your Odoo sales opportunities, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.

    3. Deliver

      On each run, Signals pulls your Odoo sales opportunities, keeps Meta audiences synced as adds and removals so lists never drift, and sends only the records that changed, with audience refresh cadence in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your Odoo sales opportunities and sends only the records that changed.

    Always-current lookalike seeds and exclusions from your Odoo sales opportunities, with API call volume steady because Signals sends only the records that changed.

    A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Odoo sales opportunities.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: odoo.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=odoo.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 17,468 · num_invalid_entries 151
    5. audience_id "1645381" · session "upsert"
    6. ✓ accepted match=84%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Odoo

    Odoo to Google Customer Match

    Odoo to Google Customer Match: your Odoo sales opportunities, hashed and consent-checked,…

    Learn more

    from Odoo

    Odoo to TikTok Custom Audience

    Odoo to TikTok Custom Audience: your Odoo sales opportunities, hashed and consent-checked,…

    Learn more

    same use case

    ActiveCampaign to Meta Custom Audience

    ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Custom Audience

    Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Odoo Meta Custom Audience 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, lookalike seeds and suppression lists that track your live customer base stays current while operations teams running Odoo CRM keep audience refresh cadence in view. Delivery needs no export and no manual upload.

    What match rate should a Odoo-sourced Meta Custom Audience 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 audience refresh cadence, which operations teams running Odoo CRM then raise inside your Odoo sales opportunities.

    NEXT STEP

    Odoo to Meta Custom Audience, in production this week.

    Talk to our team All Odoo use cases