Returning customer bidding in Meta on any website with Cloudflare
Send repeat orders from your website to Meta as PMReturningCustomer through the Meta Conversions API with Advanced Matching, and optimise a campaign on a custom conversion.
Each purchase on your website 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, so Meta can match it to the person who clicked.
Prerequisites
- Your website on Cloudflare Tracking: its domain on Cloudflare DNS with the record proxied (the orange cloud), a workspace admin who signs in to Cloudflare and approves Product Metrics (that is the whole setup), and the website linked to your property. See Any website (Cloudflare).
- For the profit event, your additional costs must be active and the order’s costs complete.
Set it up with AI
Connect your assistant
First time? Add the Product Metrics MCP server to your assistant, then paste the prompt below.
In Claude, choose Add custom connector; in ChatGPT, Settings → Apps & Connectors. Paste this URL:
https://www.productmetrics.io/mcpClaude Code: run this in your terminal.
claude mcp add --transport http product-metrics https://www.productmetrics.io/mcpPaste the prompt into your assistant.
Set up returning customer bidding for my website (tracked with Cloudflare Tracking) 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.Set up returning customer bidding for my website (tracked with Cloudflare Tracking) 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.Set up returning customer bidding for my website (tracked with Cloudflare Tracking) 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.Set up returning customer bidding for my website (tracked with Cloudflare Tracking) 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 your website and Meta
Sign in to Cloudflare and choose your domain (Any website (Cloudflare)). 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).
You should see: the gateway card says Gateway setup complete; Meta accepted the test event.
2. Check how your website decides returning customers
Cloudflare Tracking reads each purchase from your order confirmation page, not from a shop system, so it has no order history to look up. A buyer is returning when they are identified and Product Metrics has already seen them pay on your website. Product Metrics can’t confirm that anyone is new.
- No new customers. Website orders are never sent as Product Metrics - New Customer or
PMNewCustomer. - Returning from what Product Metrics has seen. History starts when tracking went live: a customer who bought before that is not recognised as returning.
- Everything else is unknown. An order that isn’t returning is sent as Product Metrics - Revenue and Product Metrics - Profit only.
- Want order history? Custom Store / Webhook Integration lets a developer send every order from your backend, including the customer’s order history. The website still needs Cloudflare Tracking to link visits to orders.
Check a few recent orders before you bid on them. Ask your assistant: “Were my last 20 website orders from new or returning customers?”
You should see: whether the order counts as returning or unknown.
3. Create the custom conversion
This step happens in Meta Events Manager.
- Choose Custom conversions → Create custom conversion and select your pixel.
- Choose the event
PMReturningCustomer(orPMReturningCustomerProfitto optimise on profit). - Add the event parameter rule
pm_purposeequalsCUSTOMER_RETURNING(orCUSTOMER_RETURNING_PROFIT). - Choose Purchase as the category. Use the event’s value and currency; leave the fixed conversion value unset.
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.
Place two test orders on your website as the same identified customer, finishing each through to the order confirmation page. 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
- Classification. The order check from step 2 shows your test order as returning. A test order shows up under Check your purchases within two minutes.
- Event. In Events Manager,
PMReturningCustomerarrives withpm_purpose=CUSTOMER_RETURNINGandcustomer_type=RETURNING. - Custom conversion. It shows activity after the next repeat order.
- Delivery. Tracking → Meta Conversions API says Meta destination saved, and Sending reads On without “Test mode”.
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 Product Metrics know a website buyer is returning?
The buyer is identified and Product Metrics has already seen them pay on your website. Every other order is sent as revenue and profit only.
Does a customer who bought before tracking went live count?
No. History starts when tracking went live, so earlier purchases on your website aren’t known.
Does PMReturningCustomerProfit work without product costs?
Yes. Profit uses your Product cost fallback (%) plus your additional costs.
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.
Where next
- Returning customer bidding: the feature on every platform and channel.
- Returning customer bidding on any website with Cloudflare in Google Ads: the same feature on the other channel.
- New customer bidding on any website with Cloudflare in Meta: the other side of the split.
- Any website (Cloudflare) and Meta: set-up and troubleshooting.
- New and returning customers and Conversion values
- On the website: repeat purchase rate, LTV-adjusted ROAS