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

    CONNECTIONS / WooCommerce / WooCommerce to Google OCI

    From WooCommerce orders to Google Ads offline conversion import.

    Signals reads your WooCommerce orders through scoped API access to WooCommerce, reading only your WooCommerce orders, then reconciles closed-won revenue to the Google Ads click through GCLID so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    woocommerce -> google-oci :: live

    1. ● woocommerce → google.oci :: live
    2. > read closed_deals rows=73,026
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 59,151 matched

    WHAT THIS ENABLES

    WooCommerce to Google Offline Conversions

    Google Offline Conversions for WooCommerce: Signals reconciles closed-won revenue to the Google Ads click through GCLID straight from your WooCommerce orders, hashed and consent-screened as orders complete.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your WooCommerce orders as orders complete.
    • A clean line from click to closed revenue, with no export step out of your WooCommerce orders.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Order sync recorded in WooCommerce S Signals hash · dedupe Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, working out of WooCommerce orders, customers, and subscriptions.

    WordPress merchants running WooCommerce who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy out of WooCommerce orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to WooCommerce, reading only your WooCommerce orders, mapped to Google Ads' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your WooCommerce orders align to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed as each order syncs and checked for GCLID coverage.

    3. Deliver

      As orders complete, Signals reads your WooCommerce orders and reconciles closed-won revenue to the Google Ads click through GCLID, sends only the orders that changed, with GCLID coverage watched 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 OCI 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 WooCommerce records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: woocommerce.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=woocommerce.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-22T11:38:43"
    5. conversion_value 26128 · currency_code SAR
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from WooCommerce

    WooCommerce to Google Store Sales

    Google Store Sales for WooCommerce: Signals matches in-person transactions to Google…

    Learn more

    from WooCommerce

    WooCommerce to Meta Offline CAPI

    Meta Offline CAPI for WooCommerce: Signals credits dealer, branch, and phone sales to the…

    Learn more

    same use case

    ActiveCampaign to Google OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the WooCommerce Google OCI sync run?

    You set the cadence, from near-real-time to a nightly WooCommerce sync of your WooCommerce orders into Google Ads. Since Signals sends only the orders that changed, Smart Bidding trained on booked revenue instead of a mid-funnel proxy keeps pace and WordPress merchants running WooCommerce watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

    What match rate should a WooCommerce-sourced Google OCI batch expect?

    Match rate follows identifier coverage in your WooCommerce orders, which WordPress merchants running WooCommerce control, not WooCommerce itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Offline Conversion Import (Google Ads API) pinpoints GCLID coverage, the number WordPress merchants running WooCommerce tune against.

    NEXT STEP

    WooCommerce to Google OCI, in production this week.

    Talk to our team All WooCommerce use cases