Magento and Meta Ads: Enterprise E-commerce Advertising Guide

For Magento Open Source or Adobe Commerce, write down the installed version, patch level, payment module and enabled queue transport before designing a Meta integration. Store views, payment states and configurable products need explicit mappings. A thank-you page is not proof that payment was captured.

Versioned integration contract

Illustrative reference environment: a Magento 2.4.x installation with a custom integration module and a configured message-queue consumer. This is an architectural example, not code certified for every 2.4 release. Compare it with your exact installed release. Adobe’s message-queue framework documentation describes publishers and asynchronous consumers; supported transports and deployment configuration must match that release. A queue reduces synchronous work but still has latency and can fail.

Adobe’s invoice tutorial distinguishes receiving payment and creating an invoice for its example order. Define a paid-order predicate with your gateway: authorization alone, an invoice-save notification or order creation may not satisfy it. Handle partial capture explicitly rather than sending a whole-order Purchase for every invoice.

Worked consumer design

Synthetic order US:100042 has a fully captured USD 120 payment. In this illustrative design, emit one Purchase for a fully paid order, with ledger key US:100042:Purchase:v1. A later partial refund belongs to a separate accounting adjustment; it must not create a second purchase.

1. The observer persists a minimal order/store reference in durable work after the transaction is committed. Do not perform a remote advertising request in the checkout success-page controller.
2. The consumer loads current order and gateway payment evidence. If not fully captured under the declared policy, retain pending state and recheck through the supported payment-update path.
3. Within a transaction, claim the stable ledger key and freeze event time, order currency and value definition. Build the allowed Meta event payload; use the matching event name and identity in the browser when it represents that same purchase, through the browser integration’s supported eventID option rather than a server-only payload field.
4. Retry transient failures with the same key and payload. Separate terminal validation errors and dead-letter work for investigation. Reconcile captured orders against sent, suppressed, failed and pending rows after an outage.
5. Honor consent and permitted identity use. Do not put a customer group name in user_data as though it were a supported identity field. Segmentation belongs in a separately approved audience workflow.

Choose one consistent variant export

Use the Meta product item model to check API field names and types, then the installed exporter’s feed contract. Preview the exact color, size, price and stock at the destination. Do not export variants and then exclude all of them merely because their Magento standalone visibility is disabled.

Reconcile each market without demanding identical attribution

Maintain a store-view ledger containing order currency, captured amount, tax, shipping, refunds, reporting exchange rate and dataset/catalog mapping. Separate store views into datasets only when ownership, consent, operational separation and measurement justify it; a store view does not universally require a new Pixel.

Hypothetical reconciliation: the shop ledger has ten fully paid orders; a UTM session report associates six with this campaign; Meta attributes seven under its selected settings. Those figures are not automatically tracking defects. Compare click/view credit, reporting time zone, cross-device behavior, consent loss, repeat visits and conversion lag before debugging event counts. Advertising credit is not incremental lift.

Use mature net contribution to judge a customer-reactivation hypothesis, with a comparable holdout where feasible. Do not assume an AOV or reactivation uplift. After the store contract passes, prepare market-specific offer drafts in NovaStorm and review prices and budget limits. The queue, feed exporter and cross-market reconciliation remain outside that draft workflow.