> ## Documentation Index
> Fetch the complete documentation index at: https://e328d4e-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://e328d4e-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://e328d4e-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://e328d4e-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Magento server-side tracking with the Meta Conversions API (/docs/tracking/server-side/magento-meta)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1860 · updated: 2026-11-16 -->
Related: [Shopify server-side tracking for Google Ads](/docs/tracking/server-side/shopify-google-ads.md), [WooCommerce server-side tracking for Google Ads](/docs/tracking/server-side/woocommerce-google-ads.md), [Magento server-side tracking for Google Ads](/docs/tracking/server-side/magento-google-ads.md), [Lightspeed server-side tracking for Google Ads](/docs/tracking/server-side/lightspeed-google-ads.md), [Shopware server-side tracking for Google Ads](/docs/tracking/server-side/shopware-google-ads.md), [Server-side tracking for Google Ads on any website with Cloudflare](/docs/tracking/server-side/cloudflare-google-ads.md)

> Send every purchase from your Magento store view to Meta from the server through the Meta Conversions API, with Advanced Matching and the script served from your own domain.

Each purchase is confirmed from **your Magento orders** and sent to your Meta pixel [from the server](/docs/concepts/server-side-tracking), through the **Meta Conversions API**. Nothing in the browser talks to Meta, so an [ad blocker](/docs/features/ad-blocker-proof-tracking) has nothing to block. Each event carries hashed customer data for [Advanced Matching](/docs/tracking/enhanced-conversions/magento-meta).

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking).
* **Magento 2.4, 2.0 or 1.9 / OpenMage**, a **developer** with terminal access to the server, Magento cron running, and the **store-view ID** and public HTTPS address of the store view you track.
* **Access to your pixel in Meta Events Manager**, to copy its ID and generate a Conversions API access token.

## Set it up with AI



Paste the prompt into your assistant.



First connect the Product Metrics MCP server ([https://www.productmetrics.io/mcp](https://www.productmetrics.io/mcp); see [Connect your assistant](/docs/mcp/connect)).

**Claude or ChatGPT:** "Set up server-side conversion tracking for my Magento store in Meta with Product Metrics. Check my setup status first, walk me through each open step, and give me the link when I need to click something."

**Claude Code or Codex:** "Set up server-side conversion tracking for my Magento store in Meta with Product Metrics. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first), and tell me when a step needs me in a browser."

## In the app

### 1. Connect Magento and Meta

* **Store:** create the module configuration under **Ecommerce platforms → Connect Magento**, have your developer install the module, then verify the store view and link it to your property. See [Magento](/docs/platforms/magento).
* **Meta:** in Events Manager, copy your **Pixel or Dataset ID** and generate a Conversions API access token, then add both under **Tracking → Meta Conversions API → Connect Meta** and send a test event. See [Meta](/docs/channels/meta).



![The Add Meta destination form with Pixel or Dataset ID, Access token, Test event code (optional) and the Send events to Meta switch, then the saved Meta Conversions API destination showing Active, the access token Accepted by Meta and Sending On.](/docs/_assets/b8f3701ffab8399a9aad9788c63abe4161115d01a029732731a74012315454bb)

*Figure: Add Meta destination: paste the Pixel or Dataset ID and access token, keep Send events to Meta on.*

**You should see:** under **Manage Magento**, the connection is **Active** and your property is linked; Events Manager shows the test event under **Test events**.

### 2. Choose your consent banner

In Product Metrics, open **Tracking → Configure consent** and choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. **Magento's own cookie restriction notice does not grant consent.** With any other banner, your developer passes the visitor's choices to Product Metrics; anything not set stays denied. See [Consent](/docs/concepts/consent).



> **Warning:** Meta has no consent mode. Product Metrics sends an event only when the visitor allowed ad user data; the custom events also need analytics consent. A wrong banner here means nothing reaches Meta.

**You should see:** **Configure consent** names the banner your store view actually shows.

### 3. Create custom conversions

In Events Manager, create a custom conversion for each Product Metrics value you want to bid on, with the rule `pm_purpose` equals the purpose: `PMOrderRevenue` (`ORDER_REVENUE`) for revenue, `PMOrderProfit` (`ORDER_PROFIT`) for profit, every other event in [Meta events](/docs/concepts/conversion-actions-and-events#meta-events). Follow [Create custom conversions in Meta](/docs/using/conversion-actions#custom-conversions-in-meta) once a test order has reached Meta.

**You should see:** your custom conversions show in Events Manager.

### 4. Check it works

**Place a paid test order** in the connected store view with your payment provider's test mode, and allow a few minutes for cron.

**You should see:** under **Manage Magento**, the desired and active revision numbers are the same, and the order appears for the linked property; in Events Manager, the order shows as `Purchase`, plus the Product Metrics custom events your visitor's consent allows. More checks: [Check tracking works](/docs/using/check-tracking).



**How it works on Magento**

* **Script and collector served by:** The Product Metrics module, on its own paths of your store domain, set for each store view by the module's configuration file. Nothing loads from another domain and there is no script tag
* **Purchase confirmed from:** Your Magento orders
* **Sent:** When the order is paid; the module sends changes every two minutes through cron
* **Delivered:** Server-side, through the Meta Conversions API: `Purchase` plus the Product Metrics custom events
* **Refunds and cancellations:** Sent events aren't revised. Meta refuses events more than 7 days old
* **Consent read from:** OneTrust, Cookiebot, Usercentrics or Osano, or your own banner, passed on by your developer

## Troubleshooting

### The event isn't in Meta's custom conversion selector

Meta lists an event only after it received it. Place a test order with all cookies accepted, then create the custom conversion.

## FAQ

### Do I need a developer to send Magento orders to Meta?

Once, to install the Product Metrics module and make sure Magento cron runs. Connecting Meta and creating custom conversions happen in Product Metrics and Events Manager.

### How quickly does a paid Magento order reach Meta?

The module sends order changes every two minutes through Magento cron. Mark orders paid within 7 days: Meta refuses older events.

### Does Magento's cookie notice give consent for Meta?

No. Magento's cookie restriction notice does not grant consent, and Meta has no consent mode. Without a supported banner, or your developer passing your banner's choices, nothing reaches Meta.

### Are Magento refunds sent to Meta?

No. Sent Meta events aren't revised, so a refund or cancellation in Magento doesn't change them.

## Where next

* [Magento](/docs/platforms/magento): the full platform setup
* [Meta](/docs/channels/meta): what Product Metrics sends and how to troubleshoot it
* [Server-side tracking for Magento in Google Ads](/docs/tracking/server-side/magento-google-ads): the same store view, the other channel
* [Meta Conversions API on Magento](/docs/tracking/enhanced-conversions/magento-meta): the customer data each event carries
* [Server-side conversion tracking](/docs/features/ad-blocker-proof-tracking): every platform and channel
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [ad blocker conversion tracking check](https://www.productmetrics.io/ad-blocker-conversion-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie), [Product Metrics for Magento](https://www.productmetrics.io/platforms/magento)

Developers: do the same with the [CLI](/docs/cli/commands#destinations) or the [API](/docs/api/destinations/set-meta).
