CONNECTIONS / Wix / Wix to X CAPI
Your Wix Stores orders, wired to the X Conversions API.
Signals reads your Wix Stores orders through scoped API access to Wix, reading only your Wix Stores orders, then reports online sales to X server-side so campaigns keep measuring conversions so X sees web conversions without an export.
- ● wix → x.capi :: live
- > read web_orders rows=43,426
- hash sha256(email,phone) consent=filtered
- route x deliver
- ✓ delivered · 38,649 matched
WHAT THIS ENABLES
Wix to X Conversions API
Wix to X Conversions API: your Wix Stores orders, hashed and consent-checked, feed X as Signals reports online sales to X server-side so campaigns keep measuring conversions as orders complete.
- Signals reports online sales to X server-side so campaigns keep measuring conversions, reading your Wix Stores orders as orders complete.
- Online sales still counted on X, with no export step out of your Wix Stores orders.
WHAT FLOWS WHERE
Wix to X CAPI, mapped.
Each sync hands the on-site purchase and checkout events from your Wix Stores 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 Wix Stores 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.
Small merchants on Wix who need X conversions that persist after the browser signal fades out of Wix Stores orders.
From kickoff to verified events.
-
Connect
Scoped API access to Wix, reading only your Wix Stores orders, mapped to X's Conversions API and tuned for hashed-email matching.
-
Map
Columns from your Wix Stores 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 Wix Stores 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 Wix Stores orders, delivered as orders complete.
Online sales still counted on X out of your Wix Stores 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 Wix Stores orders.
What X CAPI actually receives.
- ● signals :: event payload
- > POST /conversion source=wix.web_orders
- conversion_time 1784364524000
- identifiers [{ hashed_email: "9c04ef…" }]
- conversion_value 2483.00 · conversion_currency AED
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Wix
Wix to Meta CAPI
Wix to Meta Conversions API: your Wix Stores orders, hashed and consent-checked, feed Meta…
Learn morefrom Wix
Wix to Meta CTM
Wix to Meta Click-to-Message: your Wix Stores orders, hashed and consent-checked, feed Meta…
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 Wix X CAPI sync run?
Delivery tracks Wix, run by small merchants on Wix: a near-real-time or scheduled sync of your Wix Stores orders feeds X on that cadence. Each run sends only the orders that changed, so online sales still counted on X holds up on hashed-email matching. The live debugger confirms every delivery inline.
What match rate should a Wix-sourced X CAPI batch expect?
Coverage of hashed identifiers across your Wix Stores orders decides it, and small merchants on Wix own that inside Wix. A live email or phone matches into X; neither, and it will not. First-run feedback flags hashed-email matching, which small merchants on Wix then raise inside your Wix Stores orders.
NEXT STEP