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

# Server-side tracking for Google Ads on any website with Cloudflare (/docs/tracking/server-side/cloudflare-google-ads)

<!-- agent-signals: reading_time_min: 9 · est_tokens: 3914 · updated: 2026-11-17 -->
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), [Shopify server-side tracking with the Meta Conversions API](/docs/tracking/server-side/shopify-meta.md)

> Send every purchase from your website to Google Ads from the server, with the script served from your own domain.

Each purchase is confirmed from **the purchase your order confirmation page reports** and sent to Google Ads [from the server](/docs/concepts/server-side-tracking), through Google's **Data Manager**. Nothing in the browser talks to Google, so an [ad blocker](/docs/features/ad-blocker-proof-tracking) has nothing to block.



* **Store:** [Any website (Cloudflare)](/docs/platforms/cloudflare). Your domain on Cloudflare DNS and a Cloudflare sign-in.
* **Channel:** [Google Ads](/docs/channels/google-ads). Your Google Ads account, connected with Continue with Google.
* **Result:** Every paid order sent server-side to the eight **Product Metrics** conversion actions.

## Set it up with AI



Setting it up with AI takes one prompt and 60 seconds: paste it 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 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:** "Set up server-side conversion tracking 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."

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

## In the app

### 1. Connect your website and Google Ads

**Website:** add your website in Product Metrics, then sign in to Cloudflare. See [Any website (Cloudflare)](/docs/platforms/cloudflare).



1. **Open Ecommerce platforms.** Go to **Integrations → Ecommerce platforms**. Under **Unlock server-side conversion tracking**, select **Connect** on **Cloudflare Tracking**.

   ![The Unlock server-side conversion tracking section at the bottom of Ecommerce platforms, for any website on a platform not listed above: Cloudflare Tracking, Track every sale server-side on your own domain, with a Connect button.](/docs/_assets/8820daec93b28f5786ee9afbc911958a2ff2a6612725f3f423094f16fa35898f)

2. **Start the setup.** The page lists three steps: add your website, link a property and connect Cloudflare. Select **Connect Cloudflare Tracking**.

   ![The Cloudflare Tracking page under Integrations → Ecommerce platforms: 0 of 3 steps done, step 1 Add your website with the Connect Cloudflare Tracking button, then Link a property and Connect Cloudflare.](/docs/_assets/979d8250dd1db29c1caca685a6c1162f5130bfd8a72b575129ef6ed11722aeaf)

3. **Enter your website domain.** Enter the domain your customers visit and select **Connect**. One installation per hostname.

   ![The Connect Cloudflare Tracking dialog, for any website using Cloudflare DNS: an empty Your website domain field and the Cancel and Connect buttons.](/docs/_assets/ede7bed40075b1056a2c009a2642f756a36280f1ec705b4633b9e0d32b31dea4)

**Google Ads:** connect it in onboarding (**Connect Google Ads and Merchant Center**) or on **Integrations**, pick the client account that runs your campaigns and grant Data Manager access. See [Google Ads](/docs/channels/google-ads).



1. **Connect Google.** On **Connect Google Ads and Merchant Center**, select **Continue as** your Google account and sign in with the account that can see your Google Ads. Tick **Google Ads** on Google's screen: Merchant Center connects with the same sign-in.

   ![The Connect step of onboarding, Connect Google Ads and Merchant Center: Google Ads and Merchant Center both Not connected, a Use our manager account link for when you can't sign in with that Google account, and the Continue as sam@northwind-outfitters.example button.](/docs/_assets/0d2be369dbe5104c735cd1c7373a8e7ff08264ebea02c129bd51097490f525e3)

   *Example data.*

2. **Pick the client account.** Choose the Google Ads **client account** that runs your campaigns, not a manager account. The workspace is named after the account you pick.

   ![The account step of onboarding: the Google Ads accounts the signed-in Google account can see, to pick the one Product Metrics should analyse.](/docs/_assets/0e327319a8a785046273763a2be1b6d2c546e1fa773c5ec87ee2c64687e06c9c)

   *Example data.*

Already have a workspace? Open **Integrations** and select **Connect Google Ads** on the **Google Ads** row (**Add account** once one is connected). The same sign-in and account steps follow.

![Integrations in Product Metrics: the required connections first, Google Ads and Merchant Center with your product feed, each row with its status and one action.](/docs/_assets/e7a64e8fb340c3708610b6de560704e9a8c3bbc87fbac246c364f0024392700d)

*Example data.*

**Connect through our manager account instead**

Use this when you can't sign in with a Google account that can see your Google Ads. Product Metrics' manager account invites your Google Ads account, with access to that one account only.

1. **Choose the manager account.** On the **Connect** step, select **Use our manager account**.

   ![The Connect step of onboarding with the Use our manager account link, for when you can't sign in with the Google account that sees your Google Ads.](/docs/_assets/4795c769c1dc46b2348ec5796a84155e4bb0f4d0de7212fffd32ca30801c7727)

2. **Name the workspace.** Enter a name for the workspace the invite belongs to, then select **Continue**.

   ![The workspace name field of the manager account route, with the Continue button.](/docs/_assets/4fa654128e9a60d95e2ae0545925409921419a320e8b5f14f87d092342f2b85e)

3. **Enter your customer ID.** Enter your Google Ads customer ID and select **Send invite**.

   ![The Use our manager account form on the Connect step: enter the account's customer ID and send the invite, the account owner accepts it in Google Ads under Admin → Access and security → Managers, and Product Metrics checks access every 2 minutes. A Google Ads customer ID field, a Check access link, Connect with Google instead, and the Send invite button.](/docs/_assets/eaee093b9a33fc6b0e91382fb830909287363dcdfbdccd09a822b1be7a2fb4c1)

4. **Accept the invite in Google Ads.** In Google Ads, open **Admin → Access and security → Managers** and accept the invite. Product Metrics checks access every few minutes and starts the analysis once it has access.

**You should see:** the gateway card says **Gateway setup complete**; your Google Ads account shows on **Integrations**.

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



1. **Open Tracking.** Go to **Integrations → Tracking**. The checklist shows six steps: start by connecting your store, or use Cloudflare Tracking if you have no store platform.

   ![Tracking in Product Metrics with the Complete your tracking setup checklist of six steps, starting with Connect your store.](/docs/_assets/09a584afb1797a0439b68310c4d6085412eafebba1524c019f42a90f3ed4ea37)

2. **Follow the next step.** Once your store is connected and linked, the checklist opens the next open step. Each step says what it does.

   ![The Complete your tracking setup checklist in Tracking: 3 of 6 essential steps completed, with Connect your store, Link the store to this property and Install storefront tracking ticked, and Configure consent open as step 4 with the consent platform still Not configured.](/docs/_assets/b385237058280a34dca53f7f1e42704faa9a8aee59024bd5baafc2211e201e7e)

3. **Configure consent.** Under **Configure consent**, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.

   ![The Configure consent step in the tracking checklist, with the list of consent platforms to choose from.](/docs/_assets/f0a8d61eaa086657ce840c85899df48d5f3a7a52fb6c552710f93b1482b90e72)

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

### 3. Create the conversion actions

In Product Metrics, select **Tracking** → **Create Google Ads conversions** → **Create 8 conversion actions**. All eight are **secondary**, so nothing changes in your campaigns until you make one primary. See [Conversion actions](/docs/using/conversion-actions).



1. **Create Google Ads conversions.** Under **Create Google Ads conversions**, select **Create 8 conversion actions**. Product Metrics manages one Google Ads conversion action per purpose; they start as secondary goals, and you choose the primary goal in Google Ads.

   ![The Conversion actions page in Product Metrics, opened from Tracking: Not configured, 0 of 8 managed and the Create 8 conversion actions button. Below it, Customer types (New customer revenue and profit, Returning customer revenue and profit) and Order value (Order revenue, Order profit), each Missing with Google goal status Unknown, and the Lifetime value group.](/docs/_assets/816fdc81f1068f5d013a17d0d26166a0834cc61c69943d0c05d5171b557e0652)

Then [add your additional costs](/docs/using/costs), so the profit actions carry profit (on a website, set **Product cost fallback (%)**: website orders carry no product costs).



1. **Add your additional costs.** Product costs come from your store where it reports them. Under **Add your additional costs**, add shipping, handling, returns and payment fees, set **Product cost fallback (%)** and select **Activate additional costs**, so the profit conversions carry real profit.

   ![The Add your additional costs step in Tracking, prefilled for your country: shipping, handling, returns and payment fee fields, a Product cost fallback (%) field and the Activate additional costs button.](/docs/_assets/9aa53f961b1d7a0f43c3ebdccb7dfda4cb044d52cf5c7d4cd3b10fc95a7083fb)

**You should see:** the badge next to **Tracking** reads **Tracking active**.

### 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. More checks: [Check tracking works](/docs/using/check-tracking).

## How it works on a website

|                                    | 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 Google's Data Manager, to the eight **Product Metrics** conversion actions                                                                                                                                            |
| **Refunds and cancellations**      | Product Metrics adjusts the conversion when the order is refunded or cancelled                                                                                                                                                             |
| **Consent read from**              | OneTrust, Cookiebot, Usercentrics or Osano                                                                                                                                                                                                 |

## Troubleshooting

| Problem                              | Fix                                                                                                                                                                                               |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Orders are missing in Google Ads** | Check that **Tracking → Configure consent** names the banner your website actually shows: Product Metrics sends an order only with the consent this page lists. See [Consent](/docs/concepts/consent). |

## FAQ

### Do I need to change my website's code or DNS?

No. Setup is signing in to Cloudflare: a gateway on your Cloudflare zone serves the Tracking SDK and Event collector on your own domain, and Product Metrics never changes your DNS.

### How do the profit actions work without product costs?

Website orders carry no product costs, so set **Product cost fallback (%)** and add your additional costs under [Costs](/docs/using/costs). **Product Metrics - Profit** then carries profit for POAS bidding.

### Are refunds on my website sent to Google Ads?

Yes. Product Metrics adjusts the conversion when the order is refunded or cancelled.

### What if the confirmation page reports an order twice?

The first report wins, so reloading the order confirmation page doesn't send a second conversion.

## Where next



* [Any website (Cloudflare)](/docs/platforms/cloudflare): the full platform setup
* [Google Ads](/docs/channels/google-ads): what Product Metrics sends and how to troubleshoot it
* [Server-side tracking for any website (Cloudflare) in Meta](/docs/tracking/server-side/cloudflare-meta): the same website, the other channel
* [Enhanced conversions for any website (Cloudflare) in Google Ads](/docs/tracking/enhanced-conversions/cloudflare-google-ads): add hashed customer data
* [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#google-ads) or the [API](/docs/api/google-ads/create-conversion-actions).
