> ## 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

# Customer Match lists in Google Ads on any website with Cloudflare (/docs/tracking/customer-lists/cloudflare-google-ads)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1811 · updated: 2026-11-16 -->
Related: [Lightspeed Customer Match lists in Google Ads](/docs/tracking/customer-lists/lightspeed-google-ads.md), [Magento Customer Match lists in Google Ads](/docs/tracking/customer-lists/magento-google-ads.md), [Shopify Customer Match lists in Google Ads](/docs/tracking/customer-lists/shopify-google-ads.md), [Shopware Customer Match lists in Google Ads](/docs/tracking/customer-lists/shopware-google-ads.md), [WooCommerce Customer Match lists in Google Ads](/docs/tracking/customer-lists/woocommerce-google-ads.md), [What is Product Metrics?](/docs/overview/what-is-product-metrics.md)

> Create six Customer Match lists in Google Ads and keep them filled from your website, from first-time buyers to lapsed customers.

Product Metrics creates six **Customer Match** lists in your Google Ads account and keeps them up to date from your website orders, moving each customer to the right lists after every purchase (for example from **First-time buyers** to **Second-time buyers**). You choose where to use them: Product Metrics never changes your campaigns.

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics, with Pro (Full Signal Tracking). Google Ads needs [Merchant Center](/docs/using/merchant-center) connected.
* **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).
* **Google Ads connected** to your property, with its conversion actions created and conversion tracking on in Google Ads, and a Google login allowed to manage the account, to accept the Customer Match terms. See [Google Ads](/docs/channels/google-ads).

## 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:** "Create the six Product Metrics customer lists for my website (tracked with Cloudflare Tracking) in Google Ads and keep them filled. 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:** "Create the six Product Metrics customer lists for my website (tracked with Cloudflare Tracking) in Google Ads and keep them filled. 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 your website recognises customers



**How it works on a website**

* **Customer:** The email address your purchase page passes to Product Metrics
* **Counted orders:** Purchases your order confirmation page reports
* **History:** The page reports no order history, so a customer's history starts with the first purchase Product Metrics receives from your website. Refunds and cancellations count.
* **Sent to Google:** Hashed email and phone and, when all four are known, hashed first and last name with unhashed country and postcode, from what your purchase page passes to Product Metrics
* **High-value threshold:** Profit when every order in the window has known costs, else revenue. Set once 50 customers ordered in the last 365 days; recalculated every 30 days

Each member stays on a list for 540 days. Everything is hashed with SHA-256 and sent through Google's Data Manager. A privacy request that deletes a customer's data removes them from every list.

Place a test order.



> **Note:** Want earlier orders to count? **Custom Store / Webhook Integration** lets a developer send every order from your backend, including the customer's order history.

**You should see:** your test order as the last purchase received.

### 2. Set consent

In **Tracking → Configure consent**, choose the banner your website shows: OneTrust, Cookiebot, Usercentrics or Osano. A customer **joins** a list only when the visitor allowed both **ad user data** and **ad personalisation**. **Leaving** a list never needs consent: Product Metrics always removes a customer who no longer qualifies. See [Consent](/docs/concepts/consent).



![The Configure consent step with the consent platform list open: Not configured, Shopify Customer Privacy, OneTrust, Cookiebot, Usercentrics and Osano.](/docs/_assets/eb2d6e767cb722a4f9fc28ca607791b9b73c69ea9e416f3e8d76cb286dec18d6)

*Figure: Configure consent: choose the banner your store shows visitors.*

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

### 3. Accept the Customer Match terms

Google Ads only accepts customer lists once the account has accepted its Customer Match terms. You do this yourself in the Google Ads web interface.

**You should see:** creating the lists in the next step doesn't fail with a Customer Match terms error.

### 4. Create the lists

Product Metrics creates the six lists ([who joins each](/docs/features/customer-list#the-six-lists)), or adopts matching ones it already manages, and tags each with its Google Ads customer type.

In Product Metrics, select **Tracking** → **Google Ads** → **Customer lists** → **Create 6 customer lists**.

**You should see:** all six lists created. If some lists exist already, the button reads **Create 2 missing customer lists** or **Set up 1 customer list**.

### 5. Use the lists in your campaigns

In Google Ads, the lists appear with your other audience lists as **Product Metrics - \[list] - \[your website]**. For example:

* Exclude **All customers** from a campaign that should only find new customers.
* Use **Lapsed customers** to win back customers who haven't ordered in six months.
* Tell Performance Max who your **High-value customers** are.

Customers join with their next purchase after the lists exist; the lists fill up from there.

**You should see:** the lists show members in Google Ads.

## Troubleshooting

### Creating the lists fails with a Customer Match terms error

Accept the Customer Match terms in the Google Ads web interface, then create the lists again.

## FAQ

### Are refunds and cancellations reflected in the lists?

Yes. Product Metrics tracks refunds and cancellations on your website, and a refund removes the customer from the list.

### Do my customers' earlier orders count?

No. A customer's history starts with the first purchase Product Metrics receives from your website. To include earlier orders, a developer can send the customer's order history through **Custom Store / Webhook Integration**.

### Which cookie banners work with website customer lists?

OneTrust, Cookiebot, Usercentrics or Osano. A customer joins a list only when the visitor allowed both ad user data and ad personalisation.

### Can I use these customer lists in Meta?

No. Customer lists are Google Ads only: Product Metrics doesn't create Meta Custom Audiences.

## Where next

* [Customer lists](/docs/features/customer-list): every platform, and what each error means
* [Any website (Cloudflare)](/docs/platforms/cloudflare): the full website setup
* [Google Ads](/docs/channels/google-ads): conversion actions, Enhanced Conversions and troubleshooting
* [LTV bidding on any website (Cloudflare) in Google Ads](/docs/bidding/ltv/cloudflare-google-ads): bid on the same customers' lifetime value
* [New and returning customers](/docs/concepts/new-and-returning-customers): how a customer is recognised
* On the website: [repeat purchase rate](https://www.productmetrics.io/glossary/repeat-purchase-rate), [pricing](https://www.productmetrics.io/pricing)

Developers: do the same with the [CLI](/docs/cli/commands#google-ads) or the [API](/docs/api/google-ads/create-customer-lists).
