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

# WooCommerce lifetime value (LTV) bidding in Meta (/docs/bidding/ltv/woocommerce-meta)

<!-- agent-signals: reading_time_min: 11 · est_tokens: 4159 · updated: 2026-11-17 -->
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 WooCommerce to Meta through the Meta Conversions API with Advanced Matching, and optimise on it.

With every paid order of a recognised WooCommerce 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/woocommerce-meta), so Meta can match it to the person who clicked.



* **Store:** [WooCommerce](/docs/platforms/woocommerce). The WordPress plugin, connected with a one-time setup token.
* **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`.

## 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 LTV bidding (bidding on customer lifetime value) for my WooCommerce 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 WooCommerce 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

* **[Editor or admin](/docs/using/team#1-choose-a-role)** on the property in Product Metrics, with Pro (Full Signal Tracking).
* **Your WooCommerce store connected**: a WordPress administrator login, WordPress 6.4+ and PHP 8.1+ with WP-Cron running, and the shop at the root of an HTTPS domain (no subfolder, no custom port). You install the Product Metrics plugin, connect it with a one-time setup token, choose your paid order statuses and link the store to your property. See [WooCommerce](/docs/platforms/woocommerce).
* **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 WooCommerce store and Meta

Connect your WooCommerce store with the Product Metrics plugin and link it to your property ([WooCommerce](/docs/platforms/woocommerce)). 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.

Connect your store, step by step:



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

   ![The store platform list in Ecommerce platforms: WooCommerce, Magento, Shopware 6, Lightspeed and Custom Store / Webhook Integration, each with a Connect button, with WooCommerce outlined.](/docs/_assets/2ebc5d1cd4423cf2d768fbd96f1313b1766af14df17a4b1549c8fc6319b7a31a)

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

   ![The WooCommerce page under Integrations → Ecommerce platforms: 0 of 3 steps done, step 1 Connect your store with the Connect WooCommerce button, then Install and connect the plugin and Link a property.](/docs/_assets/6bf466ca0781081f0c33d4bc5a0ac4efd114540ed8d9521da9bfb016178117d5)

3. **Enter your store URL.** Enter your WooCommerce shop address, starting with `https://`, and select **Create connection**.

   ![The Connect WooCommerce dialog: an empty store URL field and the Cancel and Create connection buttons.](/docs/_assets/7357f34add2e34d551543aa2425c2a017bc05caf12a31e281443f7311e174fb6)

4. **Install and pair the plugin.** Download the plugin ZIP and install it in WordPress Admin, then paste the one-time setup token from this page under **WooCommerce → Product Metrics** and select **Connect store**. The page updates by itself once WooCommerce confirms the connection.

5. **Follow the setup guide.** Select **Setup guide** for every step in WordPress and WooCommerce, with screenshots. You can also download it as a Word document.

   ![The WooCommerce setup guide panel in Product Metrics: a Download Word document button, then Before you begin: a WordPress administrator login, access to your Product Metrics workspace, your shop's web address starting with https:// and a test payment method.](/docs/_assets/207d0b6c5ee392d3400cc9163d1e7178cd68cebfce41c2641d47cdbf4d1d11d2)

6. **Link a property.** With the store connected, choose which Product Metrics property receives its orders under **Link property**. Then authorise Google Ads conversions.

   ![The WooCommerce page under Integrations → Ecommerce platforms for northwind-outfitters.example, Active, 2 of 3 steps done: Connect your store and Install and connect the plugin are done, and Link a property is next, with the Default storefront scope.](/docs/_assets/9d7e72f61e863c6773b2f12d4d99b41449da26142596bb5dd930bbc36ad8fbf8)

   *Example data.*

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/db57bf8bfd722bf95f851e3275f928edb7ae79980483b9c579130ad240b3d9b8)

   *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:** the plugin says **Store connected successfully.** and **Webhooks: 2 of 2 active**; Events Manager shows the test event under **Test events**.

### 2. Check your WooCommerce store recognises customers

Ask your assistant: "Are my last five WooCommerce orders from new or returning customers?" A guest who later orders with an account starts again under their account. Only the order statuses you marked as paid under **Orders & product data** count: if you leave out a status your store really uses, those orders add nothing to lifetime value.

**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 store shows: OneTrust, Cookiebot, Usercentrics or Osano. Clear your full-page cache after you change it. With any other banner, or left on **Not configured**, Product Metrics can't read the visitor's choice and treats it as not given: those 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).



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 Consent management panel in Tracking: the storefront script collects nothing until your cookie banner says the visitor agreed, a Not configured status, and the Consent platform dropdown.](/docs/_assets/f0a8d61eaa086657ce840c85899df48d5f3a7a52fb6c552710f93b1482b90e72)

For Profit LTV, product costs come from **WooCommerce Core COGS** or the product meta key you chose in the plugin. Payment and actual shipping costs can come from order meta keys; everything else comes from your [additional costs](/docs/using/costs): activate them under **Tracking → Add your additional costs**.



1. **Add your additional costs.** Product costs come from your store where it reports them. Under **Add your additional costs**, add shipping, handling, returns and payment fees, set **Product cost fallback (%)** and select **Activate additional costs**, so the profit conversions carry real profit.



> **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 WooCommerce store 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.

## How it works on WooCommerce

|                    | On WooCommerce                                                                                                       |
| ------------------ | -------------------------------------------------------------------------------------------------------------------- |
| **Customer**       | The WooCommerce **customer account**, else the billing email for guest orders, else the phone number                 |
| **History**        | Each connected WooCommerce store is counted on its own.                                                              |
| **`PMRevenueLTV`** | This order's products and shipping; `pm_cumulative_ltv` is the running total                                         |
| **`PMProfitLTV`**  | This order's profit, 0 for a loss. Costs: WooCommerce Core COGS or your product meta key, plus your additional costs |
| **Consent**        | OneTrust, Cookiebot, Usercentrics or Osano; 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 WooCommerce customer recognised for Meta?

By the WooCommerce customer account, else the billing email for guest orders, else the phone number. Only orders with a status you marked as paid under **Orders & product data** count. 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 WooCommerce?

Product costs come from WooCommerce Core COGS or your product meta key, chosen in the plugin. Everything else comes from your additional costs. A loss-making order is sent as 0.

## Where next



* [LTV bidding on WooCommerce in Google Ads](/docs/bidding/ltv/woocommerce-google-ads): the same lifetime value, bid on in Google Ads
* [WooCommerce](/docs/platforms/woocommerce): 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 WooCommerce in Meta](/docs/bidding/poas/woocommerce-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 WooCommerce](https://www.productmetrics.io/platforms/woocommerce)

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