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

# Enhanced conversions for Google Ads on any website with Cloudflare (/docs/tracking/enhanced-conversions/cloudflare-google-ads)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 2107 · updated: 2026-11-16 -->
Related: [Shopify enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/shopify-google-ads.md), [WooCommerce enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/woocommerce-google-ads.md), [Magento enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/magento-google-ads.md), [Lightspeed enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/lightspeed-google-ads.md), [Shopware enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/shopware-google-ads.md), [Shopify Meta Conversions API Advanced Matching](/docs/tracking/enhanced-conversions/shopify-meta.md)

> Send hashed customer data from your website with each Google Ads conversion, only when the visitor allowed ad user data.

On a website with Cloudflare Tracking, Product Metrics hashes **only the email address your site passes to Product Metrics** with **SHA-256** and sends it with each purchase conversion through Google's **Data Manager**, only when the visitor allowed **ad user data**. There is no Google tag setting and no code.

## 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). Google Ads needs [Merchant Center](/docs/using/merchant-center) connected.
* **[Server-side tracking for any website (Cloudflare) in Google Ads](/docs/tracking/server-side/cloudflare-google-ads)** set up first. It needs 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.
* **Admin access to the Google Ads account**, to accept the customer data terms.

## 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:** "Turn on Enhanced Conversions for my website (tracked with Cloudflare Tracking) in Google Ads 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:** "Turn on Enhanced Conversions for my website (tracked with Cloudflare Tracking) in Google Ads 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. Check server-side tracking runs

Enhanced conversions are not a separate switch: once the website sends orders to the **Product Metrics** conversion actions, each order carries the customer data it has.

**You should see:** every Product Metrics conversion action created under **Tracking → Conversion actions**. If not, finish [server-side tracking for any website (Cloudflare) in Google Ads](/docs/tracking/server-side/cloudflare-google-ads).

### 2. Set consent

In **Tracking → Configure consent**, choose the banner your website shows: OneTrust, Cookiebot, Usercentrics or Osano. What each choice lets through: [Consent](/docs/using/consent#what-each-choice-lets-through).

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

### 3. Accept Google's customer data terms

Google rejects conversions with customer data until the account accepts its terms. Only you can do this, in Google Ads.



![Two states of the Enhanced conversions card. Action required: Customer data terms Not accepted, with Open Google Ads settings and Re-check. Ready: Customer data terms Accepted, Enhanced conversions for leads On and Data Manager acceptance Accepted.](/docs/_assets/44b559493dce7db7f50904681df1f46acb236187a6420626f9d882590dca734d)

*Figure: Tracking → Google Ads → Enhanced conversions: Action required until the account accepts Google's customer data terms.*

1. In Product Metrics, open **Tracking → Google Ads**. Under **Enhanced conversions**, look at **Customer data terms**.
2. If it reads **Not accepted**, select **Open Google Ads settings**. Under **Customer data terms**, choose **View terms** and agree.
3. If **Data Manager acceptance** reads **Rejected**, select **Turn on enhanced conversions**. In Google Ads, open **Goals → Settings**, expand **Customer data use**, tick **Turn on enhanced conversions**, then agree and save.
4. Select **Re-check** in Product Metrics.



> **Note:** If Product Metrics says **Terms are managed on account** with another number, that is your manager account. Accept the terms there.

**You should see:** **Ready** under **Enhanced conversions**. **Re-check** runs a new check. What each state means:

| In the app                | What to do                                                                     |
| ------------------------- | ------------------------------------------------------------------------------ |
| **Ready**                 | Nothing. Customer data goes with every consented order.                        |
| **Setting up**            | Wait. Data Manager needs about 15 minutes to recognise new conversion actions. |
| **Action required**       | Accept the customer data terms, or turn on enhanced conversions (step 3).      |
| **Check failed**          | Reconnect Google Ads, or select **Re-check** in a moment.                      |
| **Not checked yet**       | Open **Tracking → Google Ads** and select **Re-check**.                        |
| **No Google Ads account** | Connect Google Ads first.                                                      |

### 4. Check an order

Place a test order through to your order confirmation page, then open **Tracking → Check your purchases**.

**You should see:** your order as **Last purchase received**. The check only proves the purchase arrived: it shows no customer data.

## Fields sent

| Customer data              | Where it comes from on Any website (Cloudflare)                           | Sent to Google Ads as                            |
| -------------------------- | ------------------------------------------------------------------------- | ------------------------------------------------ |
| Email address              | Only the email your site passes to Product Metrics; hashed in the browser | Hashed email                                     |
| Phone number               | Not available                                                             | —                                                |
| Name, country and postcode | Not available                                                             | —                                                |
| Ad click                   | The visitor's click on your ad                                            | gclid, gbraid or wbraid, with ad storage consent |
| New or returning customer  | Purchases Product Metrics has seen from this website                      | Sent with the conversion                         |

Product Metrics only sends what the website passed. It adds no checkout fields and guesses nothing.

## Troubleshooting

### Orders are missing in Google Ads

Check that **Tracking → Configure consent** names the banner your website actually shows ([step 2](#2-set-consent)).

## FAQ

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

No. Enhanced conversions aren't a separate switch: once your website sends orders to the **Product Metrics** conversion actions, each order carries the customer data it has. You accept Google's customer data terms once.

### Are phone and name sent from a website order?

No. A website order has no phone number, name, country or postcode, so Product Metrics sends none of them and guesses nothing.

### Are website customers marked as new or returning?

Yes. Product Metrics marks them from the purchases it has seen from this website and sends that with the conversion.

### What if a visitor declines ad user data?

Google Ads still receives the order when the visitor allowed ad storage, but without the hashed customer data. With neither ad user data nor ad storage, the order isn't sent.

## Where next

* [Any website (Cloudflare)](/docs/platforms/cloudflare): the full platform setup
* [Server-side tracking for any website (Cloudflare) in Google Ads](/docs/tracking/server-side/cloudflare-google-ads): the step before this one
* [Meta Conversions API on any website (Cloudflare)](/docs/tracking/enhanced-conversions/cloudflare-meta): the same customer data, sent to Meta
* [Google Ads](/docs/channels/google-ads): the channel setup and troubleshooting
* [Enhanced Conversions](/docs/features/enhanced-conversions): every platform and channel
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie), [GCLID](https://www.productmetrics.io/glossary/gclid)

Developers: do the same with the [CLI](/docs/cli/commands#stores-and-tracking) or the [API](/docs/api/stores-and-tracking/tracking-get-enhanced-conversions).
