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

# Server-side tracking with the Meta Conversions API on any website with Cloudflare (/docs/tracking/server-side/cloudflare-meta)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1849 · updated: 2026-11-16 -->
Related: [Shopify server-side tracking for Google Ads](/docs/tracking/server-side/shopify-google-ads.md), [WooCommerce server-side tracking for Google Ads](/docs/tracking/server-side/woocommerce-google-ads.md), [Magento server-side tracking for Google Ads](/docs/tracking/server-side/magento-google-ads.md), [Lightspeed server-side tracking for Google Ads](/docs/tracking/server-side/lightspeed-google-ads.md), [Shopware server-side tracking for Google Ads](/docs/tracking/server-side/shopware-google-ads.md), [Server-side tracking for Google Ads on any website with Cloudflare](/docs/tracking/server-side/cloudflare-google-ads.md)

> Send every purchase from your website to Meta from the server through the Meta Conversions API, with Advanced Matching and the script served from your own domain.

Each purchase is confirmed from **the purchase your order confirmation page reports** and sent to your Meta pixel [from the server](/docs/concepts/server-side-tracking), through the **Meta Conversions API**. Nothing in the browser talks to Meta, so an [ad blocker](/docs/features/ad-blocker-proof-tracking) has nothing to block. Each event carries hashed customer data for [Advanced Matching](/docs/tracking/enhanced-conversions/cloudflare-meta).

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking).
* **Your website's domain on Cloudflare DNS**, with its record proxied (the orange cloud), and a workspace admin who can sign in to that Cloudflare account.
* **Access to your pixel in Meta Events Manager**, to copy its ID and generate a Conversions API access token.

## 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 server-side conversion tracking 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."

**Claude Code or Codex:** "Set up server-side conversion tracking 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

* **Website:** add your website in Product Metrics, then sign in to Cloudflare and link the website to your property. See [Any website (Cloudflare)](/docs/platforms/cloudflare).
* **Meta:** in Events Manager, copy your **Pixel or Dataset ID** and generate a Conversions API access token, then add both under **Tracking → Meta Conversions API → Connect Meta** and send a test event. See [Meta](/docs/channels/meta).



![The Add Meta destination form with Pixel or Dataset ID, Access token, Test event code (optional) and the Send events to Meta switch, then the saved Meta Conversions API destination showing Active, the access token Accepted by Meta and Sending On.](/docs/_assets/b8f3701ffab8399a9aad9788c63abe4161115d01a029732731a74012315454bb)

*Figure: Add Meta destination: paste the Pixel or Dataset ID and access token, keep Send events to Meta on.*

**You should see:** the gateway card says **Gateway setup complete**; Events Manager shows the test event under **Test events**.

### 2. Choose your consent banner

In Product Metrics, open **Tracking → Configure consent** and choose the banner your website shows: OneTrust, Cookiebot, Usercentrics or Osano. See [Consent](/docs/concepts/consent).



> **Warning:** Meta has no consent mode. Product Metrics sends an event only when the visitor allowed ad user data; the custom events also need analytics consent. A wrong banner here means nothing reaches Meta.

**You should see:** **Configure consent** names the banner your website actually shows.

### 3. Create custom conversions

In Events Manager, create a custom conversion for each Product Metrics value you want to bid on, with the rule `pm_purpose` equals the purpose: `PMOrderRevenue` (`ORDER_REVENUE`) for revenue, `PMOrderProfit` (`ORDER_PROFIT`) for profit, every other event in [Meta events](/docs/concepts/conversion-actions-and-events#meta-events). Follow [Create custom conversions in Meta](/docs/using/conversion-actions#custom-conversions-in-meta) once a test order has reached Meta.

**You should see:** your custom conversions show in Events Manager.

### 4. Check it works

**Place a test order** through to the order confirmation page.

**You should see:** **Tracking → Check your purchases** shows **Last purchase received** within two minutes, and **Live endpoints** lists the **Tracking SDK** and **Event collector** on your domain; in Events Manager, the order shows as `Purchase`, plus the Product Metrics custom events your visitor's consent allows. More checks: [Check tracking works](/docs/using/check-tracking).



**How it works on a website**

* **Script and collector served by:** A Cloudflare gateway (a Worker on your website's Cloudflare zone) that serves the **Tracking SDK** and **Event collector** on your own domain. Setup is only signing in to Cloudflare: no code, and Product Metrics never changes your DNS
* **Purchase confirmed from:** The purchase your order confirmation page reports
* **Sent:** When your order confirmation page reports the purchase; if it reports the same order twice, the first report wins
* **Delivered:** Server-side, through the Meta Conversions API: `Purchase` plus the Product Metrics custom events
* **Refunds and cancellations:** Tracked by Product Metrics; sent events aren't revised. Meta refuses events more than 7 days old
* **Consent read from:** OneTrust, Cookiebot, Usercentrics or Osano

## Troubleshooting

### The event isn't in Meta's custom conversion selector

Meta lists an event only after it received it. Place a test order with all cookies accepted, then create the custom conversion.

## FAQ

### Do I need to change my website's code for Meta?

No. Setup is signing in to Cloudflare: a gateway on your zone serves the Tracking SDK and Event collector on your own domain, and the order goes to Meta through the Meta Conversions API.

### Can I keep my Meta pixel?

Yes. Meta counts an event once when the pixel and the Meta Conversions API send the same event name and event ID within 48 hours. `Purchase` uses the order transaction ID, so it deduplicates on its own.

### How does Meta get profit from my website orders?

Website orders carry no product costs, so set **Product cost fallback (%)** plus your additional costs under [Costs](/docs/using/costs). `PMOrderProfit` then carries profit; a loss-making order is sent with value 0, as Meta accepts no negative value.

### Are refunds on my website sent to Meta?

No. Product Metrics tracks the refund in your profit and lifetime value, but sent Meta events aren't revised.

## Where next

* [Any website (Cloudflare)](/docs/platforms/cloudflare): the full platform setup
* [Meta](/docs/channels/meta): what Product Metrics sends and how to troubleshoot it
* [Server-side tracking for any website (Cloudflare) in Google Ads](/docs/tracking/server-side/cloudflare-google-ads): the same website, the other channel
* [Meta Conversions API on any website (Cloudflare)](/docs/tracking/enhanced-conversions/cloudflare-meta): the customer data each event carries
* [Server-side conversion tracking](/docs/features/ad-blocker-proof-tracking): every platform and channel
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [ad blocker conversion tracking check](https://www.productmetrics.io/ad-blocker-conversion-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie)

Developers: do the same with the [CLI](/docs/cli/commands#destinations) or the [API](/docs/api/destinations/set-meta).
