Skip to content
Google Ads

Lifetime value (LTV) bidding in Google Ads on any website with Cloudflare

Send each customer's lifetime revenue and profit from your website to Google Ads and bid on it with a target ROAS.

Product Metrics adds up each customer’s website purchases into a lifetime value: what they have actually spent with you, not a prediction. Google Ads receives it as Product Metrics - Revenue LTV and Product Metrics - Profit LTV, with every paid order of a recognised customer: each conversion carries what this order adds to their lifetime value, so a customer’s conversions add up to their lifetime value (Conversion values).

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 →

Setting it up with AI takes one prompt and 60 seconds: paste it into your assistant.

Set up LTV bidding (bidding on customer lifetime value) for my website (tracked with Cloudflare Tracking) in Google Ads with Product Metrics, and help me set the product cost fallback because my website sends no product costs. 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 (bidding on customer lifetime value) for my website (tracked with Cloudflare Tracking) in Google Ads with Product Metrics, and help me set the product cost fallback because my website sends no product costs. 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 (bidding on customer lifetime value) for my website (tracked with Cloudflare Tracking) in Google Ads with Product Metrics, and help me set the product cost fallback because my website sends no product costs. 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.
Set up LTV bidding (bidding on customer lifetime value) for my website (tracked with Cloudflare Tracking) in Google Ads with Product Metrics, and help me set the product cost fallback because my website sends no product costs. 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

  • Workspace admin in Product Metrics, with Pro (Full Signal Tracking).
  • Your website on Cloudflare Tracking: its domain on Cloudflare DNS with the record proxied (the orange cloud), a workspace admin who signs in to Cloudflare and approves Product Metrics (that is the whole setup), and the website linked to your property. See Any website (Cloudflare).
  • Google Ads connected to your property, with Data Manager access granted, and Merchant Center connected. See Google Ads.

In the app

1. Check your website recognises customers

Lifetime value needs to know who bought: on a website, the email address your purchase page passes to Product Metrics. Place a test order.

Want full customer history? Custom Store / Webhook Integration lets a developer send every order from your backend, including the customer’s order history. The website keeps Cloudflare Tracking to link visits to orders.

You should see: your test order as the last purchase received.

In Tracking → Configure consent, choose the banner your website shows: OneTrust, Cookiebot, Usercentrics or Osano. Google Ads gets a customer’s LTV conversion only when the visitor allowed both analytics and ad user data, and the order carries an email address, phone number or full address Google can match. See Consent.

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.

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.

Configure consent

Under Configure consent, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.

The Configure consent step in the tracking checklist, with the list of consent platforms to choose from.

You should see: Configure consent names the banner your website actually shows.

3. Create the LTV conversion actions

In Product Metrics, select Tracking → Create Google Ads conversions → Create 8 conversion actions. All eight are secondary, so nothing changes in your campaigns yet (Conversion actions).

Create Google Ads conversions

Under Create Google Ads conversions, select Create 8 conversion actions. Product Metrics manages one Google Ads conversion action per purpose; they start as secondary goals, and you choose the primary goal in Google Ads.

The Conversion actions page in Product Metrics, opened from Tracking: Not configured, 0 of 8 managed and the Create 8 conversion actions button. Below it, Customer types (New customer revenue and profit, Returning customer revenue and profit) and Order value (Order revenue, Order profit), each Missing with Google goal status Unknown, and the Lifetime value group.

You should see: both LTV conversion actions are created and linked.

4. Add your costs (for Profit LTV)

Website orders carry no product costs, so profit uses your Product cost fallback (%) of each line’s revenue, plus shipping, handling, returns and payment fees from your additional costs: set both under Tracking → Add your additional costs.

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.

The Add your additional costs step in Tracking, prefilled for your country: shipping, handling, returns and payment fee fields, a Product cost fallback (%) field and the Activate additional costs button.

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: the Profit tracking section says your additional costs are active.

5. Bid on lifetime value

  1. In Google Ads, make Product Metrics - Revenue LTV or Product Metrics - Profit LTV primary and your old purchase action secondary (how). Both need a recognised customer; Profit LTV also needs known costs.
  2. Set the campaign to Maximise conversion value with a target ROAS, written as a percentage.

An LTV conversion carries what each order adds to a customer’s lifetime value, and only recognised customers’ orders count. Don’t copy the target ROAS of your purchase action without thinking: set it on what a customer is worth to you over time.

You should see: in Google Ads, Goals → Conversions lists the LTV action you chose as primary.

6. Check it works

Open Tracking → Conversion actions. Then ask your assistant about your test order: “I just placed a test order. Did Product Metrics get it?” See Check tracking.

You should see: Tracking ready, and the test order with its revenue, profit and customer. In the conversion action report, the LTV action gets conversions from recognised customers.

How it works on a website

On a website
CustomerThe email address your purchase page passes to Product Metrics
HistoryThe page reports no order history, so a customer’s history starts with the first purchase Product Metrics receives from your website. Refunds and cancellations count.
Revenue LTVProducts and shipping of every purchase Product Metrics has seen from the customer
Profit LTVThe same orders’ profit. Costs: your Product cost fallback (%), plus your additional costs
Sent asProduct Metrics - Revenue LTV and Product Metrics - Profit LTV: one conversion with every paid order, worth what that order adds (a loss-making order’s Profit LTV is sent as 0)
ConsentOneTrust, Cookiebot, Usercentrics or Osano; needs analytics and ad user data

Orders from before you connected aren’t imported, so lifetime value starts from the orders Product Metrics has seen.

Troubleshooting

ProblemFix
Orders arrive with revenue onlyA 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).

FAQ

Are past website orders counted in lifetime value?

No. The page reports no order history, so a customer’s history starts with the first purchase Product Metrics receives from your website. Refunds and cancellations after that do count. For full history, a developer can send every order from your backend with Custom Store / Webhook Integration.

Does Profit LTV work without product costs on my website?

Yes. A website sends no product costs, so profit uses your Product cost fallback (%) of each line’s revenue, plus your additional costs. Profit is only as accurate as that percentage.

Does Google Ads get an LTV conversion for every repeat order?

Yes. Google Ads gets one with every paid order of a recognised customer, worth what that order adds, so a customer’s LTV conversions add up to their lifetime value.

What target ROAS should I set for LTV bidding?

Set it on what a customer is worth to you over time, written as a percentage. Don’t copy the target ROAS of your purchase action without thinking: each LTV conversion carries what an order adds to a recognised customer’s lifetime value, and orders from customers Product Metrics can’t recognise send none.

Where next

On the website: LTV-adjusted ROAS, repeat purchase rate, CAC to LTV calculator

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