Why this happens
Events Manager and Ads Manager answer two different questions. Events Manager asks whether Meta received a well-formed event and matched it to a known or probable person. Ads Manager asks whether that person previously saw or clicked an ad from this specific ad account, inside the attribution window configured on the ad set, for the event the ad set is actually optimizing for.
An event can pass the first test and fail the second for reasons that have nothing to do with delivery: the ad set optimizes for a differently-named event than the one CAPI is sending, the Pixel or dataset the CAPI call targets is not the same asset the live ad set references, the attribution window has already lapsed by the time the server event arrives, or the Event Match Quality is too low to link the server event back to a specific ad exposure at all.
Fix it
- Confirm the ad set's optimization or conversion event, under Ads Manager > ad set > Conversion location/event, exactly matches the
event_nameyour CAPI call sends. - Confirm the Pixel or dataset ID your server-side call targets is the same one the ad account and ad set are actually configured against - a second Pixel from a duplicate implementation, a dev environment, or an agency handoff never gets referenced by the live ad set.
- Check the attribution window setting on the ad set against how long after ad exposure the CAPI event typically arrives - a long checkout or lead-nurture cycle can legitimately outlast a short window.
- Improve Event Match Quality by sending as many of email, phone, external_id, fbc, and fbp as you legitimately have, hashed per Meta's spec - a low score directly reduces how often a server event links back to an ad exposure.
- If multiple ad accounts share a Business Manager or a Pixel across properties, check whether attribution is being claimed elsewhere by a different campaign targeting the same person.
How to verify it worked
- In Events Manager, check the Event Match Quality score for the event over the period in question - a persistently low score (rated Fair or Poor on Meta's own diagnostics panel) explains attribution loss even when event volume looks healthy.
- In Ads Manager, add the Results and Cost per Result columns for the exact configured event, then cross-check the count against Events Manager's event count for the same date range and Pixel - a large gap with healthy match quality points to an attribution-window or optimization-event mismatch, not a delivery failure.
- Where available, use Meta's Attribution tool to trace one known conversion back through its touchpoints, confirming whether it was even eligible to attribute to any ad exposure.