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

# Lightspeed POAS bidding: ChatGPT Ads tracking with profit (/docs/bidding/poas/lightspeed-openai)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1778 · updated: 2026-11-16 -->
Related: [Shopify POAS bidding: Google Ads conversion tracking with profit](/docs/bidding/poas/shopify-google-ads.md), [WooCommerce POAS bidding: Google Ads conversion tracking with profit](/docs/bidding/poas/woocommerce-google-ads.md), [Magento POAS bidding: Google Ads conversion tracking with profit](/docs/bidding/poas/magento-google-ads.md), [Lightspeed POAS bidding: Google Ads conversion tracking with profit](/docs/bidding/poas/lightspeed-google-ads.md), [Shopware POAS bidding: Google Ads conversion tracking with profit](/docs/bidding/poas/shopware-google-ads.md), [Cloudflare POAS bidding: Google Ads conversion tracking with profit](/docs/bidding/poas/cloudflare-google-ads.md)

> Send profit from Lightspeed orders to ChatGPT Ads through the OpenAI Conversions API and bid on it (POAS).

Every paid Lightspeed order goes to your ChatGPT Ads pixel through the OpenAI Conversions API, server-side, with its profit in the custom event [`pm_order_profit`](/docs/concepts/conversion-actions-and-events#chatgpt-ads-events). Optimise for it and ChatGPT Ads bids on profit (POAS).

## 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 POAS bidding (bidding on profit) 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 POAS bidding (bidding on profit) 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

Connect your store with [Lightspeed](/docs/platforms/lightspeed). Then, under **Tracking → OpenAI Conversions API → Connect OpenAI**, add your **Pixel ID** and a Conversions API key from Ads Manager → **Conversions**: [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). `pm_order_profit` also needs analytics consent. Without ad personalisation consent, the event is sent marked as opted out. See [Consent](/docs/using/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

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

Then, under **Tracking → Add your additional costs**, check the defaults for your country, set **Product cost fallback (%)** and select **Activate additional costs**: [Costs](/docs/using/costs).

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

### 3. Add a conversion for pm_order_profit

This step happens in ChatGPT Ads. Place a test order first, with consent accepted and your costs active, so ChatGPT Ads has received `pm_order_profit`.

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

For revenue, `order_created` needs no extra step.

**You should see:** the conversion shows in Ads Manager.

### 4. Bid on profit in ChatGPT Ads

In your ChatGPT Ads campaign, choose the `pm_order_profit` conversion as the conversion to optimise for, and optimise for its value: break-even is 100%, €1 of profit per €1 of ad spend. For revenue (ROAS), use `order_created`; your margin decides break-even, for example 286% at a 35% margin.

**You should see:** the campaign's conversion is `pm_order_profit`, and its conversions show next to the campaign's spend in Ads Manager.

### 5. Check it works

Open **Tracking → OpenAI Conversions API**: [Check tracking works](/docs/using/check-tracking#4-meta-and-chatgpt-ads).

**You should see:** **Sending: On** and the delivery counts; recent orders arrive with a known profit.



**How it works on Lightspeed**

* **Revenue:** The order's revenue → `order_created` (and `pm_order_revenue`)
* **Product costs:** The cost price on each Lightspeed order line → Taken off profit
* **Payment fees:** Your additional costs (Lightspeed reports no payment fees) → Taken off profit
* **Shipping, handling, returns:** Your additional costs → Taken off profit
* **Profit:** Revenue ex tax − all costs → `pm_order_profit`; 0 for a loss
* **Refunds:** Your shop reports them → Not sent: ChatGPT Ads events aren't revised

ChatGPT Ads accepts events up to 7 days old, so past orders are not imported.

## Troubleshooting

### 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

### Where does pm_order_profit get its Lightspeed product costs?

From the cost price on each Lightspeed order line. For a product without one, Product Metrics uses the cost of goods in your linked Merchant Center for the same SKU, then your **Product cost fallback (%)**.

### Can I bid on new customers in ChatGPT Ads?

Not yet: ChatGPT Ads has no new or returning customer conversions. You can bid on profit with `pm_order_profit` and on lifetime value with `pm_revenue_ltv` or `pm_profit_ltv`.

### Should I keep the OpenAI Pixel on my shop?

You can. `order_created` uses the order transaction ID, and OpenAI keeps the first event it receives for the same Pixel ID, event name and event ID, so the order counts once.

### Is pm_order_profit sent without ad personalisation consent?

Yes, marked as opted out. It does need analytics consent.

## 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 Google Ads](/docs/bidding/poas/lightspeed-google-ads): the same profit, bid on in Google Ads
* [POAS bidding on Lightspeed in Meta](/docs/bidding/poas/lightspeed-meta)
* [Profit](/docs/concepts/profit): how each order's profit is built
* On the website: [POAS](https://www.productmetrics.io/glossary/poas), [target ROAS](https://www.productmetrics.io/glossary/target-roas), [POAS calculator](https://www.productmetrics.io/poas-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).
