Meta CAPI Events Not Showing in Events Manager: A Troubleshooting Guide
When CAPI events are not showing in Events Manager, the server event is not reaching Meta or is not being associated with your dataset. The break is somewhere in the server-side flow, which has more steps than a browser tag. Trace the flow from the business event to Meta to find where the server event stops.
Table of Contents
- 01.The server event flow
- 02.What to check first
- 03.Is the server event being generated
- 04.Authentication and the endpoint
- 05.Required fields and the payload
- 06.The server response
- 07.How to test it
The server event flow
A CAPI event follows a longer path than a browser event. A business event happens, your server generates an event, the server sends a CAPI request to Meta, Meta receives and processes it and the event appears in Events Manager. Each step can fail silently, and the failure gives you no visible error in the browser.
| Step | What happens | What can fail |
|---|---|---|
| 1. Business event | Order or lead occurs | Event never triggers server logic |
| 2. Server generates event | Server builds the payload | Missing required fields |
| 3. CAPI request sent | Server calls Meta endpoint | Auth failure, wrong endpoint |
| 4. Meta receives | Meta processes the request | Payload rejected, no response |
| 5. Events Manager | Event appears in dataset | Wrong dataset, delay |
What to check first
- Confirm the business event actually triggers your server-side logic.
- Check the server response from the CAPI request for errors.
- Confirm the access token or authentication is valid.
- Confirm the event is sent to the correct dataset or Pixel connection.
- Confirm required fields like event name and event time are present.
Is the server event being generated
Before anything reaches Meta, your server has to generate the event. If the business event, like an order completion, does not trigger the server logic that builds the CAPI payload, nothing is sent. Confirm the trigger for your server event fires. This is often a webhook from your ecommerce platform or a server-side function called after an order. If the webhook does not fire or the function is not called, no event is generated.
Authentication and the endpoint
CAPI requests need valid authentication, usually an access token, and must go to the correct endpoint for your dataset. An expired or wrong token causes the request to be rejected. A wrong dataset ID sends the event to the wrong place or nowhere. Check the server response for auth errors and confirm the token and dataset ID are correct and current.
Required fields and the payload
A CAPI request needs certain fields to be accepted. The event name and event time are required, and user data is needed for matching. If required fields are missing or malformed, Meta may reject the event or accept it without being able to match it. Inspect the payload your server builds and confirm the required fields are present and correctly formatted.
The server response
Unlike a browser tag, a CAPI request gives you a server response you can inspect. The response tells you whether Meta accepted the event and can flag issues with the payload. Log the response from your CAPI requests and check for errors. A request that returns an error is not reaching Meta successfully, regardless of what your server logic assumes.
How to test it
- 1.Trigger the business event that should generate a server event.
- 2.Confirm your server logic runs and builds a payload.
- 3.Log the CAPI request and the response from Meta.
- 4.Check the response for success or error codes.
- 5.Confirm the event appears in Test Events for the correct dataset.
Frequently Asked Questions
Why are my CAPI events not showing even though the request is sent?
The request may be rejected due to auth, a wrong dataset or missing required fields. Inspect the server response from the CAPI request, which tells you whether Meta accepted the event and flags payload problems.
How is debugging CAPI different from debugging the Pixel?
The Pixel gives you browser signals. CAPI gives you a server response you can log and inspect. You debug CAPI on the server side by checking the request payload and the response, not in the browser.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Meta CAPI Purchase Events Missing: How to Trace the Server-Side Event Flow
A missing CAPI Purchase is a server-side flow problem. Confirm the order triggers the server logic, confirm the payload carries the order data and check the CAPI response.
Meta CAPI User Data Missing: How It Can Affect Event Matching
Missing user data you are permitted to collect is a fixable gap. Send the data you lawfully can, correctly formatted. Never send data without appropriate consent or fabricate unavailable data.
Meta Browser Events and Server Events Do Not Match: How to Audit the Difference
Browser and server counts will not always be identical because the paths face different restrictions. Find unexpected differences, confirm event names and deduplication, then investigate.