Meta Conversions API isn't receiving expected events?
First prove whether your server sends anything at all, then whether Meta accepts it. Most Conversions API gaps come from a wrong dataset ID or access token, required fields missing, events older than Meta accepts, or an integration that was never switched on for the events you expect.
Symptom
Events Manager shows browser events but few or no server events. Or server events arrive for PageView but not for Purchase. Or your integration says it is connected, yet the event counts don't move.
The direct answer: send one known test event with Meta's test_event_code, watch Test events, and read the response your server gets back. That separates "never sent" from "sent and rejected" from "accepted but not where you are looking".
Possible causes
- Wrong dataset or access token. Events go to a different pixel or dataset ID, or the token was revoked, expired or lacks permission.
- Missing required fields. Meta's server event parameters page marks
event_name,event_time,user_dataandaction_sourceas required, and saysevent_source_urlis required for website events. - Events too old. Meta's guide says
event_timecan be up to 7 days before you send. If any event in a request is older, the whole request is rejected and no events in it are processed. - The integration doesn't cover that event. A platform app may only send server events at a certain data-sharing level, or only for some event types.
- A test code left in place. Meta's guide says to remove
test_event_codewhen you send production events. - Consent or filtering upstream. A server container or app may drop events for visitors without marketing consent. That can be correct, but it should be deliberate.
How to check
- Confirm the IDs. Write down the dataset (pixel) ID in Events Manager and compare it with the one in your integration, server container or app settings.
- Send a test event. In Events Manager, open the dataset, go to Test events and copy the test code. Send one event with it from your integration. Meta documents the endpoint as a POST to
/{PIXEL_ID}/eventsongraph.facebook.com. - Read the response. Your server, server container or integration log should record Meta's reply. An error message there usually names the problem: token, parameter or timestamp.
- Check the payload fields. Compare a logged payload with the required list above, and check
event_timeis in Unix seconds, not milliseconds. - Check diagnostics. In Events Manager, review the dataset's diagnostics and the overview for server events. Look for warnings about parameters or deduplication.
- Check the app settings. On Shopify, open the Facebook & Instagram app and check the customer data-sharing setting. Shopify's help describes which level uses the Conversions API.
Illustrative server event, with invented values and a placeholder for the hashed email:
{
"data": [{
"event_name": "Purchase",
"event_time": 1794916800,
"event_id": "1001",
"action_source": "website",
"event_source_url": "https://example.co.uk/checkout",
"user_data": { "em": ["<sha256 hash>"] },
"custom_data": { "value": 42.50, "currency": "GBP" }
}]
}
What the result means
- Nothing in your logs: your server never sent it. The fault is in the trigger, the app setting or the server container.
- An error response: Meta rejected the request. Fix the field, token or timestamp the error points to.
- Accepted, visible in Test events, missing in the overview: check whether the test code is still in production requests, and that you are viewing the right dataset.
- Accepted for some events only: your integration may not cover the others.
A limitation: server events are not a perfect copy of every order. Consent choices, missing customer data and integration rules mean some orders may legitimately not be sent. Compare against orders where you expect an event, not against every order.
How to fix it
- Correct the dataset ID and generate a new access token through Meta's documented route if the old one fails.
- Add the missing required fields. For website events include
event_source_urlandaction_source: "website". - Send events promptly. Meta recommends sending within an hour, and rejects requests containing events older than 7 days.
- Remove
test_event_codefrom production. - Add a shared
event_idfor every event that is also sent by the browser. Without it you will swap missing events for duplicate purchases. - Hash customer data the way Meta's parameters documentation describes before you send it.
Get a specialist when the server path runs through a server-side tag container, a custom backend or several apps at once. These setups need someone to read the logs and the payloads together.
What not to do
- Don't send historic orders in bulk to "fill the gap". Events older than 7 days make the whole request fail.
- Don't send unhashed personal data, or more customer data than you need.
- Don't leave both a platform app and a custom integration sending the same events without a deduplication plan.
When to request help
Our Google Ads and Meta conversions service checks the browser and server paths together, with test events and a test order as evidence. If you are unsure the problem is Meta at all, request a free check first.
Related guides: Meta duplicate purchases, Meta Pixel not firing, Consent Mode v2 checks and the Shopify tracking checklist.
Sources and updated date
- Meta for Developers: Get started with the Conversions API
- Meta for Developers: Using the Conversions API
- Meta for Developers: Server event parameters
- Meta for Developers: Conversions API parameters
- Meta for Developers: Handling duplicate Pixel and Conversions API events
Last checked against official documentation: 18 November 2026. Events Manager screens change often, so if a label differs from what you see, follow Meta's current help.
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.