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

# Shopify Meta Conversions API Advanced Matching (/docs/tracking/enhanced-conversions/shopify-meta)

<!-- agent-signals: reading_time_min: 5 · est_tokens: 1708 · updated: 2026-11-16 -->
Related: [Shopify enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/shopify-google-ads.md), [WooCommerce enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/woocommerce-google-ads.md), [Magento enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/magento-google-ads.md), [Lightspeed enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/lightspeed-google-ads.md), [Shopware enhanced conversions for Google Ads](/docs/tracking/enhanced-conversions/shopware-google-ads.md), [Enhanced conversions for Google Ads on any website with Cloudflare](/docs/tracking/enhanced-conversions/cloudflare-google-ads.md)

> Send hashed customer information from Shopify orders with every Meta Conversions API event (Advanced Matching), only when the visitor allowed ad user data.

Every event Product Metrics sends through the **Meta Conversions API** carries customer information so Meta can match it to a person (**Advanced Matching**): on Shopify, **email, phone, name and address from the Shopify order**, hashed with **SHA-256**, plus the visitor's IP address and browser. There is no extra switch: once the destination is saved, every consented event carries it.

## Prerequisites

* **[Workspace admin](/docs/using/team#1-choose-a-role)** in Product Metrics (editor is enough for the store and destination steps).
* **[Server-side tracking for Shopify in Meta](/docs/tracking/server-side/shopify-meta)** set up first. It needs a Shopify login that can install apps and edit the theme, and a Product Metrics subscription on the store.

## 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 Product Metrics sends customer data with my Meta Conversions API events from my Shopify store. 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:** "Check that Product Metrics sends customer data with my Meta Conversions API events from my Shopify store. 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."

## In the app

### 1. Check the Meta Conversions API is connected

In Product Metrics, open **Tracking → Meta Conversions API**.



![The Add Meta destination form with Pixel or Dataset ID, Access token, Test event code (optional) and the Send events to Meta switch, then the saved Meta Conversions API destination showing Active, the access token Accepted by Meta and Sending On.](/docs/_assets/b8f3701ffab8399a9aad9788c63abe4161115d01a029732731a74012315454bb)

*Figure: Add Meta destination: paste the Pixel or Dataset ID and access token, keep Send events to Meta on.*

**You should see:** your Meta pixel is connected and enabled. Not there yet? Follow [server-side tracking for Shopify in Meta](/docs/tracking/server-side/shopify-meta).

### 2. Set consent

In **Tracking → Configure consent**, choose **Shopify Customer Privacy**, unless your store shows OneTrust, Cookiebot, Usercentrics or Osano instead.

Meta has no consent mode, so without **ad user data** the event isn't sent at all. What each choice lets through: [Consent](/docs/using/consent#what-each-choice-lets-through).

**You should see:** **Tracking → Configure consent** names the banner your store actually shows.

### 3. Send a test event

In **Tracking → Meta Conversions API**, send a test event. It checks the connection only.

**You should see:** Meta accept the test event.

### 4. Check an order

To see the customer information on a real event, place and pay for a test order: it is sent once Shopify marks it paid. Then, in the Shopify app, open **Tracking** in the app menu and select **Run tracking test**.

**You should see:** the checks **Passing**, and **Tracking is live on your store**.



> **Note:** Meta refuses events more than 7 days old, so an order paid more than a week after checkout never reaches Meta.

## Fields sent

| Customer information parameter           | Where it comes from on Shopify                   | Sent as                                                                |
| ---------------------------------------- | ------------------------------------------------ | ---------------------------------------------------------------------- |
| Email, phone                             | The Shopify order                                | `em`, `ph`: hashed; phone as digits with the country code              |
| First name, last name, postcode, country | The Shopify order's address                      | `fn`, `ln`, `zp`, `country`: hashed                                    |
| Customer ID                              | Your Shopify customer ID, when the order has one | `external_id`: hashed                                                  |
| IP address, user agent                   | The visitor's browser                            | `client_ip_address`, `client_user_agent`: not hashed, as Meta requires |
| Browser and click IDs                    | Meta's `_fbp` and `_fbc` cookies                 | `fbp`, `fbc`, with ad storage consent                                  |

Product Metrics only sends what the order already has. It adds no checkout fields and guesses nothing. Sent events aren't revised after a refund.

## Troubleshooting

### Orders are missing in Meta

Check that **Tracking → Configure consent** names the banner your store actually shows ([step 2](#2-set-consent)).

## FAQ

### Does this replace my Meta pixel?

No. You can keep your browser pixel: Meta counts an event once when the pixel and the Meta Conversions API send the same event name and event ID within 48 hours.

### Is my Shopify customer ID sent to Meta?

Yes, hashed as `external_id` when the order has one. Advanced Matching also gets the hashed email, phone, name, postcode and country from the Shopify order.

### What if a visitor declines ad user data on Shopify?

The event isn't sent to Meta at all, because Meta has no consent mode. Product Metrics reads the choice from Shopify Customer Privacy, or from OneTrust, Cookiebot, Usercentrics or Osano if your store shows one.

### Are past orders and refunds sent to Meta?

No. Meta accepts events up to 7 days old, so past orders aren't imported, and later refunds and cancellations don't revise events already sent.

## Where next

* [Shopify](/docs/platforms/shopify): the full platform setup
* [Server-side tracking for Shopify in Meta](/docs/tracking/server-side/shopify-meta): the step before this one
* [Enhanced conversions for Shopify in Google Ads](/docs/tracking/enhanced-conversions/shopify-google-ads): the same customer data, sent to Google Ads
* [Meta](/docs/channels/meta): the channel setup and troubleshooting
* [Customer data on every channel](/docs/features/enhanced-conversions): Enhanced Conversions, the Meta Conversions API and the OpenAI Conversions API on every platform
* On the website: [Full Signal Tracking](https://www.productmetrics.io/server-side-tracking), [first-party cookie](https://www.productmetrics.io/glossary/first-party-cookie), [Product Metrics for Shopify](https://www.productmetrics.io/platforms/shopify)

Developers: do the same with the [CLI](/docs/cli/commands#destinations) or the [API](/docs/api/destinations/test-meta).
