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

# New customer bidding in Meta on any website with Cloudflare (/docs/bidding/new-customers/cloudflare-meta)

<!-- agent-signals: reading_time_min: 4 · est_tokens: 1501 · updated: 2026-11-16 -->
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)

> Why website orders tracked with Cloudflare reach Meta through the Meta Conversions API with Advanced Matching, but not as new customers, and what to bid on instead.

Cloudflare Tracking reads each purchase from your **order confirmation page**. The page tells Product Metrics what was bought, not whether this customer ever bought before, so Product Metrics can't confirm a first order. `PMNewCustomer` and `PMNewCustomerProfit` are **never sent** for website orders. Everything else works: revenue, profit (with **Product cost fallback (%)**) and returning customers. Website purchases still reach Meta through the **Meta Conversions API**, with [Advanced Matching](/docs/tracking/enhanced-conversions/cloudflare-meta) on the email your site passes.

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics.
* **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)](/docs/platforms/cloudflare).
* **Meta connected.** Follow [Meta](/docs/channels/meta).

## 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:** "Check whether Product Metrics can send new customers from my website (tracked with Cloudflare Tracking) to Meta, and help me choose what to bid on instead. 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:** "Check whether Product Metrics can send new customers from my website (tracked with Cloudflare Tracking) to Meta, and help me choose what to bid on instead. 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. Check how your website decides new customers

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.

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

Ask your assistant: "Were my last 20 website orders from new or returning customers?"

**You should see:** first purchases counted as unknown, and returning only for identified buyers Product Metrics has already seen pay.

### 2. Bid on something else

* **Optimise on returning customers** with `PMReturningCustomer`: [Returning customer bidding on any website with Cloudflare in Meta](/docs/bidding/returning-customers/cloudflare-meta).
* **Optimise on all orders by profit** with `PMOrderProfit`: [POAS bidding](/docs/features/poas-bidding).

### 3. Or send orders from your backend

With **Custom Store / Webhook Integration**, a developer sends every order from your backend, signed, when it is paid, refunded or cancelled, **including the customer's order history**. With that history Product Metrics can tell new customers apart.

The website still needs Cloudflare Tracking to link visits to orders.

### 4. Check it works

Place a test order on your website and finish it through to the order confirmation page.

**You should see:** your test order's transaction ID, value and currency. In the app, **Check your purchases** shows **Last purchase received**.



**How it works on a website**

* **Where the history comes from:** Purchases Product Metrics has seen on your website
* **New customers:** Never sent: no order history to confirm a first order
* **Returning customers:** Sent for identified buyers seen paying before
* **Every order:** Sent as revenue and profit

## Troubleshooting

### No new customer conversions arrive

Website orders are never sent as new customers. Bid on returning customers or on all orders by profit instead (step 2).

## FAQ

### Do my website purchases still reach Meta?

Yes. They go through the **Meta Conversions API** with **Advanced Matching** on the email your site passes, as revenue and profit events, not as `PMNewCustomer`.

### Why can a Shopify store send new customers but my website can't?

A store platform gives Product Metrics the customer's order history. Cloudflare Tracking reads the order confirmation page, which shows what was bought, not whether the buyer bought before.

### Does profit optimisation work without product costs?

Yes. `PMOrderProfit` uses your **Product cost fallback (%)** plus your additional costs.

### Is a buyer from before tracking went live seen as returning?

No. History starts when tracking went live, so only purchases Product Metrics has seen on your website count.

## Where next

* [New customer bidding](/docs/features/new-customer-bidding): the feature on every platform and channel.
* [New customer bidding on any website with Cloudflare in Google Ads](/docs/bidding/new-customers/cloudflare-google-ads): the same feature on the other channel.
* [Returning customer bidding on any website with Cloudflare in Meta](/docs/bidding/returning-customers/cloudflare-meta): the other side of the split.
* [Any website (Cloudflare)](/docs/platforms/cloudflare) and [Meta](/docs/channels/meta): set-up and troubleshooting.
* [New and returning customers](/docs/concepts/new-and-returning-customers)
* On the website: [customer acquisition cost (CAC)](https://www.productmetrics.io/glossary/cac), [CAC to LTV calculator](https://www.productmetrics.io/cac-ltv-calculator)

Developers: do the same with the [CLI](/docs/cli/commands#store-data) or the [API](/docs/api/store-data/orders-list).
