> ## Documentation Index
> Fetch the complete documentation index at: https://3fd5199-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://3fd5199-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://3fd5199-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://3fd5199-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Magento returning customer bidding in Meta (/docs/bidding/returning-customers/magento-meta)

<!-- agent-signals: reading_time_min: 9 · est_tokens: 3322 · updated: 2026-11-17 -->
Related: [Shopify returning customer bidding in Google Ads](/docs/bidding/returning-customers/shopify-google-ads.md), [WooCommerce returning customer bidding in Google Ads](/docs/bidding/returning-customers/woocommerce-google-ads.md), [Magento returning customer bidding in Google Ads](/docs/bidding/returning-customers/magento-google-ads.md), [Lightspeed returning customer bidding in Google Ads](/docs/bidding/returning-customers/lightspeed-google-ads.md), [Shopware returning customer bidding in Google Ads](/docs/bidding/returning-customers/shopware-google-ads.md), [Returning customer bidding in Google Ads on any website with Cloudflare](/docs/bidding/returning-customers/cloudflare-google-ads.md)

> Send repeat orders from Magento to Meta as PMReturningCustomer through the Meta Conversions API with Advanced Matching, and optimise a campaign on a custom conversion.

Each paid Magento order reaches Product Metrics, which checks the customer's history and, for **every repeat order** (not once per customer), sends the custom events **`PMReturningCustomer`** (the order's revenue) and **`PMReturningCustomerProfit`** (its profit) to your pixel through the Meta Conversions API. Meta can only optimise on a custom event through a **custom conversion**, which you create once. Each event carries hashed customer data for [Advanced Matching](/docs/tracking/enhanced-conversions/magento-meta), so Meta can match it to the person who clicked.



* **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:** Meta optimises on repeat orders through a custom conversion on `PMReturningCustomer`.

## 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 returning customer bidding 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 returning customer bidding 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

* **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).
* **For the profit event**, your additional costs must be active and the order's costs complete.

## In the app

### 1. Connect Magento and Meta

Your developer installs the module and adds one configuration file per store view ([Magento](/docs/platforms/magento)). Then add your **Pixel or Dataset ID** and a Conversions API access token under **Tracking → Meta Conversions API → Connect Meta** and send a test event ([Meta](/docs/channels/meta)).

Connect your store, step by step:



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)

Then add the Meta destination:



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; Meta accepted the test event.

### 2. Check how Magento decides returning customers

The Product Metrics module looks for an earlier paid order from the same customer **in the same store view**: by customer account, or by guest email. If it finds one, the customer is **returning**. If not, they are **new**.

* **Per store view.** Each store view is connected on its own, and history is read per store view. A customer who bought in one store view is new in another.
* **History stops at the order.** Only orders placed before this order was created count.
* **Cancelled orders don't count** as earlier orders.
* **No account and no email: unknown.** An order with neither is sent as **Product Metrics - Revenue** and **Product Metrics - Profit** only.

Check a few recent orders before you bid on them. Ask your assistant: "Were my last 20 Magento orders from new or returning customers?"

**You should see:** whether the order counts as new, returning or unknown.

### 3. Create the custom conversion

This step happens in Meta Events Manager.

1. Choose **Custom conversions → Create custom conversion** and select your pixel.
2. Choose the event **`PMReturningCustomer`** (or **`PMReturningCustomerProfit`** to optimise on profit).
3. Add the event parameter rule **`pm_purpose` equals `CUSTOMER_RETURNING`** (or `CUSTOMER_RETURNING_PROFIT`).
4. Choose **Purchase** as the category. Use the event's value and currency; leave the fixed conversion value unset.



> **Warning:** Meta lists an event only after it has received it once. Custom events need **marketing and analytics consent**, so place a test order with both accepted in OneTrust, Cookiebot, Usercentrics or Osano.

In the same store view, place a second paid order with the same customer account or guest email. Use a test event code to see it under **Test events**, then remove the code.

**You should see:** the custom conversion is listed under **Custom conversions** in Events Manager.

### 4. Optimise your campaign on it

In your retention campaign, choose the returning customer custom conversion as the conversion event and optimise on its value. Meta then gives buyers who look like your repeat customers higher priority.

**You should see:** the ad set's conversion event is your returning customer custom conversion.

### 5. Check it works

1. **Classification.** The order check from step 2 shows your test order as returning. Magento sends orders through cron, so allow a few minutes after payment.
2. **Event.** In Events Manager, **`PMReturningCustomer`** arrives with `pm_purpose` = `CUSTOMER_RETURNING` and `customer_type` = `RETURNING`.
3. **Custom conversion.** It shows activity after the next repeat order.
4. **Delivery.** **Tracking → Meta Conversions API** says **Meta destination saved**, and **Sending** reads **On** without "Test mode".

## How it works on Magento

|                                  | On Magento                                                                                              |
| -------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Where the history comes from** | Same store view, account or guest email                                                                 |
| **Sent for**                     | Every paid order after the first                                                                        |
| **Meta event (`pm_purpose`)**    | `PMReturningCustomer` (`CUSTOMER_RETURNING`), `PMReturningCustomerProfit` (`CUSTOMER_RETURNING_PROFIT`) |
| **Value**                        | The order's revenue, or its profit; a loss is sent as 0                                                 |
| **Refunds**                      | Later refunds don't change the event                                                                    |
| **Past orders**                  | Not imported; Meta rejects events older than 7 days                                                     |

## Troubleshooting

| Problem                                       | Fix                                                                                                                                                |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Orders count as neither new nor returning** | Product Metrics could not tell from the order history (step 2). Those orders still go to Meta as revenue and profit, just not as new or returning. |

## FAQ

### Is a customer from one Magento store view returning in another?

No. History is read per store view, so their first order in another store view isn't sent as `PMReturningCustomer`.

### Does a cancelled earlier order make a customer returning?

No. Cancelled orders don't count as earlier orders.

### Why can't I select PMReturningCustomer in Events Manager yet?

Meta lists `PMReturningCustomer` only after it has received it once, and custom events need **marketing and analytics consent**. Place a test order with both accepted in OneTrust, Cookiebot, Usercentrics or Osano.

### Does a refund remove the PMReturningCustomer event?

No. A later refund doesn't change `PMReturningCustomer` or `PMReturningCustomerProfit` in Meta.

## Where next



* [Returning customer bidding](/docs/features/returning-customer-bidding): the feature on every platform and channel
* [Returning customer bidding on Magento in Google Ads](/docs/bidding/returning-customers/magento-google-ads): the same feature on the other channel
* [New customer bidding on Magento in Meta](/docs/bidding/new-customers/magento-meta): the other side of the split
* [Magento](/docs/platforms/magento): set-up and troubleshooting
* [Meta](/docs/channels/meta): set-up and troubleshooting
* [New and returning customers](/docs/concepts/new-and-returning-customers): how a customer is recognised
* [Conversion values](/docs/concepts/conversion-values): what each conversion carries

On the website: [repeat purchase rate](https://www.productmetrics.io/glossary/repeat-purchase-rate), [LTV-adjusted ROAS](https://www.productmetrics.io/glossary/ltv-adjusted-roas), [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).
