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

# Magento lifetime value (LTV) bidding in Meta (/docs/bidding/ltv/magento-meta)

<!-- agent-signals: reading_time_min: 7 · est_tokens: 2743 · updated: 2026-11-16 -->
Related: [Shopify lifetime value (LTV) bidding in Google Ads](/docs/bidding/ltv/shopify-google-ads.md), [WooCommerce lifetime value (LTV) bidding in Google Ads](/docs/bidding/ltv/woocommerce-google-ads.md), [Magento lifetime value (LTV) bidding in Google Ads](/docs/bidding/ltv/magento-google-ads.md), [Lightspeed lifetime value (LTV) bidding in Google Ads](/docs/bidding/ltv/lightspeed-google-ads.md), [Shopware lifetime value (LTV) bidding in Google Ads](/docs/bidding/ltv/shopware-google-ads.md), [Lifetime value (LTV) bidding in Google Ads on any website with Cloudflare](/docs/bidding/ltv/cloudflare-google-ads.md)

> Send each customer's lifetime revenue and profit from Magento to Meta through the Meta Conversions API with Advanced Matching, and optimise on it.

With every paid order of a recognised Magento customer, Product Metrics sends **`PMRevenueLTV`** and **`PMProfitLTV`** to your Meta pixel. Each carries **what this order adds** to the customer's lifetime value, with the running total as `pm_cumulative_ltv` ([Conversion values](/docs/concepts/conversion-values)). 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 lifetime value through a custom conversion on `PMRevenueLTV` or `PMProfitLTV`.

## Prerequisites

* **[Editor or admin](/docs/using/team#1-choose-a-role)** on the property in Product Metrics, 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 your Magento store view and Meta

Your developer installs the Product Metrics module, then you verify the store view and link it to your property ([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)). From then on, Product Metrics sends `PMRevenueLTV` and `PMProfitLTV` on its own.



![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. Check your Magento store view recognises customers

Ask your assistant: "Are my last five Magento orders from new or returning customers?" A guest who later orders with an account starts again under their account.

**You should see:** whether your test order's customer was recognised, as new or returning.

### 3. Set consent and costs

In **Tracking → Configure consent**, choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. With another banner, your developer passes the visitor's choices to Product Metrics. Magento's own cookie restriction notice grants nothing: without a supported banner or your developer passing the choices, visitors count as not having consented, and their customers get no lifetime value. Meta has no consent mode: the LTV events are only sent when the visitor allowed both **analytics** and **ad user data**. See [Consent](/docs/concepts/consent).

For Profit LTV, product costs come from the cost stored on each Magento order item, read when the order currency matches the base currency. Shipping, handling, returns and payment fees come from your [additional costs](/docs/using/costs): activate them under **Tracking → Add your additional costs**. Refunded orders are sent without a profit figure.



> **Note:** Revenue LTV needs no costs. Profit LTV is only sent while the order's costs are known, and the running total only while every earlier order's costs are known too.

**You should see:** **Configure consent** names the banner your Magento store view actually shows, and the **Profit tracking** section says your additional costs are active.

### 4. Create a custom conversion on PMRevenueLTV or PMProfitLTV

This step happens in Meta. An LTV event only appears in Meta's selector after Meta has received one, so first place a test order with consent accepted (and your costs active, for `PMProfitLTV`).

1. In Events Manager, choose **Custom conversions → Create custom conversion**.
2. Select your pixel and the event `PMRevenueLTV` (or `PMProfitLTV`).
3. Add the event parameter rule `pm_purpose` equals `CUSTOMER_REVENUE_LTV` (or `CUSTOMER_PROFIT_LTV`).
4. Choose **Purchase** as the category. Use the event's value and currency; leave the fixed conversion value unset.

Once your test order arrived, remove the test event code, or events keep landing under **Test events** only.

**You should see:** the custom conversion shows in Events Manager.

### 5. Optimise on lifetime value

In your sales campaign, choose the LTV custom conversion as the conversion event, optimise for value and set a ROAS goal as a percentage: `PMRevenueLTV` (`CUSTOMER_REVENUE_LTV`) for lifetime revenue, `PMProfitLTV` (`CUSTOMER_PROFIT_LTV`) for lifetime profit. Every event and its purpose: [Meta events](/docs/concepts/conversion-actions-and-events#meta-events).

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

### 6. Check it works

Open **Tracking → Meta Conversions API** ([Check tracking](/docs/using/check-tracking)).

**You should see:** **Access token: Saved**, **Sending: On** and the delivery counts, and `PMRevenueLTV` arriving in Events Manager from the Conversions API.

## 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 LTV bidding (bidding on customer lifetime value) 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 LTV bidding (bidding on customer lifetime value) 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."

## How it works on Magento

|                    | On Magento                                                                                                                                         |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Customer**       | The Magento **customer account**, else the guest email, else the phone number                                                                      |
| **History**        | Each store view is its own connection, so a customer is counted per store view: the same person buying in two store views counts as two customers. |
| **`PMRevenueLTV`** | This order's products and shipping; `pm_cumulative_ltv` is the running total                                                                       |
| **`PMProfitLTV`**  | This order's profit, 0 for a loss. Costs: cost on each Magento order item (order currency = base currency), plus your additional costs             |
| **Consent**        | OneTrust, Cookiebot, Usercentrics or Osano, or your own banner, passed on by your developer; needs analytics and ad user data                      |

Meta deduplicates on event name and order ID, so a resent order isn't counted twice. Events already sent aren't revised after a refund. Orders from before you connected aren't imported, so lifetime value starts from the orders Product Metrics has seen.

## Troubleshooting

| Problem                             | Fix                                                                                                                                                                                                    |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Orders arrive with revenue only** | A cost of the order is still unknown. Complete your costs under **Profit tracking → Edit costs**: an order is sent with profit only once every cost is known ([profit rules](/docs/concepts/profit#rules)). |

## FAQ

### What does Meta receive for a repeat order?

The events `PMRevenueLTV` and `PMProfitLTV`, sent through the Meta Conversions API. Each carries what this order adds to the customer's lifetime value, with the running total as `pm_cumulative_ltv`. Meta deduplicates on event name and order ID, so a resent order isn't counted twice.

### How is a Magento customer recognised for Meta?

By the Magento customer account, else the guest email, else the phone number. Each store view is its own connection, so the same person buying in two store views counts as two customers. Each event also carries hashed customer data for Advanced Matching, so Meta can match it to the person who clicked.

### Why is PMRevenueLTV missing from Meta's custom conversion selector?

An LTV event only appears there after Meta has received one. Place a test order with consent accepted first, and activate your costs if you want `PMProfitLTV`.

### Where does Profit LTV get its costs on Magento?

Product costs come from the cost stored on each Magento order item, read when the order currency matches the base currency. Shipping, handling, returns and payment fees come from your additional costs. A loss-making order is sent as 0.

## Where next



* [LTV bidding on Magento in Google Ads](/docs/bidding/ltv/magento-google-ads): the same lifetime value, bid on in Google Ads
* [Magento](/docs/platforms/magento): the full store setup
* [Meta](/docs/channels/meta): every event, consent and troubleshooting
* [LTV bidding](/docs/features/ltv-bidding): every platform and channel
* [POAS bidding on Magento in Meta](/docs/bidding/poas/magento-meta): profit, bid on in Meta

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