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

    CONNECTIONS / Odoo / Odoo to Google Store Sales

    Odoo sales opportunities into Google Ads, built for Google Store Sales matching.

    Connect Odoo and point Signals at your Odoo sales opportunities; it matches in-person transactions to Google accounts as store-sales conversions as records change, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    odoo -> google-store-sales :: live

    1. ● odoo → google.sales :: live
    2. > read closed_deals rows=17,316
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 14,026 matched

    WHAT THIS ENABLES

    Odoo to Google Store Sales

    Odoo to Google Store Sales: your Odoo sales opportunities, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions as records change.

    • Offline and in-store sales from your Odoo sales opportunities activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
    • Counter and showroom revenue inside the same ROAS view as online orders, 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 Google, away from any pixel. Here is how Odoo closes the loop.

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

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, with the records already in Odoo CRM leads, opportunities, and activities.

    Operations teams running Odoo CRM activating Google Store Sales matching 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' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      Signals reads your Odoo sales opportunities, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.

    3. Deliver

      On each run, Signals pulls your Odoo sales opportunities, matches in-person transactions to Google accounts as store-sales conversions, and sends only the records that changed, with the store-sales match rate 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 Store Sales 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 Store Sales actually receives.

    signals :: odoo.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=odoo.closed_deals
    3. transaction_time 2026-07-21T13:02:19 · transaction_amount_micros 22355000000
    4. currency_code SAR
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=81%
    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 Meta Offline CAPI

    Odoo to Meta Offline CAPI: your Odoo sales opportunities, hashed and consent-checked, feed…

    Learn more

    same use case

    ActiveCampaign to Google Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Odoo Google Store Sales 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, counter and showroom revenue inside the same ROAS view as online orders stays current while operations teams running Odoo CRM keep the store-sales match rate in view. Delivery needs no export and no manual upload.

    What match rate should a Odoo-sourced Google Store Sales 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 store-sales match rate, which operations teams running Odoo CRM then raise inside your Odoo sales opportunities.

    NEXT STEP

    Odoo to Google Store Sales, in production this week.

    Talk to our team All Odoo use cases