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

    CONNECTIONS / Odoo / Odoo to Google Customer Match

    Odoo sales opportunities into Google Ads, built for Google Customer Match.

    Connect Odoo and point Signals at your Odoo sales opportunities; it projects your segments into Google Ads as Customer Match lists as records change, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    odoo -> google-customer-match :: live

    1. ● odoo → google.match :: live
    2. > read segments rows=22,672
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 19,498 matched

    WHAT THIS ENABLES

    Odoo to Google Customer Match

    Odoo to Google Customer Match: your Odoo sales opportunities, hashed and consent-checked, feed Google Ads as Signals projects your segments into Google Ads as Customer Match lists as records change.

    • Customer segments from your Odoo sales opportunities activated for Google Ads, as Signals projects your segments into Google Ads as Customer Match lists.
    • Customer Match lists that add joiners and drop lapsed members each sync, drawn from your Odoo sales opportunities by operations teams running Odoo CRM.

    WHAT FLOWS WHERE

    Odoo to Customer Match, mapped.

    Signals reads the customer segments from your Odoo sales opportunities; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    Signals reads the customer segments from your Odoo sales opportunities; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Growth teams feeding Google audiences from governed first-party data, with the records already in Odoo CRM leads, opportunities, and activities.

    Operations teams running Odoo CRM activating Google Customer Match 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 Google Ads' Customer Match API, sized for the serving-size threshold.

    2. Map

      Signals reads your Odoo sales opportunities, and its columns map to Google Ads' Customer Match API in the visual mapper, hashed and checked for the serving-size threshold.

    3. Deliver

      On each run, Signals pulls your Odoo sales opportunities, projects your segments into Google Ads as Customer Match lists, and sends only the records that changed, with the serving-size threshold in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Customer Match lists that add joiners and drop lapsed members each sync on every run, as Signals reads your Odoo sales opportunities and sends only the records that changed.

    Lists that self-maintain across syncs from your Odoo sales opportunities, with API call volume steady because Signals sends only the records that changed.

    A per-run match report from Google Ads' Customer Match API on the serving-size threshold, straight out of your Odoo sales opportunities.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: odoo.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=odoo.segments
    3. operation ADD · user_list "segment_71837"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 22,672 · members_matched 19,498
    6. ✓ accepted match=86%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Odoo

    Odoo to Meta Custom Audience

    Odoo to Meta Custom Audience: 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 Google Customer Match

    ActiveCampaign to Google Customer Match: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Google Customer Match

    Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Odoo Google Customer Match sync run?

    The pace follows your Odoo sales opportunities: Signals sends changes from Odoo to Google Ads as records change. Because it sends only the records that changed, Customer Match lists that add joiners and drop lapsed members each sync stays current while operations teams running Odoo CRM keep the serving-size threshold in view. Delivery needs no export and no manual upload.

    What match rate should a Odoo-sourced Google Customer Match 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 Google Ads; neither, and it will not. First-run feedback flags the serving-size threshold, which operations teams running Odoo CRM then raise inside your Odoo sales opportunities.

    NEXT STEP

    Odoo to Google Customer Match, in production this week.

    Talk to our team All Odoo use cases