Lightspeed lifetime value (LTV) bidding in Meta
Send each customer's lifetime revenue and profit from Lightspeed to Meta through the Meta Conversions API with Advanced Matching, and optimise on it.
With every paid order of a recognised Lightspeed 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). Each event carries hashed customer data for Advanced Matching, so Meta can match it to the person who clicked.
An API key from Lightspeed, then a Cloudflare sign-in.
Your pixel ID and a Conversions API access token.
Meta optimises on lifetime value through a custom conversion on PMRevenueLTV or PMProfitLTV.
Prerequisites
- Editor or admin on the property in Product Metrics, with Pro (Full Signal Tracking).
- Your Lightspeed eCom (C-Series) shop connected: a back-office administrator login (an API key can’t sign in), the shop’s cluster, hostname and numeric Shop ID, and an enabled API key with its secret that has Read on Content, Products, Customers and Orders, and Read and Write on Settings and Tracking. The shop can’t already be connected to another workspace, and it reads Active with Configuration is current before you link your property. See Lightspeed.
- Your shop domain on Cloudflare, with its DNS record proxied (the orange cloud), and a workspace admin who signs in to Cloudflare once.
- 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 Lightspeed shop and Meta
Connect your Lightspeed eCom (C-Series) shop with an enabled API key that has the permissions listed on Lightspeed, including Read on Customers and Orders, set up the Cloudflare gateway and link the shop to your property. 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). From then on, Product Metrics sends PMRevenueLTV and PMProfitLTV on its own.
You should see: Connection status, Credential status and Installation status read Active, Configured and Active, publication reads Configuration is current, and the gateway says Gateway setup complete; Events Manager shows the test event under Test events.
2. Check your Lightspeed shop recognises customers
Ask your assistant: “Are my last five Lightspeed orders from new or returning customers?” A guest who later orders with an account starts again under their account. The API key needs Read on Customers: without it, orders arrive without a customer and 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 shop shows: OneTrust, Cookiebot, Usercentrics or Osano. Meta has no consent mode: the LTV events are only sent when the visitor allowed both analytics and ad user data. See Consent.
For Profit LTV, product costs come from the cost price on each Lightspeed order line. Payment fees aren’t available from Lightspeed: they come from your additional costs, with shipping, handling and returns. Activate them under Tracking → Add your additional costs.
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 Lightspeed shop 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).
- In Events Manager, choose Custom conversions → Create custom conversion.
- Select your pixel and the event
PMRevenueLTV(orPMProfitLTV). - Add the event parameter rule
pm_purposeequalsCUSTOMER_REVENUE_LTV(orCUSTOMER_PROFIT_LTV). - 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.
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).
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
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/mcpClaude Code: run this in your terminal.
claude mcp add --transport http product-metrics https://www.productmetrics.io/mcpPaste the prompt into your assistant.
Set up LTV bidding (bidding on customer lifetime value) for my Lightspeed shop 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.Set up LTV bidding (bidding on customer lifetime value) for my Lightspeed shop 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.Set up LTV bidding (bidding on customer lifetime value) for my Lightspeed shop 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.Set up LTV bidding (bidding on customer lifetime value) for my Lightspeed shop 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 Lightspeed
| On Lightspeed | |
|---|---|
| Customer | The customer on the Lightspeed order, else its email address, else its phone number |
| History | Each connected Lightspeed shop 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: cost price on each Lightspeed order line, plus your additional costs (including payment fees) |
| 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). |
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 Lightspeed customer recognised for Meta?
By the customer on the Lightspeed order, else its email address, else its phone number. The API key needs Read on Customers: without it, orders arrive without a customer and add nothing to lifetime value. 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 Lightspeed?
Product costs come from the cost price on each Lightspeed order line. Lightspeed doesn’t report payment fees, so those come from your additional costs, with shipping, handling and returns. A loss-making order is sent as 0.
Where next
On the website: LTV-adjusted ROAS, repeat purchase rate, CAC to LTV calculator, Product Metrics for Lightspeed