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

# Lightspeed POAS bidding: Meta Conversions API with profit (/docs/bidding/poas/lightspeed-meta)

<!-- agent-signals: reading_time_min: 10 · est_tokens: 4010 · updated: 2026-11-17 -->
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 Meta through the Meta Conversions API with Advanced Matching, and optimise on it with a ROAS goal.

Every paid Lightspeed order goes to your Meta pixel through the Meta Conversions API, server-side, with its profit in the custom event [`PMOrderProfit`](/docs/concepts/conversion-actions-and-events#meta-events). Optimise on a custom conversion on it and Meta steers on profit (POAS). 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 profit through a custom conversion on `PMOrderProfit`.

## 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 POAS bidding (bidding on profit) 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 POAS bidding (bidding on profit) 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 store with [Lightspeed](/docs/platforms/lightspeed). Then, under **Tracking → Meta Conversions API → Connect Meta**, add your **Pixel or Dataset ID** and a Conversions API access token from Events Manager, and send a test event: [Meta](/docs/channels/meta).

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)

On Lightspeed, Product Metrics reads consent from the banner chosen under **Tracking → Configure consent** (OneTrust, Cookiebot, Usercentrics or Osano). The profit event also needs analytics consent. See [Consent](/docs/using/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)

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



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)

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

### 3. Create a custom conversion on PMOrderProfit

This step happens in Meta. `PMOrderProfit` only appears in Meta's selector after Meta has received one, so first place a test order with consent accepted and your costs active.

1. In Events Manager, choose **Custom conversions → Create custom conversion**.
2. Select your pixel and the event `PMOrderProfit`.
3. Add the event parameter rule `pm_purpose` equals `ORDER_PROFIT`.
4. Choose **Purchase** as the category. Use the event's value and currency; leave the fixed conversion value unset.

For ROAS, skip this: the standard `Purchase` event already carries revenue.

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.

### 4. Optimise on profit

In your sales campaign, choose the `PMOrderProfit` custom conversion as the conversion event, optimise for value and set a ROAS goal as a percentage: 100% is break-even, 150% keeps €0.50 profit per €1 of ad spend. For revenue (ROAS), use `Purchase` with your revenue target, for example 420% for a ROAS of 4.2.



> **Warning:** Moving a campaign from revenue to profit? Lower the goal: [POAS and ROAS bidding](/docs/features/poas-bidding).

**You should see:** the ad set's conversion event is your `PMOrderProfit` custom conversion.

### 5. Check it works

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

**You should see:** **Access token: Saved**, **Sending: On** with test mode off, and the delivery counts; recent orders arrive with a known profit.

## How it works on Lightspeed

|                                 | On Lightspeed                                              | Sent as                                                                                  |
| ------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| **Revenue**                     | The order's revenue                                        | `Purchase` (and `PMOrderRevenue`, `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                                 | `PMOrderProfit` (`ORDER_PROFIT`); 0 for a loss, signed value in `pm_contribution_profit` |
| **Refunds**                     | Your store reports them                                    | Not sent: Meta events aren't revised                                                     |

Meta rejects events older than 7 days, so past orders are not imported.

## 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)). |
| **Events only show under Test events** | Remove the test event code from your Meta destination under **Tracking → Meta Conversions API**.                                                                                                       |

## FAQ

### Which Lightspeed costs make up the profit Meta receives?

Product costs come from the cost price on each Lightspeed order line. Lightspeed reports no payment fees, so those come from your additional costs, as do shipping, handling and returns.

### Which consent banners work with Lightspeed?

OneTrust, Cookiebot, Usercentrics or Osano, chosen under **Tracking → Configure consent**. `PMOrderProfit` needs both marketing and analytics consent.

### Do I still need my Meta pixel?

You can keep it. `Purchase` uses the order transaction ID, so Meta counts it once when your pixel and the Meta Conversions API both send it within 48 hours. The server-side events also carry hashed customer data for Advanced Matching.

### Does Meta get past orders or refunds?

No. Meta rejects events older than 7 days, so past orders aren't imported, and a later refund doesn't revise the order's Meta events.

## Where next



* [Lightspeed](/docs/platforms/lightspeed): the full store setup
* [Meta](/docs/channels/meta): every event, consent and troubleshooting
* [POAS bidding on Lightspeed in Google Ads](/docs/bidding/poas/lightspeed-google-ads): the same profit, bid on in Google Ads
* [POAS and ROAS bidding](/docs/features/poas-bidding): every platform and channel
* [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-meta).
