Server-side tracking for Google Ads on any website with Cloudflare
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, through Google’s Data Manager. Nothing in the browser talks to Google, so an ad blocker has nothing to block.
Your domain on Cloudflare DNS and a Cloudflare sign-in.
Your Google Ads account, connected with Continue with Google.
Every paid order sent server-side to the eight Product Metrics conversion actions.
Set it up with AI
Connect your assistant
First time? Add the Product Metrics MCP server to your assistant, then paste the prompt below.
In Claude, choose Add custom connector; in ChatGPT, Settings → Apps & Connectors. Paste this URL:
https://www.productmetrics.io/mcpClaude Code: run this in your terminal.
claude mcp add --transport http product-metrics https://www.productmetrics.io/mcpSetting it up with AI takes one prompt and 60 seconds: paste it into your assistant.
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.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.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.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 in Product Metrics (editor is enough for the store and destination steps), with Pro (Full Signal Tracking). Google Ads needs 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).
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).
Open Ecommerce platforms
Go to Integrations → Ecommerce platforms. Under Unlock server-side conversion tracking, select Connect on Cloudflare Tracking.
Start the setup
The page lists three steps: add your website, link a property and connect Cloudflare. Select Connect Cloudflare Tracking.
Enter your website domain
Enter the domain your customers visit and select Connect. One installation per hostname.
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.
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.
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.
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.
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.
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.
Follow the next step
Once your store is connected and linked, the checklist opens the next open step. Each step says what it does.
Configure consent
Under Configure consent, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.
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.
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.
Then add your additional costs, so the profit actions carry profit (on a website, set Product cost fallback (%): website orders carry no product costs).
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.
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.
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. |
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. 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
The full platform setup.
What Product Metrics sends and how to troubleshoot it.
The same website, the other channel.
Add hashed customer data.
Every platform and channel.
On the website: Full Signal Tracking, ad blocker conversion tracking check, first-party cookie