CONNECTIONS / Magento
Magento orders, matched across every ad platform.
Magento's built-in Google and Meta extensions cover pixel tracking for orders placed through the default checkout. Signals adds server-side delivery to every platform you buy on, credit memo refunds reconciled against the original order, and hashed audiences from your customer segments.
- ● magento :: signals live
- > Order placed value=356.00 EUR
- > Quote converted step=payment
- hash sha256(email,phone) pii=cleared
- route meta · google · tiktok · snap · x
- ✓ 5 destinations synced · match 79%
The signal Magento yields.
Every kind of signal that moves between Magento and the platforms, through one hashed, deduplicated route.
- Web conversions
- Every sales_order_placed and checkout_started event, on Magento Open Source or Adobe Commerce, reaches Meta, Google, TikTok, Snap, and X server-side, deduped against whichever pixel is already installed.
- Offline conversions
- B2B quotes converted to orders, and in-store or phone sales entered through the admin, post as offline conversions matched by hashed identifier instead of a click.
- Custom audiences
- A credit memo is reconciled against the original order so reported revenue reflects what was actually kept, not what was briefly charged.
Pick your platform. Every use case for it, in one place.
Every way Magento data moves, grouped by platform and ranked by how many use cases Magento supports.
Google 4 
Meta 4 
Snap 3 
TikTok 3 
LinkedIn 2 
OpenAI 2 
Pinterest 1 
Reddit 1 
X 1 - Web conversions Google Enhanced Conversions Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Web conversions Meta Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Web conversions Meta Messenger Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Web conversions Snapchat Conversions API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Web conversions TikTok Events API Web events delivered as conversions, matched with hashed identifiers.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
From authorization to delivered signal.
-
Install
Signals module added via Composer to Magento Open Source or Adobe Commerce, with a scoped integration token covering order, quote, and customer events.
-
Map
Sales order, checkout, and customer events mapped to each destination's event or audience schema in the visual mapper, including B2B quotes and credit memos where they apply.
-
Hash and dedupe
Identifiers hashed with SHA-256 and deduped against any existing pixel or tag before anything leaves Magento.
-
Deliver
Server-side delivery to every mapped destination, verified in the live debugger before campaigns rely on it.
Magento questions, answered.
Do we remove Magento's native Meta and Google extensions?
No. Keep them for basic pixel coverage on the default checkout. Signals adds server-side delivery to every platform you buy on, credit memo reconciliation, and audience sync on top, deduped against whatever pixel is already installed so nothing double counts.
Does this work with both Magento Open Source and Adobe Commerce?
Yes. Capture reads from the standard sales order and quote event stream available in both editions, whether the instance is self-hosted Magento Open Source or running on Adobe Commerce Cloud infrastructure, so the same mapping and destinations apply either way.
We run multiple stores and websites on one Magento instance. Supported?
Yes. Events carry the store and website scope, so each storefront can route its orders, checkouts, and customer events to its own destinations and ad accounts instead of one shared feed, even when every storefront shares a single Magento instance and catalog.
How does Magento B2B fit into this, with quote-based orders?
A converted B2B quote fires the same order-placed event as a standard retail order, so negotiated wholesale purchases reach the same destinations as consumer checkouts once the quote becomes an order, with the negotiated value carried through instead of a list price.
Do refunds and credit memos get reported back to ad platforms?
Where a destination supports it, yes. A credit memo is reconciled against the original order so reported revenue reflects what was actually kept, not what was briefly charged, whether it is issued in full, as a partial refund, or against a return processed weeks later.
NEXT STEP
See your Magento data working in every ad platform.
Ready to enable a use case, or still mapping what Magento data could do? Our team helps you find the right place to start.
