CONNECTIONS / Magento / Magento to X CAPI
Your Magento orders, wired to the X Conversions API.
Connect Magento and point Signals at your Magento orders; it reports online sales to X server-side so campaigns keep measuring conversions as orders complete, hashed and consent-checked for X.
- ● magento → x.capi :: live
- > read web_orders rows=32,227
- hash sha256(email,phone) consent=filtered
- route x deliver
- ✓ delivered · 23,848 matched
WHAT THIS ENABLES
Magento to X Conversions API
Magento to X Conversions API: Signals reads your Magento orders and reports online sales to X server-side so campaigns keep measuring conversions, hashed and consent-checked as orders complete.
- On-site purchase and checkout events from your Magento orders activated for X, as Signals reports online sales to X server-side so campaigns keep measuring conversions.
- X conversions that persist after the browser signal fades, drawn from your Magento orders by merchants on Adobe Commerce (Magento).
WHAT FLOWS WHERE
Magento to X CAPI, mapped.
Signals reads the on-site purchase and checkout events from your Magento orders; Signals hashes and consent-screens each record before X's Conversions API accepts the web conversions for hashed-email matching.
Signals reads the on-site purchase and checkout events from your Magento orders; Signals hashes and consent-screens each record before X's Conversions API accepts the web conversions for hashed-email matching.
Built for the teams that own the number.
Merchants on Adobe Commerce (Magento) activating the X Conversions API straight from Magento orders.
From kickoff to verified events.
-
Connect
Scoped API access to Magento, reading only your Magento orders to feed X's Conversions API, sized for hashed-email matching.
-
Map
Signals reads your Magento orders, and its columns map to X's Conversions API in the visual mapper, hashed and checked for hashed-email matching.
-
Deliver
On each run, Signals pulls your Magento orders, reports online sales to X server-side so campaigns keep measuring conversions, and sends only the orders that changed, with hashed-email matching in the debugger.
What ships with this use case.
X conversions that persist after the browser signal fades on every run, as Signals reads your Magento orders and sends only the orders that changed.
Online sales still counted on X from your Magento orders, with API call volume steady because Signals sends only the orders that changed.
A per-run match report from X's Conversions API on hashed-email matching, straight out of your Magento orders.
What X CAPI actually receives.
- ● signals :: event payload
- > POST /conversion source=magento.web_orders
- conversion_time 1784672003000
- identifiers [{ hashed_email: "9c04ef…" }]
- conversion_value 4290.00 · conversion_currency SAR
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Magento
Magento to Meta CAPI
Magento to Meta Conversions API: Signals reads your Magento orders and sends every browser…
Learn morefrom Magento
Magento to Meta CTM
Magento to Meta Click-to-Message: Signals reads your Magento orders and credits orders that…
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 Magento X CAPI sync run?
You set the cadence, from near-real-time to a nightly Magento sync of your Magento orders into X. Since Signals sends only the orders that changed, X conversions that persist after the browser signal fades keeps pace and merchants on Adobe Commerce (Magento) watch hashed-email matching. One scoped connection sets it up, cadence adjustable later.
What match rate should a Magento-sourced X CAPI batch expect?
In Magento, match rate tracks the email and phone quality your Magento orders carry. Clean identifiers land for X; blank ones never will. The first Conversions API report shows merchants on Adobe Commerce (Magento) where hashed-email matching needs work, a data-quality task handled in Magento.
NEXT STEP