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

# LTV bidding: bid on customer lifetime value in Google Ads, Meta and ChatGPT Ads (/docs/features/ltv-bidding)

<!-- agent-signals: reading_time_min: 7 · est_tokens: 3073 · updated: 2026-11-16 -->
Related: [Server-side conversion tracking that gets through ad blockers](/docs/features/ad-blocker-proof-tracking.md), [Customer Match lists in Google Ads, updated after every order](/docs/features/customer-list.md), [Enhanced Conversions, Meta Advanced Matching and OpenAI Conversions API](/docs/features/enhanced-conversions.md), [New customer bidding in Google Ads and Meta](/docs/features/new-customer-bidding.md), [POAS bidding: bid on profit in Google Ads, Meta and ChatGPT Ads](/docs/features/poas-bidding.md), [Returning customer bidding in Google Ads and Meta](/docs/features/returning-customer-bidding.md)

> Send each customer's lifetime revenue and profit to Google Ads, Meta and ChatGPT Ads with every paid order, and bid on customers who come back.

**Lifetime value is what a customer has actually bought from you, added up from the paid orders Product Metrics has seen.** It is not a prediction.

Product Metrics sends it server-side with every paid order of a recognised customer: as **Product Metrics - Revenue LTV** and **Product Metrics - Profit LTV** conversion actions in Google Ads, as **`PMRevenueLTV`** and **`PMProfitLTV`** events in Meta, and as **`pm_revenue_ltv`** and **`pm_profit_ltv`** custom events in ChatGPT Ads. Smart bidding then gives higher priority to the clicks that bring customers who keep buying.

## Pick your platform

One guide per platform and channel.



| Store                    | Google Ads                                                      | Meta                                                | ChatGPT Ads                                                  |
| ------------------------ | --------------------------------------------------------------- | --------------------------------------------------- | ------------------------------------------------------------ |
| Shopify                  | [Shopify + Google Ads](/docs/bidding/ltv/shopify-google-ads)         | [Shopify + Meta](/docs/bidding/ltv/shopify-meta)         | [Shopify + ChatGPT Ads](/docs/bidding/ltv/shopify-openai)         |
| WooCommerce              | [WooCommerce + Google Ads](/docs/bidding/ltv/woocommerce-google-ads) | [WooCommerce + Meta](/docs/bidding/ltv/woocommerce-meta) | [WooCommerce + ChatGPT Ads](/docs/bidding/ltv/woocommerce-openai) |
| Magento                  | [Magento + Google Ads](/docs/bidding/ltv/magento-google-ads)         | [Magento + Meta](/docs/bidding/ltv/magento-meta)         | [Magento + ChatGPT Ads](/docs/bidding/ltv/magento-openai)         |
| Lightspeed               | [Lightspeed + Google Ads](/docs/bidding/ltv/lightspeed-google-ads)   | [Lightspeed + Meta](/docs/bidding/ltv/lightspeed-meta)   | [Lightspeed + ChatGPT Ads](/docs/bidding/ltv/lightspeed-openai)   |
| Shopware                 | [Shopware + Google Ads](/docs/bidding/ltv/shopware-google-ads)       | [Shopware + Meta](/docs/bidding/ltv/shopware-meta)       | [Shopware + ChatGPT Ads](/docs/bidding/ltv/shopware-openai)       |
| Any website (Cloudflare) | [Website + Google Ads](/docs/bidding/ltv/cloudflare-google-ads)      | [Website + Meta](/docs/bidding/ltv/cloudflare-meta)      | [Website + ChatGPT Ads](/docs/bidding/ltv/cloudflare-openai)      |

## In the app

### 1. Create the conversion actions

In **Tracking → Create Google Ads conversions**, select **Create 8 conversion actions**. They include **Product Metrics - Revenue LTV** and **Product Metrics - Profit LTV**, created as secondary actions. Details: [Conversion actions](/docs/using/conversion-actions).

**You should see:** **Conversion actions** reads **Tracking ready**.

### 2. Make one LTV action primary

In Google Ads, make **Product Metrics - Revenue LTV** or **Product Metrics - Profit LTV** primary: [Make an action primary](/docs/using/conversion-actions#3-make-an-action-primary). Profit LTV needs your [additional costs](/docs/using/costs) active.

**You should see:** the LTV action you chose as primary under **Goals → Conversions**.

On Meta and ChatGPT Ads, you create the LTV conversion yourself: see [By channel](#by-channel).

## 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 in Google Ads with Product Metrics, so my campaigns bid on customers who keep buying. 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 in Google Ads with Product Metrics: check that the Revenue LTV and Profit LTV conversion actions exist and tell me which one to make primary. 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)."

## How lifetime value adds up

With each paid order, Product Metrics sends what that order adds to the customer's lifetime value; Meta also gets the running total.

```text
Order #1042  €108.00  first paid order Product Metrics saw from this customer
  → Meta       PMRevenueLTV  value 108.00  running total 108.00
  → Google Ads Product Metrics - Revenue LTV  value 108.00
Order #1077  €64.00   same customer, second paid order
  → Meta       PMRevenueLTV  value 64.00   running total 172.00
  → Google Ads Product Metrics - Revenue LTV  value 64.00
```

The values themselves are explained in [Conversion values](/docs/concepts/conversion-values); who counts as a customer is in [New and returning customers](/docs/concepts/new-and-returning-customers).

## Revenue LTV or Profit LTV

|             | **Revenue LTV**                                                    | **Profit LTV**                                                                |
| ----------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
| Adds up     | Products and shipping of the customer's paid orders, minus refunds | Each order's profit: revenue excluding tax − product costs − additional costs |
| Needs       | A recognised customer                                              | A recognised customer and known costs on their orders                         |
| Use it when | Your costs aren't set up yet                                       | You want bidding to steer on what customers earn you                          |

Profit is built the same way as for [POAS bidding](/docs/features/poas-bidding): see [Profit](/docs/concepts/profit).

## Rules

1. **A recognised customer.** By customer ID, else email address, else phone number, read from the store's order. An order without any of these gets no lifetime value.
2. **Paid orders only.** A cancelled order adds nothing. Revenue LTV counts products and shipping, and a refund lowers it.
3. **Observed, not imported.** Lifetime value starts from the orders Product Metrics has seen since you connected, and Meta's events are marked as observed.
4. **One store at a time.** Each connection is counted on its own: a Magento store view or a Shopware sales channel has its own customers.
5. **A guest who later orders with an account starts again**, because their customer ID replaces their email as the key.
6. **One currency for the total.** The running total is only sent when all of a customer's orders are in one currency.
7. **Consent.** The visitor must allow analytics and ad user data. See [Consent](/docs/concepts/consent).

## By channel

|            | **[Google Ads](/docs/channels/google-ads)**                                                                                   | **[Meta](/docs/channels/meta)**                                                  | **[ChatGPT Ads](/docs/channels/openai)**                                                          |
| ---------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| Sent as    | Conversion actions **Product Metrics - Revenue LTV** and **Product Metrics - Profit LTV**, through Google's Data Manager | Custom events `PMRevenueLTV` and `PMProfitLTV`, through the Conversions API | Custom events `pm_revenue_ltv` and `pm_profit_ltv`, through the OpenAI Conversions API       |
| Value      | Per order: what this order adds, so the sum over a customer's orders is their lifetime value                             | Per order: what this order adds, with the running total alongside           | Per order: what this order adds, so the sum over a customer's orders is their lifetime value |
| Setup      | Created for you as secondary actions; you make one primary                                                               | You create a custom conversion per event in Events Manager                  | You create a conversion with the custom event name in Ads Manager → **Conversions**          |
| Consent    | Analytics and ad user data, plus an email, phone or address Google can match                                             | Analytics and ad user data                                                  | Marketing consent (ad user data)                                                             |
| Profit LTV | Needs known costs on the customer's orders; a loss is sent as 0                                                          | A loss is sent as 0, with the real profit alongside                         | Needs known costs on the customer's orders                                                   |

## By platform



| Platform                                          | Customer recognised by                      | History                                                         |
| ------------------------------------------------- | ------------------------------------------- | --------------------------------------------------------------- |
| [Shopify](/docs/platforms/shopify)                     | Shopify customer ID, else email, else phone | Per store                                                       |
| [WooCommerce](/docs/platforms/woocommerce)             | Customer account, else billing email        | Per store; only statuses you marked as paid                     |
| [Magento](/docs/platforms/magento)                     | Customer account, else guest email          | Per store view; cancelled orders don't count                    |
| [Lightspeed](/docs/platforms/lightspeed)               | Customer on the order, else email           | Per shop; the API key needs Read on Customers                   |
| [Shopware](/docs/platforms/shopware)                   | Customer account, else guest email          | Per sales channel                                               |
| [Any website (Cloudflare)](/docs/platforms/cloudflare) | The email address your purchase page passes | From the first purchase Product Metrics receives; refunds count |

Profit LTV uses each order's profit, with product costs per platform as on [Profit](/docs/concepts/profit#product-costs-per-platform).

## FAQ

### Is lifetime value a prediction of future spend?

No. It is what a customer has actually bought from you, added up from the paid orders Product Metrics has seen since you connected. Older orders aren't imported.

### Should I bid on Revenue LTV or Profit LTV?

Use Revenue LTV while your costs aren't set up yet. Use Profit LTV when you want bidding to steer on what customers earn you; it needs known costs on the customer's orders.

### How does LTV differ in Google Ads, Meta and ChatGPT Ads?

They don't differ in value: Google Ads, Meta and ChatGPT Ads each get a conversion with every paid order of a recognised customer, carrying what that order adds to their lifetime value. Meta also gets the running total.

### Why does a customer's lifetime value start again?

A guest who later orders with an account starts again, because their customer ID replaces their email as the key. Each store connection also counts its own customers, so a Magento store view or Shopware sales channel has its own.

## Where next



* [Conversion values](/docs/concepts/conversion-values): the values each order carries, explained
* [New and returning customers](/docs/concepts/new-and-returning-customers): who counts as a customer
* [Profit](/docs/concepts/profit): how Profit LTV's order profit is built
* [POAS bidding](/docs/features/poas-bidding): bid on each order's profit
* [Costs](/docs/using/costs): activate the additional costs Profit LTV needs
* [Consent](/docs/concepts/consent): which choice lets an order carry lifetime value

On the website: [LTV-adjusted ROAS](https://www.productmetrics.io/glossary/ltv-adjusted-roas), [CAC to LTV calculator](https://www.productmetrics.io/cac-ltv-calculator)

Developers: do the same with the [CLI](/docs/cli/commands#google-ads) or the [API](/docs/api/google-ads/create-conversion-actions).
