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

# Enhanced Conversions, Meta Advanced Matching and OpenAI Conversions API (/docs/features/enhanced-conversions)

<!-- agent-signals: reading_time_min: 6 · est_tokens: 3157 · updated: 2026-11-16 -->
Related: [Server-side conversion tracking that gets through ad blockers](/docs/features/ad-blocker-proof-tracking.md), [Customer Match lists in Google Ads, updated after every order](/docs/features/customer-list.md), [LTV bidding: bid on customer lifetime value in Google Ads, Meta and ChatGPT Ads](/docs/features/ltv-bidding.md), [New customer bidding in Google Ads and Meta](/docs/features/new-customer-bidding.md), [POAS bidding: bid on profit in Google Ads, Meta and ChatGPT Ads](/docs/features/poas-bidding.md), [Returning customer bidding in Google Ads and Meta](/docs/features/returning-customer-bidding.md)

> Product Metrics adds SHA-256 hashed email, phone and name 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 and name, hashed with SHA-256**, with their country and postcode, 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](/docs/features/ad-blocker-proof-tracking).

## One feature, three names

| Channel                            | Called                                              | How it's sent                                                                  | Setup difference                                         |
| ---------------------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------ | -------------------------------------------------------- |
| [Google Ads](/docs/channels/google-ads) | **Enhanced Conversions**                            | Through Google's Data Manager, with each **Product Metrics** conversion action | Accept Google's customer data terms once                 |
| [Meta](/docs/channels/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 with unhashed country and postcode (Google's format), only as a complete set | 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 (when known) and user agent, not hashed. Meta needs the user agent: a website event without it isn't sent |

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](/docs/concepts/consent).

## 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:** "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."

**Claude Code or Codex:** "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](/docs/platforms/shopify)                     | Email, phone, name and address                                              | Shopify Customer Privacy, or your consent banner                                                         |
| [WooCommerce](/docs/platforms/woocommerce)             | Billing email, phone, name, postcode and country                            | Your consent banner                                                                                      |
| [Magento](/docs/platforms/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](/docs/platforms/lightspeed)               | Email (hashed in the browser), phone, name and address                      | Your consent banner                                                                                      |
| [Shopware](/docs/platforms/shopware)                   | Email, plus phone, name, postcode and country from the billing address      | Shopware's own cookie manager, or your consent banner                                                    |
| [Any website (Cloudflare)](/docs/platforms/cloudflare) | Only the email address your site passes, hashed in the browser              | Your consent banner                                                                                      |

## Set it up for your platform and channel



| Store                    | Google Ads                                                                        | Meta                                                                  | ChatGPT Ads                                                                    |
| ------------------------ | --------------------------------------------------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Shopify                  | [Shopify + Google Ads](/docs/tracking/enhanced-conversions/shopify-google-ads)         | [Shopify + Meta](/docs/tracking/enhanced-conversions/shopify-meta)         | [Shopify + ChatGPT Ads](/docs/tracking/enhanced-conversions/shopify-openai)         |
| WooCommerce              | [WooCommerce + Google Ads](/docs/tracking/enhanced-conversions/woocommerce-google-ads) | [WooCommerce + Meta](/docs/tracking/enhanced-conversions/woocommerce-meta) | [WooCommerce + ChatGPT Ads](/docs/tracking/enhanced-conversions/woocommerce-openai) |
| Magento                  | [Magento + Google Ads](/docs/tracking/enhanced-conversions/magento-google-ads)         | [Magento + Meta](/docs/tracking/enhanced-conversions/magento-meta)         | [Magento + ChatGPT Ads](/docs/tracking/enhanced-conversions/magento-openai)         |
| Lightspeed               | [Lightspeed + Google Ads](/docs/tracking/enhanced-conversions/lightspeed-google-ads)   | [Lightspeed + Meta](/docs/tracking/enhanced-conversions/lightspeed-meta)   | [Lightspeed + ChatGPT Ads](/docs/tracking/enhanced-conversions/lightspeed-openai)   |
| Shopware                 | [Shopware + Google Ads](/docs/tracking/enhanced-conversions/shopware-google-ads)       | [Shopware + Meta](/docs/tracking/enhanced-conversions/shopware-meta)       | [Shopware + ChatGPT Ads](/docs/tracking/enhanced-conversions/shopware-openai)       |
| Any website (Cloudflare) | [Website + Google Ads](/docs/tracking/enhanced-conversions/cloudflare-google-ads)      | [Website + Meta](/docs/tracking/enhanced-conversions/cloudflare-meta)      | [Website + ChatGPT Ads](/docs/tracking/enhanced-conversions/cloudflare-openai)      |

## 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. Google Ads takes country and postcode unhashed, and Meta takes 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](/docs/features/ad-blocker-proof-tracking): how the orders themselves get through ad blockers
* [Consent](/docs/concepts/consent): which choice unlocks which data
* [Google Ads](/docs/channels/google-ads) and [Meta](/docs/channels/meta): the channel setup and troubleshooting
* [Customer lists](/docs/features/customer-list): the same customer data, as Google Ads Customer Match lists
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [GCLID](https://www.productmetrics.io/glossary/gclid), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie)

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