Why it happens
The access token stopped working
The access token stopped working
A token generated by a person who left, or a system user that was removed, fails every request at once. Server events fall to zero on one day.
The integration was disconnected
A store app reinstall, a changed partner account or a gateway whose cloud billing lapsed stops sending without an error you would see.
Meta rejects the payload
An event_time more than 7 days old, a missing action_source, or no customer information at all gets the event refused.
Events carry a test code
A test_event_code left on in production routes every server event to Test events. Overview shows nothing from the server.
The dataset ID changed
The server still posts to an old pixel. Its events arrive somewhere you are not looking.
How to fix it, step by step
Read the Server count
In Events Manager, open Data sources, your dataset, Overview. Note which events show Server and when each was last received.
Read Diagnostics
The Diagnostics tab lists server events Meta received and could not use, with the reason.
Check the integration
Under Settings, Conversions API, confirm the partner integration or gateway is still connected. For a direct setup, generate a new access token and replace the old one.
Read the response
Every Conversions API request gets a response from Meta. A healthy one reports events_received; an error names the field. Meta Payload Helper in the developer docs checks a payload by hand.
Remove the test code
Confirm production requests carry no test_event_code, and post to the dataset ID your ads use.
Steps checked against Meta Business Help Center articles: About the Conversions API; Troubleshoot the Conversions API; About diagnostics in Events Manager. Meta for Developers: Conversions API parameters.
Sprites diagnoses this
Sprites diagnoses it
Sprites reads your pixel and CAPI health and shows where it breaks: which server events went quiet, when, and what Meta says about them.
What Sprites does
- Reads server event counts per event for this week and the week before, and flags any event that went silent.
- Reads when Meta last received anything from the dataset.
- Reads Meta's own diagnostics for the dataset, where refused server events show up.
- Tells apart a dataset the connection cannot read from a dataset that received nothing.
What it doesn't do
- Read your server logs or the responses Meta sent your server
- Send or resend events
- Renew the access token
Questions
Why is my Conversions API not receiving events?
An expired or revoked access token, a disconnected integration, a rejected payload or a test code left on. Check them in that order.
How do I know if CAPI events are reaching Meta?
In Events Manager, Overview shows Server next to each event that arrives from the Conversions API, with the last time it was received.
Why do CAPI events show in Test events only?
They are sent with a test_event_code. Remove it from production requests.
How old can a Conversions API event be?
Web events must reach Meta within 7 days of when they happened. Older events are rejected.
Do my ads stop if CAPI stops?
No. They keep spending on whatever the browser pixel still reports, which is usually less.
See where it breaks
Connect your accounts. Sprites reads them side by side and shows you exactly where the numbers split.