Skip to content
Connect your channels

Meta Conversions API and Advanced Matching

Send purchases to your Meta pixel through the Meta Conversions API with Advanced Matching, with revenue, profit, new and returning customer and lifetime value events you can bid on.

Product Metrics confirms each purchase from your store’s order data and sends it from its server to your Meta pixel through the Meta Conversions API. Meta receives AddToCart, InitiateCheckout and Purchase, plus one custom event per value (revenue, profit, new and returning customer, lifetime value). Each event carries hashed customer data for Advanced Matching: see Customer data.

This is server-side tracking (Full Signal Tracking), included in Pro. Unlike Google Ads, you create the custom conversions yourself, and there are no customer lists.

You need

Your pixel ID and a Conversions API access token from Events Manager.

In the app

Tracking → Meta Conversions API → Connect Meta

What is sent

Purchases plus one custom event per value, with Advanced Matching.

Prerequisites

In the app

1. Get your pixel ID and access token

In Meta Events Manager:

  1. Open the pixel your ads use and copy the number under its name: your Pixel or Dataset ID.
  2. Open the pixel’s Settings and choose Generate access token under Conversions API. Copy the token.
  3. Optional: copy a code from Test events, to send test events while you set up.

The access token is a credential. Product Metrics never shows it again after you save it; it keeps only the last characters as a hint.

2. Add the Meta destination

Go to Tracking → Meta Conversions API → Connect Meta. Fill in Pixel or Dataset ID, Access token and, optionally, Test event code. Leave Send events to Meta on and select Add destination.

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.

Keep the access token out of shared chats. Enter it in the app. An assistant must ask you for it, and never invents, reuses or repeats it.

You should see: Meta destination saved.

3. Place a test order

With a test event code saved, place a test order on your store.

You should see: the events under Test events in Events Manager. A test event checks the connection only.

4. Create custom conversions in Meta

An event appears in Meta’s selector only after Meta receives it, so do this after the test order. In Events Manager:

  1. Custom conversions → Create custom conversion.
  2. Select your pixel and the event, and add the rule pm_purpose equals the purpose.
  3. Choose Purchase as the category. Use the event’s value and currency, and leave the fixed value unset.

The full table is on Conversion actions. Profit events don’t appear while your margin data is incomplete.

You should see: one custom conversion per event you want to bid on.

5. Remove the test event code

While a test event code is saved, events go to Test events and don’t count in reporting. Once your test order has arrived, clear Test event code in the Meta destination and save.

The token stays saved when the pixel doesn’t change. To pause sending and keep the settings, turn Send events to Meta off.

6. Check delivery

Open Tracking → Meta Conversions API.

You should see: the destination Active, Access token saved, Sending on, and events counted as Delivered, Pending, Retrying or Failed. If it shows an error, see Troubleshooting.

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.

Send my store's purchases to my Meta pixel with Product Metrics. Check my setup status first, walk me through each open step, and ask me to enter the access token in the Product Metrics app rather than in this chat.
Send my store's purchases to my Meta pixel with Product Metrics. Check my setup status first, walk me through each open step, and ask me to enter the access token in the Product Metrics app rather than in this chat.
Send my store's purchases to my Meta pixel with Product Metrics and check that Meta accepts them; read the access token from the META_ACCESS_TOKEN environment variable and never print it. 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).
Send my store's purchases to my Meta pixel with Product Metrics and check that Meta accepts them; read the access token from the META_ACCESS_TOKEN environment variable and never print it. 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).

What Product Metrics sends to Meta

Sent to Meta
Standard eventsAddToCart, InitiateCheckout and Purchase. The Purchase value is order revenue: products and shipping, minus refunds. Each Purchase lists the products bought
Custom eventsOne per value: PMOrderRevenue, PMOrderProfit, new and returning customer, and LTV. The full list with each pm_purpose is on Conversion actions
ProfitNeeds a complete contribution margin: add your costs. Meta accepts no negative value, so a loss-making order is sent with value 0, and its real profit goes along as a separate parameter
LTVNeeds a linked customer and sends only what this order adds, with the observed total alongside when available. Observed, not predicted
Customer data (Meta Conversions API)With consent to marketing, each event carries the hashed email, name, postal code and country, plus IP address and browser, so Meta can match it to a person. Meta’s browser IDs go only when the shopper also allowed ad storage
ConsentFrom the banner under Tracking → Configure consent, the same setting Google Ads uses (Consent)
LimitsMeta accepts events up to 7 days old, so past orders aren’t imported. Later refunds and cancellations don’t revise Meta events

Running the Meta Pixel as well

Keep your browser pixel if you like. Meta counts an event once when the pixel and the Conversions API send the same event name and event ID within 48 hours.

  • Purchase uses the order transaction ID, so it works on its own.
  • AddToCart and InitiateCheckout need your developer to pass the event ID Product Metrics returns to the pixel call.

Your store platform

The Meta steps are the same on every platform. Connect your store first with its platform guide.

Troubleshooting

ProblemFix
“Access token is invalid or expired”Generate a new token in Events Manager and save it (step 2).
“The access token has no access to this pixel”Generate the token from the same pixel.
“No access token is saved for this pixel”Add a token. A changed Pixel or Dataset ID needs a new token too.
“The shopper did not consent to marketing, so the event was not sent”Expected for shoppers who declined. If it shows for every event, check that consent names your banner.
“The event was more than 7 days old”Orders marked paid more than a week after checkout can’t go to Meta.
“The pixel changed after this event was queued”Events waiting during the change weren’t sent to the new pixel; new events go there.
“The custom conversion for this event is not set up correctly”The event name and pm_purpose rule must match the table on Conversion actions.
A profit event doesn’t show up in Meta’s selectorProfit events need a complete margin. Add your costs, then place another test order.
Events show under Test events but not in reportingA test event code is still saved: clear it (step 5).

Meta rate limits and timeouts are retried on their own. To stop for good, delete the destination. That removes the stored token, so setting up again needs a new one.

FAQ

Does this replace my Meta pixel?

No. Product Metrics sends events to your Meta pixel through the Meta Conversions API, and you can keep the browser pixel. Meta counts an event once when both send the same event name and event ID within 48 hours; Purchase uses the order transaction ID, so it needs no extra step.

Is this Meta Advanced Matching?

Yes. With marketing consent, each Meta Conversions API event carries the hashed email, name, postal code and country, plus IP address and browser, for Advanced Matching.

Are past orders sent to Meta?

No. Meta accepts events up to 7 days old, so Product Metrics sends orders from the moment tracking is live.

Can I bid on profit in Meta?

Yes. Create a custom conversion on the PMOrderProfit event in Events Manager and optimise your campaign on it. It is sent once the order has a complete contribution margin; a loss-making order goes with value 0.

Where next

On the website: Full Signal Tracking, ad blocker conversion tracking check, pricing

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