Facebook CAPI conversion event log
Review conversion-event history and delivery status.
Controls depend on your account and permissions.
Open and prepare
- Facebook Conversions API → View all conversion events
- Access to the Conversions API area is required.
Read the log
- Review ID, Time, Source, Contact, Deal, Event, Mode, Eligibility, Status, Attempts and Last error. The log has no status, date or other filter controls; rows are newest first. The first batch loads automatically; use Load 100 more when available to inspect additional rows. The loaded count indicates whether more are available. This log has no per-event retry control. CAPI control center and Diagnostics links return to those related views.
- Compare a failed or ineligible event with the dataset, consent rule, mapping and validation status on the CAPI control center. If loading fails, read the error and refresh the page; expired requests require a refresh. Event records can include customer information; share screenshots only after sanitizing them.
Event and delivery meanings
| Value | Meaning and next check |
|---|---|
| Mode: DISABLED, TEST, LIVE | Mode is the snapshot taken at capture. TEST delivery requires a configured test-event reference; the worker only claims events matching the current mode and dataset. A later mode change does not convert an earlier event. |
| CAPTURED / REPORT_ONLY | The event was stored but did not meet the conditions for queuing, such as enabled delivery and matching mode/dataset. It is not evidence of a send. |
| INELIGIBLE | Stored but not queued. Eligibility gives the reason, such as CONSENT_REQUIRED, OUTSIDE_META_EVENT_WINDOW, WHATSAPP_DATASET_NOT_CONNECTED or a payload validation error. |
| QUEUED | Eligible and waiting for a due worker claim; it has not yet established acceptance. |
| PROCESSING | A worker has claimed and locked the event. Attempts increments at claim, before an outcome is recorded. |
| RETRY | A transient failure was recorded and a later attempt is scheduled with backoff. Repeated failure can become PERMANENT_FAILURE at the worker’s attempt limit. |
| ACCEPTED | Meta returned a successful response with the expected received-event count. This indicates provider acceptance, not a guarantee of later attribution or reporting. |
| PERMANENT_FAILURE | The worker recorded a non-transient failure or exhausted its attempts. Read Last error and address the underlying configuration or data issue. |
| UNKNOWN | Provider outcome is ambiguous, including a network failure with no HTTP response or an unclear accepted count. Automatic retry is disabled; reconcile with the provider and diagnostics before any supported recovery. |
Eligibility examples include missing website source URL or user agent, invalid click identifiers, unsupported business-messaging signal, missing matching key, and missing WhatsApp Purchase value or currency. Last error is the sanitized most recent delivery error; Attempts counts claims, not necessarily confirmed provider receipts. A source action may produce no log row if capture is off, the mapping is disabled or no valid Facebook attribution is found. Review consent and capture conditions before diagnosing a missing row.