> ## 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 returning customer bidding in Meta (/docs/bidding/returning-customers/lightspeed-meta)

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

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

Each paid Lightspeed order reaches Product Metrics, which checks the customer's history and, for **every repeat order** (not once per customer), sends the custom events **`PMReturningCustomer`** (the order's revenue) and **`PMReturningCustomerProfit`** (its profit) to your pixel through the Meta Conversions API. Meta can only optimise on a custom event 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.

## Prerequisites

* **For the profit event**, your additional costs must be active and the order's costs complete.

## 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 returning 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 returning 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."

## In the app

### 1. Connect Lightspeed and Meta

Create a Lightspeed API key and connect it in Product Metrics ([Lightspeed](/docs/platforms/lightspeed)). 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)).

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

### 2. Check how Lightspeed decides returning 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:** whether the order counts 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 **`PMReturningCustomer`** (or **`PMReturningCustomerProfit`** to optimise on profit).
3. Add the event parameter rule **`pm_purpose` equals `CUSTOMER_RETURNING`** (or `CUSTOMER_RETURNING_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 again as the same Lightspeed customer, 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 retention campaign, choose the returning customer custom conversion as the conversion event and optimise on its value. Meta then gives buyers who look like your repeat customers higher priority.

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

### 5. Check it works

1. **Classification.** The order check from step 2 shows your test order as returning. A paid Lightspeed order shows up within a few minutes.
2. **Event.** In Events Manager, **`PMReturningCustomer`** arrives with `pm_purpose` = `CUSTOMER_RETURNING` and `customer_type` = `RETURNING`.
3. **Custom conversion.** It shows activity after the next repeat order.
4. **Delivery.** **Tracking → Meta Conversions API** says **Meta destination saved**, and **Sending** reads **On** without "Test mode".



**How it works on Lightspeed**

* **Where the history comes from:** Lightspeed's new-customer flag, then the customer's orders
* **Sent for:** Every paid order after the first
* **Meta event (`pm_purpose`):** `PMReturningCustomer` (`CUSTOMER_RETURNING`), `PMReturningCustomerProfit` (`CUSTOMER_RETURNING_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

### 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 decide a customer is returning?

Product Metrics uses Lightspeed's new-customer flag and reads the customer's orders from Lightspeed. An earlier order makes them returning.

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

When Lightspeed marks it paid.

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

Meta lists `PMReturningCustomer` 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.

### Are past Lightspeed orders sent to Meta?

No. Meta rejects events older than 7 days, so Product Metrics sends orders from the moment tracking is live.

## Where next

* [Returning customer bidding](/docs/features/returning-customer-bidding): the feature on every platform and channel.
* [Returning customer bidding on Lightspeed in Google Ads](/docs/bidding/returning-customers/lightspeed-google-ads): the same feature on the other channel.
* [New customer bidding on Lightspeed in Meta](/docs/bidding/new-customers/lightspeed-meta): the other side of the split.
* [Lightspeed](/docs/platforms/lightspeed) and [Meta](/docs/channels/meta): set-up and troubleshooting.
* [New and returning customers](/docs/concepts/new-and-returning-customers) and [Conversion values](/docs/concepts/conversion-values)
* On the website: [repeat purchase rate](https://www.productmetrics.io/glossary/repeat-purchase-rate), [LTV-adjusted ROAS](https://www.productmetrics.io/glossary/ltv-adjusted-roas), [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).
