> ## Documentation Index
> Fetch the complete documentation index at: https://4ce2765-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://4ce2765-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://4ce2765-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://4ce2765-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Lightspeed lifetime value (LTV) bidding in Meta (/docs/bidding/ltv/lightspeed-meta)

<!-- agent-signals: reading_time_min: 11 · est_tokens: 4207 · 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 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](/docs/concepts/conversion-values)). Each event carries hashed customer data for [Advanced Matching](/docs/tracking/enhanced-conversions/lightspeed-meta), so Meta can match it to the person who clicked.



* **Store:** [Lightspeed](/docs/platforms/lightspeed). An API key from Lightspeed, then a Cloudflare sign-in.
* **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 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."

**Claude Code or Codex:** "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."

## Prerequisites

* **[Editor or admin](/docs/using/team#1-choose-a-role)** 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](/docs/platforms/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](/docs/platforms/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](/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 **Lightspeed**.

   ![Ecommerce platforms under Integrations, listing the supported store platforms with a Connect button on Lightspeed.](/docs/_assets/0c05b9d4decc1de6535ef457c54dfe27804efbe9a7b5ca7c20d0a46bb3f8ff15)

2. **Start the setup.** The Lightspeed page lists three steps: connect your store, verify the connection and link a property. Select **Connect Lightspeed**.

   ![The Lightspeed page under Integrations → Ecommerce platforms: 0 of 3 steps done, step 1 Connect your store with the Connect Lightspeed button, then Verify the connection and Link a property.](/docs/_assets/8d91ee07b543eef0b937594ab6d687baf56be4cedec1b58cec69f9a34376b52d)

3. **Enter your shop details.** Choose the **Cluster**, then enter the **Store hostname**, **Shop ID**, **API key** and **API secret**. You create the API key in the Lightspeed back office under **Settings → Store Settings → Developers**.

   ![The Connect Lightspeed dialog: Cluster set to Europe, then empty Store hostname, Shop ID, API key and API secret fields, each with where to find it in the Lightspeed back office, including the API key permissions, and the Cancel and Connect Lightspeed buttons.](/docs/_assets/11453e2e2b52149b29209d41615ebfae944f3ad5954e9e11c06183e9cbd9e1a4)

4. **Connect the store.** Select **Connect Lightspeed**. Product Metrics checks the key, saves the connection, registers its order webhooks and detects your shop language.

   ![The Lightspeed page after Connect Lightspeed, with the store's connection, credential and installation status.](/docs/_assets/6102e9bc56937e92684b3c198bcd8b98d1430bb9cc855791abe843bfb265eb29)

   *Example data.*

5. **Follow the setup guide.** Select **Setup guide** for every step in the Lightspeed back office, including the permissions the API key needs.

   ![The Lightspeed setup guide panel in Product Metrics: every step in the Lightspeed back office, including the permissions the API key needs.](/docs/_assets/bad196dcafbc326d06548c2adc21db9d10b37fd1f653881f22abdf9be16fd627)

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

   *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:** **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](/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 Configure consent step in the tracking checklist, with the list of consent platforms to choose from.](/docs/_assets/f0a8d61eaa086657ce840c85899df48d5f3a7a52fb6c552710f93b1482b90e72)

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](/docs/using/costs), with shipping, handling and returns. 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.

   ![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.](/docs/_assets/9aa53f961b1d7a0f43c3ebdccb7dfda4cb044d52cf5c7d4cd3b10fc95a7083fb)



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

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 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](/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 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



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

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