Facebook / Meta Pixel & Conversions API

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.