Meta Conversions API on Magento 2: server-side setup that matches what Meta counts in 2026

TL;DR

Server-side events from Magento are still worth sending, and the addon that sends them has not changed shape. What changed is the ruler. Two Meta counting updates in 2026 rewrote which conversions appear in reporting, and one of them fails quietly [1]. So a Magento merchant looking at a lower Purchase count this spring has two candidate explanations, and the reporting one is more likely than the plumbing one. This article covers what the addon actually sends, how to verify it end to end with test mode and the log file, and where the honest limits are on deduplication.

Key Takeaways

• The January 12, 2026 Marketing API change removed the 7-day and 28-day view windows, capped unique metrics at 13 months, and capped frequency at 6 months [1]. Deprecated windows return empty data, not an error, so dashboards and scripts break silently.
• The March 3, 2026 change redefined click-through as genuine link clicks and moved engagement into a separate "engage-through" bucket with a fixed 1-day window [2]. Two different definitions of a click now exist in the same account history.
• weltpixel/module-ga4-metass sends Purchase, Add Payment Info, Initiate Checkout, Add To Cart, Add To Wishlist, Search, View Content, and View Category from the Magento server [3].
• The addon requires GA4 PRO 1.14.9 or higher plus a configured client-side Meta Pixel, and it installs independently of the TikTok, Reddit, or Klaviyo addons [3].
• Meta's deduplication rule requires event_id paired with event_name across browser and server [4]. Verify deduplication in Events Manager.
• Installation is Composer-only since v1.16.0 (January 7, 2026) [3]. Older instructions that tell you to copy files into app/code describe a path that no longer applies.
• Match parameters improved release by release: email and phone on purchases in v1.15.9, hashed email, phone, and address persisted for returning customers in v1.16.1 [3].

What Meta changed about counting in 2026

Two dated changes, one in January and one in March.

The first landed on January 12, 2026, announced in a Meta for Developers post on October 16, 2025 [1]. The Insights API stopped supporting 7-day view and 28-day view attribution windows. Unique metrics are capped at a 13-month lookback and frequency metrics at 6 months. The part that catches teams out is the failure mode: a request for a removed window comes back with empty data rather than an error response. A nightly export that used to pull 28-day-view purchases now pulls zero of them and reports zero with no warning.

The second landed on March 3, 2026 [2]. Click-through attribution now means a genuine link click. Engagement that used to be folded into click-through moved into a separate bucket called engage-through, on a fixed 1-day window. Ad sets that were credited under the old definition are credited differently under the new one, which means a year-over-year comparison in Ads Manager is comparing two different definitions of the same word. The Shopify-side write-up goes deeper on how the click-through reclassification reshapes attribution.

Neither of those is a Magento problem. Both of them change what a Magento merchant sees, and the mechanics are identical regardless of which platform is sending the events.

Why did your Magento conversions move when nothing on your server changed?

You have probably already been through this loop: the Purchase count in Ads Manager drops, someone asks whether the server-side integration broke, and an afternoon disappears into logs that turn out to be fine.

Work the order of elimination from the reporting side inward, because the reporting side is where the 2026 changes are.

Start by checking whether the number you are comparing comes from a deprecated window. If any part of your stack requests 7-day view or 28-day view, that part is now returning empty and dragging your totals down. Next, check whether the metric is a click-through metric that spans March 3. If it is, the two halves of the series are not comparable and no amount of server-side work will reconcile them.

Only after those two are ruled out does it make sense to look at whether events are actually arriving. That part is verifiable in a few minutes, and the next sections cover how.

What the Meta CAPI addon actually sends from Magento

The addon is weltpixel/module-ga4-metass, released November 14, 2024, and it runs on Magento 2.3.0 through 2.4.9 [3]. It builds on GA4 PRO: it requires version 1.14.9 or higher and a client-side Meta Pixel already configured, because the addon adds the server-side half of a pair [3]. It installs independently of the other platform addons, so running Meta server-side does not commit you to running the TikTok Events API addon as well.

Eight events are available to send from the server [3]:

Configuration is a short list. You supply the pixel ID, which Meta surfaces as the Dataset ID in Events Manager under Data Sources → Settings → Dataset ID [3], and a Conversions API access key. There is a setting to send the same events via the frontend as well, a test mode with a test event code, a customer-group filter for excluding wholesale or staff groups, and multi-property support for stores that report into more than one Meta asset [3]. Server-side events also inherit the shared behavior of the GA4 PRO addon family: the order-status exclusion list with cron catch-up, so an order that leaves an excluded status later still gets pushed, and the grand-total settings that decide whether tax and shipping are included in the value you send.

Match parameters improved release by release [3]. Version 1.15.9 added email and phone to purchase events. Version 1.16.1 persisted hashed email, phone, and address so returning customers carry identifiers on later events [3]. A separate fix made the addon read the visitor's real IP when the store sits behind a CDN, which matters because the CDN's own IP is worthless for matching. A v1.15.7 fix made the addon send product_group as the content_type for configurable products, which Meta requires; product was sent before [3].

Meta does not publish an Event Match Quality threshold, so any score target circulating in forums is not a Meta benchmark.

How do the browser pixel and the server events avoid double counting?

This is the question where it is easy to blur two separate facts, so here they are separately.

Meta's rule has not changed: Meta deduplicates a browser event and a server event when both carry the same event_name and the same event_id [4]. That is Meta's documented requirement for anyone sending both.

Our addon's documentation says Meta Events Manager should have built-in functionality to avoid data duplication, and it does not document an event_id implementation. If you switch on the "send via frontend too" option, confirm deduplication in Events Manager against your own Purchase volume before you trust the totals.

One related fix is worth knowing because it looks like a duplication problem and is not. Version 1.16.0 fixed a bug where an unhandled response code 100 from the Meta API caused the same event to be processed more than once; events are now processed once on a successful API response [3]. If you are running an older addon build and seeing that code in your logs, upgrade before you start rearchitecting anything.

Verifying the pipe before you trust the numbers

Three artifacts tell you whether events left Magento, and all three are on your own server or in your own admin.

Test mode. Enable it, paste the test event code from Events Manager, and place a test order. Events tagged with that code are marked as test events and appear in the Test Events section of Events Manager [3]. This is the fastest way to answer "did anything leave the server at all". Remember to disable test mode when you finish testing [3].

The log file. The addon writes to meta-api.log. That file holds the request and the response for each server-side send, so an authentication failure, a rejected payload, and a silence each look different in the log.

The admin payload viewer. Since version 1.15.11 the payloads are readable from the Magento admin [3]. On a managed host where you do not have shell access, this is the difference between debugging the integration yourself and opening a ticket.

Run all three in order once. After that, the log file alone is usually enough.

Does your Magento version affect any of this?

Yes, though less than people expect, and mostly through Content Security Policy.

Magento 2.4.9 shipped May 12, 2026 [5]. Its Google Analytics module CSP whitelist is now independent of the Adwords module, and 2.4.8 had already allowed region1.analytics.google.com when Google Analytics is enabled, which had been generating CSP errors for EU visitors. Payment pages have run CSP in restrict mode since 2.4.7 for PCI DSS 4.0 (other pages stay in report-only mode). If a browser-side pixel stops firing after an upgrade, CSP is the first place to look, and the server-side events will keep flowing throughout because they never touch the browser.

There is a newer patching detail that has not filtered into most Magento content yet. Adobe now ships monthly isolated security patches between the numbered -pN releases. These are security-only and non-cumulative, and they are sequential, which means order matters: the August 11, 2026 critical patch requires the July 2026 patch to be applied first [6]. If your upgrade routine assumes patches are cumulative, that assumption is now wrong. Our guide on updating Magento 2 and installing security patches covers the mechanics.

One more version note, this one about setup instructions. Installation has been Composer-only since v1.16.0 on January 7, 2026 [3]. Any walkthrough that has you copying files into app/code/WeltPixel/GA4MetaSS predates that change, including the setup half of our own earlier article, How to integrate Magento 2 with the Meta Pixel Conversions API. Read that one for the configuration walkthrough and use Composer for the install step.

FAQ

Do I still need the browser pixel if the addon sends events server-side?

Yes. The addon requires a configured client-side Meta Pixel as a prerequisite, and it adds server-side sending alongside it [3]. If you send from both, confirm deduplication in Events Manager, since Meta's documented rule requires matching event_id and event_name values on the pair [4].

Why did my 28-day view conversions go to zero in January?

Because the Insights API stopped supporting 7-day view and 28-day view attribution windows on January 12, 2026, and those requests now come back empty [1]. Any report or export that hardcoded those windows now returns nothing for them. Check what window your reporting requests before investigating your Magento setup.

Which Magento versions does the Meta CAPI addon support?

Magento 2.3.0 through 2.4.9, with GA4 PRO 1.14.9 or higher as a prerequisite [3]. The addon's changelog introduced Magento 2.4.9 and PHP 8.5 compatibility in v1.17.0 [3].

Where do I find the pixel ID and the access key?

Both come from Meta Events Manager. The pixel ID appears there as the Dataset ID, and the Conversions API access key is generated in the same place. The access key is a long string. Paste it once and move on.

Does the addon work without the other WeltPixel platform addons installed?

Yes. Each platform addon is a separate Composer package that depends on GA4 PRO and its own client-side pixel, and the addons do not depend on each other [3]. You can run Meta server-side alone.

If you are running Magento 2 and want the server-side half of your Meta setup handled inside the admin rather than in a separate tagging server, the Google Analytics 4 PRO extension with server-side tracking is the base the Meta Conversions API addon installs on top of.

The one thing worth doing this week regardless of which tooling you use: open your reporting and find out whether anything in it still asks Meta for a 7-day or 28-day view window. That request has been returning empty since January 12.

Sources

1. Meta for Developers blog, October 16, 2025, announcing the January 12, 2026 Marketing API attribution and metric-lookback changes.
2. Meta, March 3, 2026 change to click-through attribution and the introduction of the engage-through bucket with a fixed 1-day window.
3. WeltPixel Meta Pixel Conversions API Addon, user guide and changelog (addon released November 14, 2024; versions cited as of GA4 PRO v1.17.3, August 3, 2026). https://docs.weltpixel.com/MetaPixelAddon/User-Guide-WeltPixel-Meta-Pixel-Addon.html
4. Meta for Developers, "Handling Duplicate Pixel and Conversions API Events." https://developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events/
5. Adobe Experience League, Adobe Commerce 2.4.9 release notes (released May 12, 2026). https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/adobe-commerce/2-4-9
6. Adobe security bulletin APSB26-92, August 11, 2026, and Adobe Commerce knowledge base article ka-40380 on isolated security patches.