Skip to content
Meta

Shopify Meta Conversions API Advanced Matching

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 in Product Metrics (editor is enough for the store and destination steps).
  • Server-side tracking for Shopify in Meta set up first.
  • Your Shopify store connected: a Shopify login that can install apps and edit the theme, the Product Metrics app installed with its app embed on, the store linked to your property, and your subscription started in the app with Create subscription (billed through Shopify). See Shopify.

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

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.

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.

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

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 →

Paste the prompt into your assistant.

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

Fields sent

Customer information parameterWhere it comes from on ShopifySent as
Email, phoneThe Shopify orderem, ph: hashed; phone as digits with the country code
First name, last name, postcode, countryThe Shopify order’s addressfn, ln, zp, country: hashed
Customer IDYour Shopify customer ID, when the order has oneexternal_id: hashed
IP address, user agentThe visitor’s browserclient_ip_address, client_user_agent: not hashed, as Meta requires
Browser and click IDsMeta’s _fbp and _fbc cookiesfbp, 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

ProblemFix
Orders are missing in MetaCheck that Tracking → Configure consent names the banner your store actually shows (step 2).

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

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

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