Skip to content
LTV bidding

LTV bidding: bid on customer lifetime value in Google Ads, Meta and ChatGPT Ads

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.

The values themselves are explained in Conversion values; who counts as a customer is in New and returning customers.

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: the customer's LTV
    conversion, value 108.00
Order #1077  €64.00   same customer, second paid order
  → Meta       PMRevenueLTV  value 64.00   running total 172.00

Set it up with AI

Connect your assistant

First time? Add the Product Metrics MCP server to your assistant, then paste the prompt below.

In Claude, choose Add custom connector; in ChatGPT, Settings → Apps & Connectors. Paste this URL:

https://www.productmetrics.io/mcp

Claude Code: run this in your terminal.

claude mcp add --transport http product-metrics https://www.productmetrics.io/mcp

CodexAll clients and details →

Paste the prompt into your assistant.

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

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.

You should see Conversion actions read 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. Profit LTV needs your additional 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

Google AdsMetaChatGPT Ads
Sent asConversion actions Product Metrics - Revenue LTV and Product Metrics - Profit LTV, through Google’s Data ManagerCustom events PMRevenueLTV and PMProfitLTV, through the Conversions APICustom events pm_revenue_ltv and pm_profit_ltv, through the OpenAI Conversions API
ValueOne conversion per customer, dated at their first order Product Metrics saw, valued at the customer’s lifetime totalPer order: what this order adds, with the running total alongsidePer order: what this order adds, so the sum over a customer’s orders is their lifetime value
SetupCreated for you as secondary actions; you make one primaryYou create a custom conversion per event in Events ManagerYou create a conversion with the custom event name in Ads Manager → Conversions
ConsentAnalytics and ad user data, plus an email, phone or address Google can matchAnalytics and ad user dataMarketing consent (ad user data)
Profit LTVNeeds known costs on the customer’s orders A loss is sent as 0, with the real profit alongsideNeeds known costs on the customer’s orders

Revenue LTV or Profit LTV

Revenue LTVProfit LTV
Adds upProducts and shipping of the customer’s paid orders, minus refundsEach order’s profit: revenue excluding tax − product costs − additional costs
NeedsA recognised customerA recognised customer and known costs on their orders
Use it whenYour costs aren’t set up yetYou want bidding to steer on what customers earn you

Profit is built the same way as for POAS bidding: see Profit. Related on the website: LTV-adjusted ROAS and the CAC to LTV calculator.

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.

By platform

PlatformCustomer recognised byHistory
ShopifyShopify customer ID, else email, else phonePer store
WooCommerceCustomer account, else billing emailPer store; only statuses you marked as paid
MagentoCustomer account, else guest emailPer store view; cancelled orders don’t count
LightspeedCustomer on the order, else emailPer shop; the API key needs Read on Customers
ShopwareCustomer account, else guest emailPer sales channel
Any website (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.

Pick your platform and channel

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?

Google Ads gets one conversion per customer, worth their lifetime total. Meta and ChatGPT Ads get an event with every paid order, carrying what that order adds; 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.

Developers: do the same with the CLI or the API.