Skip to content
Google Ads

WooCommerce enhanced conversions for Google Ads

Send hashed customer data from WooCommerce orders with each Google Ads conversion, only when the visitor allowed ad user data.

On WooCommerce, Product Metrics hashes the order’s billing email, phone and name with SHA-256 and sends them, plus the billing country and postcode, 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.

WooCommerce

The WordPress plugin, connected with a one-time setup token.

Google Ads

Your Google Ads account, connected with Continue with Google.

Result

Hashed customer data with each Google Ads conversion, when the visitor allowed ad user data.

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/mcp

Claude Code: run this in your terminal.

claude mcp add --transport http product-metrics https://www.productmetrics.io/mcp

CodexAll clients and details →

Setting it up with AI takes one prompt and 60 seconds: paste it into your assistant.

Turn on Enhanced Conversions for my WooCommerce store 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.
Turn on Enhanced Conversions for my WooCommerce store 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.
Turn on Enhanced Conversions for my WooCommerce store 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.
Turn on Enhanced Conversions for my WooCommerce store 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.
  • Server-side tracking for WooCommerce in Google Ads set up first.
  • Your WooCommerce store connected: a WordPress administrator login, WordPress 6.4+ and PHP 8.1+ with WP-Cron running, and the shop at the root of an HTTPS domain (no subfolder, no custom port). You install the Product Metrics plugin, connect it with a one-time setup token, choose your paid order statuses and link the store to your property. See WooCommerce.
  • Admin access to the Google Ads account, to accept the customer data terms.

In the app

1. Check server-side tracking runs

Enhanced conversions are not a separate switch: once the store 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 WooCommerce in Google Ads.

In Tracking → Configure consent, choose the banner your store shows: OneTrust, Cookiebot, Usercentrics or Osano. After you change it, clear your full-page cache so every page loads the new setting. With Not configured, nothing is treated as allowed. What each choice lets through: 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.

Tracking in Product Metrics with the Complete your tracking setup checklist of six steps, starting with Connect your store.

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.

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.

You should see: Tracking → Configure consent names the banner your store 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.

  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.

Review the Google Ads destination

Open Tracking → Google Ads. The panel shows the connection, the conversion actions, profit tracking and, under Enhanced conversions, whether Google’s Customer data terms are accepted.

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 appWhat to do
ReadyNothing. Customer data goes with every consented order.
Setting upWait. Data Manager needs about 15 minutes to recognise new conversion actions.
Action requiredAccept the customer data terms, or turn on enhanced conversions (step 3).
Check failedReconnect Google Ads, or select Re-check in a moment.
Not checked yetOpen Tracking → Google Ads and select Re-check.
No Google Ads accountConnect Google Ads first.

4. Check an order

In WordPress, select Verify with next paid order under WooCommerce → Product Metrics, place and pay for a test order within ten minutes, then select Refresh connection status.

You should see: Live order delivery reads Verified.

Fields sent

Customer dataWhere it comes from on WooCommerceSent to Google Ads as
Email addressThe order’s billing emailHashed email
Phone numberThe order’s billing phoneHashed phone, with the country code and +
Name, country and postcodeThe order’s billing addressHashed first and last name, with country and postcode unhashed (Google’s format), only as a complete set
Ad clickThe visitor’s click on your adgclid, gbraid or wbraid, with ad storage consent
New or returning customerThe customer’s order historySent with the conversion

Product Metrics only sends what the order already has. It adds no checkout fields and guesses nothing.

Troubleshooting

ProblemFix
Nothing reaches Google AdsCheck that Tracking → Configure consent names the banner your store shows. Left on Not configured, Product Metrics can’t read the visitor’s choice and treats it as not given.

FAQ

Do I need Google Tag Manager for Enhanced Conversions?

No. Product Metrics sends the hashed customer data server-side with each order through Google’s Data Manager, so there is no Google tag setting and no code on your WooCommerce store.

Does it use the billing or the shipping details?

The billing details: the order’s billing email, phone and name, hashed with SHA-256. The name only goes as a complete set with country and postcode, which Google takes unhashed.

Yes. After you change the banner under Tracking → Configure consent, clear your full-page cache so every page loads the new setting.

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

On the website: Full Signal Tracking, first-party cookie, GCLID, Product Metrics for WooCommerce

Developers: do the same with the CLI or the API.