CONNECTIONS / WooCommerce / WooCommerce to X CAPI
From WooCommerce orders to the X Conversions API.
Signals reads your WooCommerce orders through scoped API access to WooCommerce, reading only your WooCommerce orders, then reports online sales to X server-side so campaigns keep measuring conversions so X sees web conversions without an export.
- ● woocommerce → x.capi :: live
- > read web_orders rows=38,919
- hash sha256(email,phone) consent=filtered
- route x deliver
- ✓ delivered · 33,081 matched
WHAT THIS ENABLES
WooCommerce to X Conversions API
X Conversions API for WooCommerce: Signals reports online sales to X server-side so campaigns keep measuring conversions straight from your WooCommerce orders, hashed and consent-screened as orders complete.
- Signals reports online sales to X server-side so campaigns keep measuring conversions, reading your WooCommerce orders as orders complete.
- Online sales still counted on X, with no export step out of your WooCommerce orders.
WHAT FLOWS WHERE
WooCommerce to X CAPI, mapped.
Each sync hands the on-site purchase and checkout events from your WooCommerce orders to Signals, which hashes and filters every record, then X's Conversions API logs the web conversions for hashed-email matching.
Each sync hands the on-site purchase and checkout events from your WooCommerce orders to Signals, which hashes and filters every record, then X's Conversions API logs the web conversions for hashed-email matching.
Built for the teams that own the number.
WordPress merchants running WooCommerce who need X conversions that persist after the browser signal fades out of WooCommerce orders.
From kickoff to verified events.
-
Connect
Scoped API access to WooCommerce, reading only your WooCommerce orders, mapped to X's Conversions API and tuned for hashed-email matching.
-
Map
Columns from your WooCommerce orders align to X's Conversions API in the visual mapper, hashed as each order syncs and checked for hashed-email matching.
-
Deliver
As orders complete, Signals reads your WooCommerce orders and reports online sales to X server-side so campaigns keep measuring conversions, sends only the orders that changed, with hashed-email matching watched in the debugger.
What ships with this use case.
X conversions that persist after the browser signal fades from your WooCommerce orders, delivered as orders complete.
Online sales still counted on X out of your WooCommerce orders, delivered as orders complete without API call volume climbing.
Match feedback on hashed-email matching from X's Conversions API each run, tied back to your WooCommerce orders.
What X CAPI actually receives.
- ● signals :: event payload
- > POST /conversion source=woocommerce.web_orders
- conversion_time 1784575228000
- identifiers [{ hashed_email: "9c04ef…" }]
- conversion_value 1761.00 · conversion_currency AED
- ✓ accepted · match=true
Adjacent moves on the same stack.
from WooCommerce
WooCommerce to Meta CAPI
Meta Conversions API for WooCommerce: Signals sends every browser checkout to Meta…
Learn morefrom WooCommerce
WooCommerce to Meta CTM
Meta Click-to-Message for WooCommerce: Signals credits orders that began in a WhatsApp or…
Learn more
same use case
BigCommerce to X CAPI
X Conversions API for BigCommerce: Signals reports online sales to X server-side so…
Learn moregeneric
X CAPI
Datahash implements X (Twitter) Conversions API with dedupe against the X Pixel and hashed…
Learn moreAsked on almost every call.
How often does the WooCommerce X CAPI sync run?
You set the cadence, from near-real-time to a nightly WooCommerce sync of your WooCommerce orders into X. Since Signals sends only the orders that changed, X conversions that persist after the browser signal fades keeps pace and WordPress merchants running WooCommerce watch hashed-email matching. One scoped connection sets it up, cadence adjustable later.
What match rate should a WooCommerce-sourced X 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 X; one missing both cannot. First-run feedback from Conversions API pinpoints hashed-email matching, the number WordPress merchants running WooCommerce tune against.
NEXT STEP