Conversions API Not Working? A Fix-It Checklist for SMEs

2. What “Conversions API Not Working” Actually Means

Quick Answer: “Not working” means your server isn’t sending usable events to Meta — either the connection never fires, it fires but Meta rejects the payload, or it fires but doubles up with the pixel because deduplication is off. These are three different faults with three different fixes, so name yours first.

People say “my Conversions API isn’t working” for three very different problems, and treating them as one is why so many fixes fail. Before you change anything, work out which state you’re in:

• Not connected at all. No server events reach Meta — the integration was never finished, the access token is dead, or the endpoint is wrong.
• Connected but rejected. Events send, but Meta throws them out — a wrong dataset ID, missing required parameters, or a hashing mistake means the data arrives and gets discarded.
• Connected but doubling. Both the pixel and the server send the same event with no shared event ID, so one purchase counts as two.

The Conversions API is Meta’s server-side feed, built to back up the browser pixel when iOS limits, ad blockers, and cookie restrictions eat the signal. So it usually breaks alongside the pixel, not instead of it. If your Meta Pixel isn’t firing either, you’re flying blind on both layers and the fix has to cover both.

3. How to Check If Your Conversions API Is Working

Quick Answer: Check three things in Events Manager before touching any code — the data source’s server activity, the Event Match Quality score, and Test Events with live traffic. Together they tell you in minutes whether the server connection fires, whether Meta accepts the events, and where the break sits.

Diagnosis takes about five minutes and stops you fixing the wrong thing. Run these checks in this order:

• Data source overview. In Events Manager, open your dataset and look at the server processing column — a healthy CAPI shows recent server events beside the browser ones.
• Test Events. Open Test Events, send a live action or a test payload, and watch whether the server event lands in real time.
• Event Match Quality. Read the EMQ score on your key events; a low or falling score means Meta receives events but can’t match them to users.
• Deduplication status. Check whether Meta flags your events as deduplicated — if not, the pixel and server are double-counting.

This is the same diagnose-before-you-fix habit our Meta Ads team runs at the start of every account audit. The panel that shows the problem usually points straight at the fix.

4. Why the Conversions API Stops Working

Quick Answer: Most Conversions API setups stop working after an access token expires, a dataset ID is entered wrong, or required event parameters go missing. Deduplication gaps, unverified domains, and payload errors make up the rest. A single expired token is behind more cases than any Meta-side glitch.

CAPI rarely dies on its own. A token expired, an ID changed, a developer shipped an update. The table below shows how the not-working cases we handle break down by root cause.

Notice the pattern — the top causes are all setup and maintenance issues on your side, not Meta outages. That’s the same account-hygiene theme behind a single Facebook ad getting rejected: small, avoidable, and usually reversible once you spot it.

5. The Fixes, in the Right Order

Quick Answer: Work top to bottom, fixing one thing at a time and re-testing after each — confirm the fault, refresh the access token, verify the dataset ID, fix event parameters, set up deduplication, then verify your domain. Changing three things at once means you never learn which one was broken.

Fixing in order matters, because changing several things at once means you never learn which one was broken. Follow this sequence:

1. Confirm the fault in Test Events. Note the exact error or the missing event before you change anything, so you know what “fixed” looks like.
2. Refresh the access token. Regenerate the system-user token in Business Settings and update it wherever your integration stores it — expired tokens are the single most common cause.
3. Verify the dataset ID. Make sure the dataset (pixel) ID in your server code matches the one in Events Manager, and that events hit the right endpoint.
4. Fix the event parameters. Send the customer parameters Meta needs — hashed email and phone, plus the fbc and fbp cookies — and confirm they’re hashed with SHA-256, not sent in plain text.
5. Set up deduplication. Give the pixel and server events a shared event_id and matching event name, so Meta merges the pair instead of counting both.
6. Verify your domain and re-test. Confirm your domain in Business settings, then re-run Test Events to watch clean, deduplicated events land.

If the payload itself is being rejected, Meta’s own Conversions API troubleshooting guide lists the exact error codes and what each one means. Our Meta Ads team never bundles changes, because bundling hides which repair actually worked.

6. How Long Until Your Server Events Come Back

Quick Answer: Once the fix is live, most server events reappear within minutes to a day. A refreshed token or corrected dataset ID is near-instant; deduplication and domain verification can take a couple of days to settle before your reports read normally again.

Events usually show in Test Events straight away, but full reporting and attribution lag a little behind. The table shows the median time we see per cause, once the fix is in.

Give a corrected setup a few days before you judge the numbers. Chasing Meta support on day one — the way panic sets in when a Facebook Page gets unpublished — usually just adds stress without speeding anything up.

7. Event Match Quality: The Number That Decides Everything

Quick Answer: Event Match Quality measures how well Meta can match your server events to real people. A CAPI that fires but sends thin data scores low and optimises badly. Adding hashed email, phone, and the fbc and fbp cookies lifts the score fast, and Meta flags anything on the low end.

A connected Conversions API is not the same as a useful one. If you only send page data, Meta receives the event but can’t match it to a person, so your ads optimise on guesswork. The table shows how the match score climbs as you add customer parameters.

Email and phone carry the most weight because they’re unique identifiers Meta can match reliably. This is also why a healthy pixel matters — the Meta Pixel supplies the fbc and fbp cookies the server event leans on for matching.

8. Deduplication: The Mistake That Doubles Your Numbers

Quick Answer: When the pixel and the Conversions API both send the same event without a shared event ID, Meta counts one purchase twice. Your reports look great, your real cost per result climbs, and delivery optimises toward inflated numbers. Deduplication — a matching event_id on both — is the fix SMEs miss most.

This is the trap of a CAPI that looks like it’s working. The numbers go up, so nobody checks. The table shows what happens to reported conversions across three common setups.

Over-reporting is worse than under-reporting, because it hides waste behind good-looking numbers — the same way a broken ad spending limit can quietly drain budget before anyone notices. Deduplication keeps the pixel and server as one clean signal, not two competing ones.

9. How to Keep Your Conversions API Healthy

Quick Answer: Prevention is mostly maintenance — use a long-lived system-user token, re-test after every website or server change, watch Event Match Quality weekly, and keep deduplication in place. These few habits stop most repeat breaks before they cost you a lead.

Getting the feed back is a relief; keeping it working is the real win. A few standing habits keep the accounts we manage out of trouble:

• Use a system-user token. A system-user access token from Business Settings lasts far longer than a personal one, so it won’t expire mid-campaign.
• Re-test after every change. Any theme update, checkout change, or server deploy gets a quick Test Events check before it goes live.
• Watch EMQ and dedup weekly. A quick look catches a falling match score or broken deduplication early, the way testing early stops a small issue snowballing like a Facebook ad that stops delivering.
• Limit who can edit. Keep server, tag, and dataset access to a couple of trained people — most breaks start with a well-meaning change.

10. Conclusion

A Conversions API that isn’t working looks alarming, but it’s usually a small, findable fault. Name the state, confirm it in Events Manager, fix one cause at a time, then give the data a few days to settle. Get deduplication and Event Match Quality right so the feed you fixed actually earns its keep — that calm, ordered path beats guessing every time.

If your server events are dark and your campaigns are optimising on air, or you’d rather not gamble ad budget on trial and error, you don’t have to sort it alone. The team at ZenWeb runs tracking-tight Meta Ads campaigns for Malaysian businesses every day, and fixing broken Conversions API setups the right way is part of the job.

11. Frequently Asked Questions

1. How do I know if my Conversions API is working?

Open Events Manager, select your dataset, and check the server processing column — a working CAPI shows recent server events beside the browser ones. For a live check, use Test Events and send a real action; the server event should land in real time. If nothing appears, the connection isn’t working.

2. Why did my Conversions API suddenly stop working?

The most common cause is an expired access token, especially a personal token rather than a system-user one. Wrong dataset IDs, missing event parameters, and server updates that changed the payload cause most of the rest. Check when the events went quiet and what changed on your server around that time.

3. What is a good Event Match Quality score?

Meta scores Event Match Quality up to 10, and higher is better. A score on the low end means Meta can’t match your events to users well, so delivery optimises poorly. Sending hashed email, phone, and the fbc and fbp cookies is the fastest way to lift the score.

4. Do I still need the Meta Pixel if I have the Conversions API?

Yes — they work best together, with deduplication set up. The pixel captures browser behaviour in real time and supplies the fbc and fbp cookies; the Conversions API sends events server-side to fill the gaps the browser misses. Running both with a shared event_id gives the most complete, resilient tracking.

5. Will I lose data while my Conversions API was down?

The server events missed while it was down can’t be recovered — Meta only records what it receives. But nothing captured before the break is lost, and once you fix the cause, new events resume normally. The browser pixel also keeps recording throughout, which is exactly why running both layers matters.