CONNECTIONS / WooCommerce / WooCommerce to Google Store Sales
From WooCommerce orders to Google Store Sales matching.
Signals reads your WooCommerce orders through scoped API access to WooCommerce, reading only your WooCommerce orders, then matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.
- ● woocommerce → google.sales :: live
- > read closed_deals rows=19,820
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 15,856 matched
WHAT THIS ENABLES
WooCommerce to Google Store Sales
Google Store Sales for WooCommerce: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your WooCommerce orders, hashed and consent-screened as orders complete.
- Signals matches in-person transactions to Google accounts as store-sales conversions, reading your WooCommerce orders as orders complete.
- Store visits reconciled to campaign spend, with no export step out of your WooCommerce orders.
The click, the conversion, and the credit.
The conversion happens off Google, away from any pixel. Here is how WooCommerce closes the loop.
Built for the teams that own the number.
WordPress merchants running WooCommerce who need counter and showroom revenue inside the same ROAS view as online orders out of WooCommerce orders.
From kickoff to verified events.
-
Connect
Scoped API access to WooCommerce, reading only your WooCommerce orders, mapped to Google Ads' Store Sales Direct API and tuned for the store-sales match rate.
-
Map
Columns from your WooCommerce orders align to Google Ads' Store Sales Direct API in the visual mapper, hashed as each order syncs and checked for the store-sales match rate.
-
Deliver
As orders complete, Signals reads your WooCommerce orders and matches in-person transactions to Google accounts as store-sales conversions, sends only the orders that changed, with the store-sales match rate watched in the debugger.
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 WooCommerce records the event. |
What Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=woocommerce.closed_deals
- transaction_time 2026-07-19T19:26:18 · transaction_amount_micros 18247000000
- currency_code GBP
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=80%
Adjacent moves on the same stack.
from WooCommerce
WooCommerce to Google OCI
Google Offline Conversions for WooCommerce: Signals reconciles closed-won revenue to the…
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 Store Sales
ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Google Store Sales
Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…
Learn moreAsked on almost every call.
How often does the WooCommerce Google Store Sales 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, counter and showroom revenue inside the same ROAS view as online orders keeps pace and WordPress merchants running WooCommerce watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.
What match rate should a WooCommerce-sourced Google Store Sales 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 Store Sales Direct API pinpoints the store-sales match rate, the number WordPress merchants running WooCommerce tune against.
NEXT STEP