Facebook / Meta Pixel & Conversions API

Key Features

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

Per store-view / website scope configuration of Pixel ID, dataset ID and CAPI access token, supporting multi-brand and multi-region Magento installs

Dedicated admin configuration section under Stores > Configuration with ACL resources, so only authorized roles can view or edit the CAPI access token

Test Event Code support and structured logging so you can validate events in Meta Events Manager's Test Events tab during go-live

Graceful consent integration: events can be gated behind your cookie-consent / GDPR mechanism, with the server rail respecting the same opt-in signal

Access token stored using Magento's encrypted config (core_config_data with encrypted backend model), not in plain code or version control

Built as a clean module under app/code/Ecosire/MetaCapi with di.xml, events.xml and service contracts — upgrade-safe and free of core hacks

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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.

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.

What you get

Custom-built Magento 2 module (Ecosire_MetaCapi) installed under app/code on your Magento Open Source or Adobe Commerce instance

Configuration of your Meta Pixel ID, dataset ID and Conversions API access token wired to the correct store-view / website scopes

Browser pixel + server-side CAPI event mapping for the full purchase funnel, with event deduplication verified in Meta Events Manager

Advanced matching implementation with server-side SHA-256 hashing of customer identifiers

Dynamic Ads product catalog feed configured to your SKU / product-ID scheme (where Dynamic Ads are in scope)

Go-live validation using Meta's Test Events tool, plus a short admin handover document covering settings, the ACL role, and how to read the event logs

30 days of post-launch support covering bug fixes and tracking-accuracy issues on the delivered scope

Who this is for

Performance Marketer / Paid Social Lead

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.

Magento Store Owner / E-commerce Manager

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.

Magento Developer / Technical Lead

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.

How Facebook / Meta Pixel & Conversions API Compares

Criterion	ECOSIRE	Custom Build	Competitor
Server-side Conversions API (CAPI), not just the browser pixel	Included	Partial support	Partial support
Event deduplication via shared event_id across pixel and CAPI	Included	Partial support	Partial support
Server-side advanced matching with SHA-256 hashed identifiers	Included	Partial support	Included
Built, installed and supported on your specific Magento install	Included	Included	Not included
Tailored to your theme, one-step checkout and SKU/catalog scheme	Included	Included	Partial support
Async dispatch via Magento queues/cron so checkout never blocks	Included	Partial support	Partial support
Dynamic Ads catalog feed for retargeting	Included	Partial support	Included
Available instantly as a self-service download	Not included	Not included	Included

Frequently Asked Questions about Facebook / Meta Pixel & Conversions API

How long until it's live on my store, and is this an instant 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.

What ongoing support and updates are included?

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.

Does this send raw customer PII to Meta?

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.

Will server-side tracking and event deduplication cause double-counting in Meta?

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.

Does it work on Adobe Commerce as well as Magento Open Source, and across multiple store views?

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.