CONNECTIONS / WooCommerce / WooCommerce to Meta Offline CAPI
From WooCommerce orders to Meta's offline optimization.
Signals reads your WooCommerce orders through scoped API access to WooCommerce, reading only your WooCommerce orders, then credits dealer, branch, and phone sales to the Meta campaigns behind them so Meta sees offline conversions without an export.
- ● woocommerce → meta.capi :: live
- > read closed_deals rows=50,488
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 39,886 matched
WHAT THIS ENABLES
WooCommerce to Meta Offline CAPI
Meta Offline CAPI for WooCommerce: Signals credits dealer, branch, and phone sales to the Meta campaigns behind them straight from your WooCommerce orders, hashed and consent-screened as orders complete.
- Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your WooCommerce orders as orders complete.
- Campaign learning fed by real-world purchases, with no export step out of your WooCommerce orders.
The click, the conversion, and the credit.
The conversion happens off Meta, 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 in-store and phone revenue joining Meta's optimization loop out of WooCommerce orders.
From kickoff to verified events.
-
Connect
Scoped API access to WooCommerce, reading only your WooCommerce orders, mapped to Meta's Offline Conversions API and tuned for Meta's 62-day event window.
-
Map
Columns from your WooCommerce orders align to Meta's Offline Conversions API in the visual mapper, hashed as each order syncs and checked for Meta's 62-day event window.
-
Deliver
As orders complete, Signals reads your WooCommerce orders and credits dealer, branch, and phone sales to the Meta campaigns behind them, sends only the orders that changed, with Meta's 62-day event window 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 Offline CAPI 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 Offline CAPI actually receives.
- ● signals :: event payload
- > POST /offline_conversions source=woocommerce.closed_deals
- event_name "Purchase" · event_time 2026-07-16T03:47:17
- value 35992.00 · currency USD
- em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-58637"
- ✓ accepted match=79%
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 morefrom WooCommerce
WooCommerce to Google Store Sales
Google Store Sales for WooCommerce: Signals matches in-person transactions to Google…
Learn more
same use case
ActiveCampaign to Meta Offline CAPI
ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…
Learn moreAsked on almost every call.
How often does the WooCommerce Meta Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly WooCommerce sync of your WooCommerce orders into Meta. Since Signals sends only the orders that changed, in-store and phone revenue joining Meta's optimization loop keeps pace and WordPress merchants running WooCommerce watch Meta's 62-day event window. One scoped connection sets it up, cadence adjustable later.
What match rate should a WooCommerce-sourced Meta Offline CAPI 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 Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number WordPress merchants running WooCommerce tune against.
NEXT STEP