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

# Lightspeed lifetime value (LTV) bidding in ChatGPT Ads (/docs/bidding/ltv/lightspeed-openai)

<!-- agent-signals: reading_time_min: 6 · est_tokens: 1910 · updated: 2026-11-16 -->
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 orders to ChatGPT Ads through the OpenAI Conversions API and bid on it.

With every paid Lightspeed order from a recognised customer, Product Metrics sends `pm_revenue_ltv` and `pm_profit_ltv` to your ChatGPT Ads pixel. Each carries **what this order adds** to the customer's lifetime value: observed value from paid orders, not a prediction ([LTV bidding](/docs/features/ltv-bidding)).

## Prerequisites

* **[Editor or admin](/docs/using/team#1-choose-a-role)** on the property in Product Metrics, with Pro (Full Signal Tracking).
* **A Lightspeed eCom (C-Series) API key and secret** from your back office, and a workspace admin who can approve Cloudflare once.
* **Access to ChatGPT Ads Manager → Conversions**, to copy your Pixel ID and create a Conversions API key.

## 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 (bidding on customer lifetime value) for my Lightspeed shop in ChatGPT Ads 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 ChatGPT Ads 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."

## In the app

### 1. Connect your Lightspeed shop and ChatGPT Ads

Add a Lightspeed API key in Product Metrics and sign in to Cloudflare for the gateway, then link the shop to your property ([Lightspeed](/docs/platforms/lightspeed)). Then, in Ads Manager → **Conversions**, copy your **Pixel ID** and create a Conversions API key, and add both under **Tracking → OpenAI Conversions API → Connect OpenAI** ([ChatGPT Ads](/docs/channels/openai)).



![The Add OpenAI destination form with Pixel ID, Conversions API key and the Send events to OpenAI switch, then the saved OpenAI Conversions API destination showing Active, the key Accepted by OpenAI and Sending On.](/docs/_assets/12b7f9404eb89a50f8e9b3cf2d8a9f079571fe77837c0fd77099cf9d8ef774f9)

*Figure: Add OpenAI destination: paste the Pixel ID and Conversions API key, keep Send events to OpenAI on.*

On Lightspeed, Product Metrics reads consent from the banner chosen under **Tracking → Configure consent** (OneTrust, Cookiebot, Usercentrics or Osano). ChatGPT Ads has no consent mode: an event is only sent with marketing consent (ad user data), and the LTV events also need analytics consent. Without ad personalisation consent, the event is sent marked as opted out. See [Consent](/docs/concepts/consent).

**You should see:** **Connection status**, **Credential status** and **Installation status** read **Active**, **Configured** and **Active**, and the gateway says **Gateway setup complete**; the app says **OpenAI accepted the test event**.

### 2. Activate your additional costs

Skip this step if you only want Revenue LTV. Product costs come from the cost price on each Lightspeed order line. Lightspeed doesn't report payment fees, so those always come from **External payment fixed cost** and **External payment (%)**. Everything else comes from your [additional costs](/docs/using/costs): activate them under **Tracking → Add your additional costs**.



> **Note:** Profit LTV is only sent when every cost of the order is known. Revenue LTV doesn't need costs. A loss-making order adds 0.

**You should see:** the **Profit tracking** section says your additional costs are active.

### 3. Add conversions for the LTV events

This step happens in ChatGPT Ads. Place a test order first, as a customer with an email address, so ChatGPT Ads has received the events.

1. In ChatGPT Ads Manager, open **Conversions**.
2. Create a conversion with the custom event name `pm_revenue_ltv`, and one with `pm_profit_ltv`.

**You should see:** the conversions show in Ads Manager. `pm_profit_ltv` only arrives once your costs are active.

### 4. Bid on lifetime value in ChatGPT Ads

In your ChatGPT Ads campaign, choose an LTV event as the conversion to optimise for, and optimise for its value. ChatGPT Ads then bids on each customer's lifetime value.

| You optimise on  | Conversion       |
| ---------------- | ---------------- |
| Lifetime revenue | `pm_revenue_ltv` |
| Lifetime profit  | `pm_profit_ltv`  |

**You should see:** the campaign's conversion is `pm_revenue_ltv` or `pm_profit_ltv`.

### 5. Check it works

Open **Tracking → OpenAI Conversions API**, then ask your assistant about your test order: "I just placed a test order. Did Product Metrics get it?" See [Check tracking](/docs/using/check-tracking).

**You should see:** **Sending: On** and the delivery counts, and your test order with its revenue, profit and customer.



**How it works on Lightspeed**

* **Customer recognised by:** The customer ID on the Lightspeed order, else email address, else phone number → No customer, no LTV event
* **Revenue LTV:** Products and shipping this order adds → `pm_revenue_ltv`
* **Profit LTV:** Profit this order adds, once costs are known → `pm_profit_ltv`; 0 for a loss
* **Earlier orders:** Only orders Product Metrics has seen count → Not imported
* **Refunds:** Your shop reports them → Not sent: ChatGPT Ads events aren't revised

ChatGPT Ads accepts events up to 7 days old.

## Troubleshooting

### Orders are missing in ChatGPT Ads

Check that **Tracking → Configure consent** names the banner your store actually shows: Product Metrics sends an order only with the consent this page lists. See [Consent](/docs/concepts/consent).

## FAQ

### What does ChatGPT Ads receive for each order?

The custom events `pm_revenue_ltv` and `pm_profit_ltv`, sent server-side through the OpenAI Conversions API. Each carries what this order adds, so the sum over a customer's orders is their lifetime value.

### Which Lightspeed orders get an LTV event?

Orders from a recognised customer: the customer ID on the Lightspeed order, else its email address, else its phone number. An order without a customer gets no LTV event.

### Are orders from before I connected sent to ChatGPT Ads?

No. Orders from before you connected aren't imported, and ChatGPT Ads accepts events up to 7 days old, so lifetime value starts from the orders Product Metrics has seen.

### Can ChatGPT Ads bid on new customers instead of LTV?

Not yet: ChatGPT Ads has no new or returning customer conversions. You can bid on lifetime value or on profit per order (POAS) in ChatGPT Ads.

## Where next

* [Lightspeed](/docs/platforms/lightspeed): the full shop setup
* [ChatGPT Ads (OpenAI)](/docs/channels/openai): every event, consent, limits and troubleshooting
* [POAS bidding on Lightspeed in ChatGPT Ads](/docs/bidding/poas/lightspeed-openai): profit per order
* [LTV bidding on Lightspeed in Google Ads](/docs/bidding/ltv/lightspeed-google-ads)
* [LTV bidding](/docs/features/ltv-bidding): every platform and channel
* 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-openai).
