A build-to-order Magento 2 extension that fires the Meta Pixel in the browser AND sends server-side events through the Conversions API, with advanced matching and event deduplication for ad-block-resistant, accurate attribution. One-time license from $99.00 USD for Magento 2 / Adobe Commerce (build-to-order) — includes 12 months of updates and support.
A build-to-order Magento 2 extension that fires the Meta Pixel in the browser AND sends server-side events through the Conversions API, with advanced matching and event deduplication for ad-block-resistant, accurate attribution.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Signal loss from iOS App Tracking Transparency, browser ad-blockers, and cookie restrictions quietly erodes your Meta ad attribution — the events your pixel should report never reach Meta, so ROAS looks worse than it is and the algorithm optimizes on starved data. This build-to-order Magento 2 extension closes that gap by running tracking on two redundant rails: the standard browser Meta Pixel plus server-side events through Meta's Conversions API (CAPI), with event deduplication (shared event_id) so Meta counts each conversion exactly once.
Dual-rail tracking: browser Meta Pixel plus server-side Conversions API (CAPI) for the same events, so ad-blockers and iOS ATT no longer silently drop conversions
Event deduplication via a shared event_id and event_name on both the pixel and CAPI payloads, so Meta counts each Purchase exactly once
Server-side advanced matching: email, phone, first/last name, city, state, zip and country normalized and SHA-256 hashed before transmission — raw PII never leaves your server
Full e-commerce event mapping wired to native Magento events via observers: ViewContent, AddToCart, InitiateCheckout, AddPaymentInfo and Purchase with correct value, currency and content_ids
Dynamic Ads (DPA) support with a generated product catalog feed keyed to your SKU / product-ID scheme for catalog retargeting
Asynchronous CAPI dispatch through Magento message queues and cron, so a slow or failing Meta Graph API call never blocks checkout or page render
ECOSIRE builds this as a proper module under app/code/Ecosire/MetaCapi — not a copy-paste snippet. Browser events ride a RequireJS component; server events are dispatched from Magento observers on native events (checkout_onepage_controller_success_action, controller_action_predispatch, catalog_controller_product_view) into a CAPI client service that posts to Meta's Graph API, queued through Magento message queues / cron so a slow Meta response never blocks checkout. Advanced matching hashes customer email, phone, first/last name and address with SHA-256 server-side — never sending raw PII. Full e-commerce event mapping covers ViewContent, AddToCart, InitiateCheckout, AddPaymentInfo and Purchase with correct value, currency and content_ids. Dynamic Ads are supported via a product catalog feed keyed on your SKU/product-ID scheme for retargeting.
It works on Magento Open Source and Adobe Commerce, respects multi-store/website scopes, and exposes settings through a dedicated admin section guarded by ACL. Because it's built to order, ECOSIRE matches it to your theme, checkout (including one-step checkout extensions), and dataset ID — then installs and supports it on your install. This is an honest engagement with a real delivery lead time, not an instant Marketplace download.
Runs Meta ad campaigns and watches reported ROAS drift below real ROAS as iOS ATT and ad-blockers eat pixel events. Needs server-side CAPI with deduplication so Meta optimizes on complete conversion data, without waiting on a dev backlog.
Owns a Magento Open Source or Adobe Commerce store and wants accurate Purchase tracking and Dynamic Ads retargeting without risking checkout stability or hand-editing theme files for every tag change.
Wants tracking implemented as a clean upgrade-safe module — observers, di.xml, ACL, queues — rather than inline scripts in templates, so it survives Magento upgrades and passes code review. Hands the build to ECOSIRE to save sprint capacity.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Facebook / Meta Pixel & Conversions API 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Facebook / Meta Pixel & Conversions API,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Server-side Conversions API (CAPI), not just the browser pixel | ||||
| Event deduplication via shared event_id across pixel and CAPI | ||||
| Server-side advanced matching with SHA-256 hashed identifiers | ||||
| Built, installed and supported on your specific Magento install | ||||
| Tailored to your theme, one-step checkout and SKU/catalog scheme | ||||
| Async dispatch via Magento queues/cron so checkout never blocks | ||||
| Dynamic Ads catalog feed for retargeting | ||||
| Available instantly as a self-service download |
No — this is build-to-order, not an instant Adobe Commerce Marketplace download. ECOSIRE builds the module to your install, then installs and validates it. Typical delivery is about 5 to 10 business days from when we have access and your Meta dataset ID / access token, depending on how many checkout customizations (e.g. one-step checkout extensions) and Dynamic Ads scope are involved. You get a firm timeline before we start.
Delivery includes 30 days of post-launch support for bug fixes and tracking-accuracy issues on the delivered scope. Because the module is built cleanly under app/code with di.xml, observers and service contracts, it is upgrade-safe across Magento patch releases. If Meta changes the Conversions API version or you need new events, store scopes or catalog feeds later, ECOSIRE can handle that as a scoped follow-up — your code is yours and fully documented at handover.
No. Advanced matching identifiers (email, phone, name, address) are normalized and SHA-256 hashed server-side before they are sent through the Conversions API, per Meta's requirements. Raw personal data never leaves your server unhashed. Events can also be gated behind your existing cookie-consent / GDPR mechanism so the server rail only fires on opted-in traffic.
No. The browser pixel and the CAPI server event for the same action share an identical event_id and event_name, which is exactly how Meta's deduplication works — Meta sees both and counts the conversion once. We verify this in Meta Events Manager's Test Events and Diagnostics during go-live so you can confirm there is no inflation before you scale spend.
Yes. The module targets both Magento Open Source and Adobe Commerce and respects Magento's website / store-view scoping, so you can configure a different Pixel ID, dataset ID and access token per brand or region. CAPI dispatch runs asynchronously through Magento's message queues and cron, so it does not block checkout regardless of edition or traffic volume.
A build-to-order Magento 2 extension that fires the Meta Pixel in the browser AND sends server-side events through the Conversions API, with advanced matching and event deduplication for ad-block-resistant, accurate attribution.