> ## Documentation Index
> Fetch the complete documentation index at: https://www.productmetrics.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://www.productmetrics.io/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://www.productmetrics.io/docs/api/mcp.
> Every agent surface: https://www.productmetrics.io/docs/.well-known/llms-manifest.json

# Lightspeed new customer bidding in Meta (/docs/bidding/new-customers/lightspeed-meta)

<!-- agent-signals: reading_time_min: 9 · est_tokens: 3433 · updated: 2026-11-17 -->
Related: [Shopify new customer acquisition bidding in Google Ads](/docs/bidding/new-customers/shopify-google-ads.md), [WooCommerce new customer acquisition bidding in Google Ads](/docs/bidding/new-customers/woocommerce-google-ads.md), [Magento new customer acquisition bidding in Google Ads](/docs/bidding/new-customers/magento-google-ads.md), [Lightspeed new customer acquisition bidding in Google Ads](/docs/bidding/new-customers/lightspeed-google-ads.md), [Shopware new customer acquisition bidding in Google Ads](/docs/bidding/new-customers/shopware-google-ads.md), [New customer acquisition bidding in Google Ads on any website with Cloudflare](/docs/bidding/new-customers/cloudflare-google-ads.md)

> Send first orders from Lightspeed to Meta as PMNewCustomer through the Meta Conversions API with Advanced Matching, and optimise a campaign on a custom conversion.

For a customer's first paid Lightspeed order, Product Metrics sends the custom events **`PMNewCustomer`** (the order's revenue) and **`PMNewCustomerProfit`** (its profit) to your pixel through the Meta Conversions API, **once per customer**. Meta optimises on them through a **custom conversion**, which you create once. 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 first orders through a custom conversion on `PMNewCustomer`.

## 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 new customer bidding 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 new customer bidding 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

* **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.
* **Your additional costs active**, for the profit event: [Costs](/docs/using/costs).

## In the app

### 1. Connect Lightspeed 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**.

   ![The store platform list in Ecommerce platforms: WooCommerce, Magento, Shopware 6, Lightspeed and Custom Store / Webhook Integration, each with a Connect button, with Lightspeed outlined.](/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.

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 C-Series setup guide panel: a Download Word document button, Before you begin, and setup step 1, Sign into the C-Series back office.](/docs/_assets/7273c17d2533e636364c1f12cad7cdadf01aa4b37b5827d39cf3ad157ff4844d)

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

   *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**; Meta accepted the test event.

### 2. Check how Lightspeed decides new customers

Product Metrics uses **Lightspeed's new-customer flag** and the customer's order history in Lightspeed. When Lightspeed flags the order as a new customer's and it is the customer's only order, the customer is **new** straight away. Otherwise Product Metrics reads the customer's orders from Lightspeed: an earlier order makes them **returning**.

* **Matched by the Lightspeed customer.** An order without a Lightspeed customer to match is sent as **Product Metrics - Revenue** and **Product Metrics - Profit** only.
* **Paid only.** An order is sent once Lightspeed marks it paid, so a pay-on-pickup order is sent when it is paid.
* **History is read in the background.** When Lightspeed's flag doesn't settle it, the order shows as unknown until the customer's orders are read.

Check a few recent orders before you bid on them. Ask your assistant: "Were my last 20 Lightspeed orders from new or returning customers?"

**You should see:** each order counted as new, returning or unknown.

### 3. Create the custom conversion

This step happens in Meta Events Manager.

1. Choose **Custom conversions → Create custom conversion** and select your pixel.
2. Choose the event **`PMNewCustomer`** (or **`PMNewCustomerProfit`** to optimise on profit).
3. Add the event parameter rule **`pm_purpose` equals `CUSTOMER_NEW`** (or `CUSTOMER_NEW_PROFIT`).
4. Choose **Purchase** as the category. Use the event's value and currency; leave the fixed conversion value unset.



> **Warning:** Meta lists an event only after it has received it once. Custom events need **marketing and analytics consent**, so place a test order with both accepted in OneTrust, Cookiebot, Usercentrics or Osano.

Check out as a customer who has never ordered from your shop, and pay with your shop's test payment method. Use a test event code to see it under **Test events**, then remove the code.

**You should see:** the custom conversion is listed under **Custom conversions** in Events Manager.

### 4. Optimise your campaign on it

In your sales campaign, choose the new customer custom conversion as the conversion event and optimise on its value. Meta then gives buyers who look like first-time customers higher priority.

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

### 5. Check it works

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

**You should see:** **Meta destination saved**, and **Sending** reads **On** without "Test mode". The order check from step 2 shows your test order as new. A paid Lightspeed order shows up within a few minutes. In Events Manager, **`PMNewCustomer`** arrives with `pm_purpose` = `CUSTOMER_NEW` and `customer_type` = `NEW`, and the custom conversion shows activity after the next first order.

## How it works on Lightspeed

|                                  | On Lightspeed                                                                   |
| -------------------------------- | ------------------------------------------------------------------------------- |
| **Where the history comes from** | Lightspeed's new-customer flag, then the customer's orders                      |
| **Sent for**                     | The first paid order per customer                                               |
| **Meta event (`pm_purpose`)**    | `PMNewCustomer` (`CUSTOMER_NEW`), `PMNewCustomerProfit` (`CUSTOMER_NEW_PROFIT`) |
| **Value**                        | The order's revenue, or its profit; a loss is sent as 0                         |
| **Refunds**                      | Later refunds don't change the event                                            |
| **Past orders**                  | Not imported; Meta rejects events older than 7 days                             |

## Troubleshooting

| Problem                                                                      | Fix                                                                                                                                                |
| ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Meta says "The custom conversion for this event is not set up correctly"** | Check the event name and the `pm_purpose` rule of the custom conversion.                                                                           |
| **Orders count as neither new nor returning**                                | Product Metrics could not tell from the order history (step 2). Those orders still go to Meta as revenue and profit, just not as new or returning. |

## FAQ

### How does Lightspeed tell Product Metrics a customer is new?

With Lightspeed's new-customer flag. When the order is flagged and it is the customer's only order, `PMNewCustomer` is sent; otherwise Product Metrics first reads the customer's orders from Lightspeed.

### When is a pay-on-pickup order sent to Meta?

When Lightspeed marks it paid, not when it is placed.

### Why can't I select PMNewCustomer in Events Manager yet?

Meta lists `PMNewCustomer` only after it has received it once, and custom events need **marketing and analytics consent**. Place a test order with both accepted in OneTrust, Cookiebot, Usercentrics or Osano.

### Does a refund remove the PMNewCustomer event?

No. A later refund doesn't change `PMNewCustomer` or `PMNewCustomerProfit` in Meta.

## Where next



* [New customer bidding](/docs/features/new-customer-bidding): the feature on every platform and channel
* [New customer bidding on Lightspeed in Google Ads](/docs/bidding/new-customers/lightspeed-google-ads): the same feature on the other channel
* [Returning customer bidding on Lightspeed in Meta](/docs/bidding/returning-customers/lightspeed-meta): the other side of the split
* [Lightspeed](/docs/platforms/lightspeed): set-up and troubleshooting
* [Meta](/docs/channels/meta): set-up and troubleshooting
* [New and returning customers](/docs/concepts/new-and-returning-customers): How a customer is recognised

On the website: [customer acquisition cost (CAC)](https://www.productmetrics.io/glossary/cac), [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).
