Enhanced Conversions, Meta Advanced Matching and OpenAI Conversions API
Product Metrics adds SHA-256 hashed email, phone, name and postcode to each paid order it sends to Google Ads, the Meta Conversions API (Advanced Matching) and the OpenAI Conversions API, only when the visitor allowed ad user data.
With every paid order it sends server-side, Product Metrics adds the customer’s email, phone, name and postcode, hashed with SHA-256, so the ad platform can match the sale to the person who clicked. It reads them from the order your shop already has, and adds them only when the visitor allowed ad user data in your cookie banner.
No code, no Google tag setting. The orders themselves are sent server-side: see Server-side tracking.
One feature, three names
| Channel | Called | How it’s sent | Setup difference |
|---|---|---|---|
| Google Ads | Enhanced Conversions | Through Google’s Data Manager, with each Product Metrics conversion action | Accept Google’s customer data terms once |
| Meta | Meta Conversions API with Advanced Matching | With each event: Purchase and the Product Metrics custom events | None after saving the Meta Conversions API destination |
| ChatGPT Ads (OpenAI) | OpenAI Conversions API | With each event sent to your ChatGPT Ads pixel | None after saving the OpenAI Conversions API destination |
What Product Metrics sends
| Customer data | Google Ads | Meta Conversions API |
|---|---|---|
| Email address | Hashed | Hashed |
| Phone number | Hashed, with the country code and + | Hashed, digits only with the country code |
| First and last name, country and postcode | Hashed name, sent only as a complete set with country and postcode | Hashed first name, last name, postcode and country |
| Your shop’s customer ID | Not sent | Hashed |
| Ad click | Google click ID (gclid, gbraid or wbraid) | Meta browser and click cookies |
| Browser | Not sent | IP address and user agent, not hashed (Meta requires them unhashed) |
Product Metrics only sends what your shop already collected on the order. It doesn’t add checkout fields or guess missing details.
Consent rules
| Visitor allowed | Google Ads | Meta Conversions API |
|---|---|---|
| Ad user data | The hashed customer data goes with the order | The event can be sent at all, with the hashed customer data |
| Ad storage | The ad click ID goes with the order | Meta’s browser and click cookies go with the event |
| Analytics storage | Not needed | Also needed for the Product Metrics custom events |
Google Ads receives an order when the visitor allowed at least one of ad user data or ad storage. Meta has no consent mode: without ad user data, nothing is sent. If the visitor withdraws consent before the order is sent, it isn’t. See Consent.
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/mcpPaste the prompt into your assistant.
Check that Enhanced Conversions are ready in Google Ads for my store with Product Metrics, and that my Meta and ChatGPT Ads destinations send customer data. Walk me through anything open and give me the link when I need to click something.Check that Enhanced Conversions are ready in Google Ads for my store with Product Metrics, and that my Meta and ChatGPT Ads destinations send customer data. Walk me through anything open and give me the link when I need to click something.Check that Enhanced Conversions are ready in Google Ads for my store with Product Metrics, and that my Meta and ChatGPT Ads destinations are connected; tell me what I still need to do. 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).Check that Enhanced Conversions are ready in Google Ads for my store with Product Metrics, and that my Meta and ChatGPT Ads destinations are connected; tell me what I still need to do. 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).In the app
Google Ads is the only channel with a readiness check, because Google has to accept its customer data terms first. Meta and ChatGPT Ads need nothing after you save their destination.
1. Accept the customer data terms
In Tracking → Google Ads, under Enhanced conversions, select Open Google Ads settings and accept the Customer data terms in Google Ads.
2. Turn on enhanced conversions
If the app shows Turn on enhanced conversions, follow it and turn them on in Google Ads under Goals → Settings → Customer data use.
3. Re-check
Select Re-check.
You should see Ready. Setting up is normal for about 15 minutes after the conversion actions are created; Action required means step 1 or 2 is still open.
By platform
| Platform | Customer data on the order | Consent read from |
|---|---|---|
| Shopify | Email, phone, name and address | Shopify Customer Privacy, or your consent banner |
| WooCommerce | Billing email, phone, name, postcode and country | Your consent banner |
| Magento | The order, plus the logged-in customer and guest email passed by the module | Your consent banner, or consent your developer passes: Magento’s own cookie notice doesn’t grant consent |
| Lightspeed | Email (hashed in the browser), phone, name and address | Your consent banner |
| Shopware | Email, plus phone, name, postcode and country from the billing address | Shopware’s own cookie manager, or your consent banner |
| Any website (Cloudflare) | Only the email address your site passes, hashed in the browser | Your consent banner |
Set it up for your platform and channel
FAQ
Do I need Google Tag Manager for Enhanced Conversions?
Not with Product Metrics: it sends the hashed customer data server-side with each order, with no Google tag setting and no code. In Google Ads, you accept Google’s customer data terms once. If you set up Enhanced Conversions yourself instead, you do need Google Tag Manager or the Google tag.
Is customer data sent when a visitor declines consent?
Not without ad user data. Google Ads still receives the order if the visitor allowed ad storage, but without customer data; Meta and ChatGPT Ads receive nothing.
Is the customer data sent in plain text?
No. Product Metrics hashes the email, phone and name with SHA-256 before sending them. Meta requires the IP address and user agent unhashed, so those go as they are.
Does Product Metrics add checkout fields to get more data?
No. It sends only what your shop already collected on the order, and guesses no missing details.
Where next
- Server-side tracking: how the orders themselves get through ad blockers
- Consent: which choice unlocks which data
- Google Ads and Meta: the channel setup and troubleshooting
- Customer lists: the same customer data, as Google Ads Customer Match lists
- On the website: Full Signal Tracking, GCLID, first-party cookie