> ## Documentation Index
> Fetch the complete documentation index at: https://c1ae7e1-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://c1ae7e1-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://c1ae7e1-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://c1ae7e1-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: 9 · est_tokens: 3566 · updated: 2026-11-17 -->
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).



* **Store:** [Magento](/docs/platforms/magento). The module, installed once by a developer.
* **Channel:** [Meta](/docs/channels/meta). Your pixel ID and a Conversions API access token.
* **Result:** Every paid order sent to your pixel through the Meta Conversions API.

## Set it up with AI



Setting it up with AI takes one prompt and 60 seconds: paste it 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."

## 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).
* **Your Magento store view connected**: Magento 2.4, 2.0 or 1.9 / OpenMage, Magento Admin access, the public HTTPS shop address and the **store-view ID**, and a **developer** with access to your server who installs the Product Metrics module (Composer or ZIP), adds the store view's private configuration file and keeps Magento cron running. The connection reads **Active** before you link your property. See [Magento](/docs/platforms/magento).
* **Access to your pixel in Meta Events Manager**, to copy its ID and generate a Conversions API access token.

## 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).



1. **Open Ecommerce platforms.** Go to **Integrations → Ecommerce platforms** and select **Connect** on **Magento**.

   ![Ecommerce platforms under Integrations, listing the supported store platforms with a Connect button on Magento.](/docs/_assets/5d48e2070be161722db01c31447901650ce87360fe351da6c9b68b7a7e3157ef)

2. **Start the setup.** The Magento page lists three steps: connect your store, install the module and link a property. Select **Connect Magento**.

   ![The Magento page under Integrations → Ecommerce platforms, for Magento 1.9 and 2: 0 of 3 steps done, step 1 Connect your store with the Connect Magento button, then Install the module and Link a property.](/docs/_assets/559ef5687b68660aa29f64600cebe006fdab68ae079bbeeabe7863c7310e5295)

3. **Describe your store.** Choose your **Magento version**, enter the **Store URL** and the numeric **Store view ID**, then select **Create module configuration**. Download the configuration file and share it with your developer privately: it holds a private key.

   ![The Connect Magento dialog: Magento version set to Magento 2, a closed Advanced custom checkout mapping section, empty Store URL and Store view ID fields, and the Cancel and Create module configuration buttons.](/docs/_assets/d99894bd7f20dcd4ce41dfb8621390e9fe26c10fac65787229e88e2beb744927)

4. **Install the module.** Your developer installs the module. Select **Setup guide** and choose your Magento version and installation method: it walks your developer through installing the module and verifying the connection.

   ![The Magento setup guide panel, set to Magento 2.4, Composer and Technical: Download Word document, Magento version tabs 2.4, 2.0 (legacy) and 1.9 / OpenMage, Installation method Composer or ZIP upload, Guide mode Technical or Descriptive, and the start of Before you begin.](/docs/_assets/d83f2d5ced412764df7f8fd7031968b5d460ac70ebb88c3e476574a4d122cf53)

**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).



1. **Open Tracking.** Go to **Integrations → Tracking**. Under **Destinations**, select **Meta Conversions API**.

2. **Open the Meta panel.** The panel lists the events Product Metrics sends and what you need: a **Pixel or Dataset ID** and a Conversions API access token from Events Manager. Select **Connect Meta**.

   ![The Meta Conversions API panel, Not configured: Product Metrics sends AddToCart, InitiateCheckout and Purchase from the server to your Meta pixel, with hashed customer data when the shopper consented to marketing, plus revenue, profit, new and returning customer, and LTV events, which also need analytics consent. You need a Pixel or Dataset ID and a Conversions API access token from Events Manager. A Connect Meta button.](/docs/_assets/588444f715d3715f2be502402cee6218f721840965f4655380f205de3a834a9f)

3. **Add the Meta destination.** Choose the store, enter the **Pixel or Dataset ID** and the **Access token**, and optionally a **Test event code**. Keep **Send events to Meta** on and select **Add destination**.

   ![The Add Meta destination dialog for the example store Northwind Outfitters: empty Pixel or Dataset ID, Access token and Test event code (optional) fields, each with where to find it in Events Manager, the Send events to Meta switch on, and the Cancel and Add destination buttons.](/docs/_assets/a946724528c7a47f16adc5a3c1fd5e75b1f9b498c20142415a3e07e2cf4f656e)

   *Example data.*

4. **Create custom conversions in Meta.** In Events Manager, create a custom conversion for each Product Metrics event you want to measure, using the event names listed in the panel.

   ![The Set up custom conversions in Meta section of the Meta Conversions API panel: the steps in Events Manager, then a table of each conversion and its event: New customer revenue PMNewCustomer, New customer profit PMNewCustomerProfit, Returning customer revenue PMReturningCustomer, Returning customer profit PMReturningCustomerProfit and Order revenue PMOrderRevenue.](/docs/_assets/8d13436ae8d16e27fcb8fb31e6e842bead9c4d5d6afdb6dcd0b921af7e846079)

**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).



1. **Open Tracking.** Go to **Integrations → Tracking**. The checklist shows six steps: start by connecting your store, or use Cloudflare Tracking if you have no store platform.

   ![Tracking in Product Metrics with the Complete your tracking setup checklist of six steps, starting with Connect your store.](/docs/_assets/09a584afb1797a0439b68310c4d6085412eafebba1524c019f42a90f3ed4ea37)

2. **Follow the next step.** Once your store is connected and linked, the checklist opens the next open step. Each step says what it does.

   ![The Complete your tracking setup checklist in Tracking: 3 of 6 essential steps completed, with Connect your store, Link the store to this property and Install storefront tracking ticked, and Configure consent open as step 4 with the consent platform still Not configured.](/docs/_assets/b385237058280a34dca53f7f1e42704faa9a8aee59024bd5baafc2211e201e7e)

3. **Configure consent.** Under **Configure consent**, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.

   ![The Configure consent step in the tracking checklist, with the list of consent platforms to choose from.](/docs/_assets/f0a8d61eaa086657ce840c85899df48d5f3a7a52fb6c552710f93b1482b90e72)



> **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

|                                    | 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

| Problem                                                  | Fix                                                                                                                             |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **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).
