Meta CAPI Error 2804066: 5 Proven Fixes

Meta CAPI error 2804066 means Meta rejected the event name you sent with a chat event. Events sent with action_source set to business_messaging only accept a fixed list of 14 event names, and website names such as Lead are not on it.This guide is for developers, marketers and agencies who send WhatsApp, Messenger or Instagram events to Meta through the Conversions API. Below you will find what the error means, five common causes, a wrong and a fixed payload, and the fix steps.
Check this example in the debugger
The button opens the debugger with this exact error already decoded. Everything runs in your browser.

What error 2804066 means

Chat events have their own list of event names. When the event_name in your request is not on that list, the request fails. In a thread on Meta’s developer community, a developer reported an HTTP 400 with error code 100 and subcode 2804066 after sending LeadQualified. The error title was “Invalid event type for messaging event.”Meta’s business messaging guide lists these 14 supported event names:
  • Purchase, LeadSubmitted, InitiateCheckout, AddToCart, ViewContent
  • OrderCreated, OrderShipped, OrderDelivered, OrderCanceled, OrderReturned
  • CartAbandoned, QualifiedLead, RatingProvided, ReviewProvided
Copy each name exactly as written, including the capital letters. The same guide says messaging events should only represent customer interactions that happen in the messaging thread.Source: Meta, Conversions API for Business Messaging. Error report: Meta developer community thread.

5 common causes of this error

  1. A website event name reused for chats. Names such as Lead, Schedule, CompleteRegistration and Contact work for the web pixel but are not on the chat list.
  2. Older or wrong names copied from guides. Blog posts and BSP guides still show names such as LeadQualified and AppointmentBooked. The current list has QualifiedLead instead.
  3. The wrong letter case. purchase and leadsubmitted do not match Purchase and LeadSubmitted as Meta lists them.
  4. A custom event name. The chat list has 14 names, and a custom name is not one of them.
  5. A website CAPI template reused for chats. The template was copied for WhatsApp, Messenger or Instagram events, but the event names were never changed.
Meta CAPI error 2804066 invalid event name in a WhatsApp chat event

Wrong payload vs fixed payload

Here is a WhatsApp chat event that triggers the error. Everything else is in place, so the event name is the only fault:
{
  "data": [
    {
      "event_name": "Lead",
      "event_time": 1761570000,
      "event_id": "lead_58213",
      "action_source": "business_messaging",
      "messaging_channel": "whatsapp",
      "user_data": {
        "whatsapp_business_account_id": "123456789012345",
        "ctwa_clid": "ARAExampleClickId0123456789"
      }
    }
  ]
}
And the fixed version, with "Lead" replaced by "LeadSubmitted":
{
  "data": [
    {
      "event_name": "LeadSubmitted",
      "event_time": 1761570000,
      "event_id": "lead_58213",
      "action_source": "business_messaging",
      "messaging_channel": "whatsapp",
      "user_data": {
        "whatsapp_business_account_id": "123456789012345",
        "ctwa_clid": "ARAExampleClickId0123456789"
      }
    }
  ]
}
All IDs above are made up. Replace them with your own WhatsApp Business Account ID and the real ctwa_clid from the chat. The event_time is a Unix timestamp in seconds.

The 5 fixes, step by step

  1. Log the full request body that failed and read its event_name exactly as it left your server.
  2. Compare that name with the 14 supported names above and copy the right one exactly, with the same capital letters.
  3. Rename the event using the table below.
  4. Fix the source, not just one request. Change the name in your website CAPI template, BSP workflow or automation so every chat event uses a supported name. Drop custom names or map them to a supported one.
  5. Add a small check in your code that rejects any event_name that is not on the list before it is sent.
If you were sendingSend this instead
LeadLeadSubmitted
LeadQualifiedQualifiedLead
Schedule or AppointmentBookedNo direct match. Use QualifiedLead for a booked or converted lead, or Purchase if money changed hands.
CompleteRegistration or SubscribeThere is no chat version. Use Purchase for a paid signup, or send it through website or app CAPI instead.
CancelOrderCanceled
Order placedOrderCreated
This mapping is a practical suggestion, not an official Meta table.

How to confirm Meta CAPI error 2804066 is fixed

Send one corrected event with a test_event_code. Meta describes it as a code for checking that your server events are received correctly, and it sits at the top level of the request, next to data:
{
  "test_event_code": "TEST12345",
  "data": [ ...your corrected event... ]
}
Then look for the event in the Test Events tab in Events Manager. Meta says to remove the code from your production payload. Meta’s pages on testing do not say whether chat events show up in Test Events, so if nothing appears, rely on the API response: the request should no longer return the error. You can also paste the payload into the debugger and check that the finding is gone.

Check your own payload

Paste your payload into the CAPI debugger and it will tell you whether the event name is accepted for chat events, and flag other problems in the same event. You can start from the example first:
Check this example in the debugger
For more fixes like this one, go back to the debug hub.

Frequently asked questions

What does Meta CAPI error 2804066 mean?

The event name in your request is not accepted for chat events. Events sent with action_source business_messaging only accept the 14 event names Meta lists for business messaging.

Which event names are supported for chat events?

Purchase, LeadSubmitted, InitiateCheckout, AddToCart, ViewContent, OrderCreated, OrderShipped, OrderDelivered, OrderCanceled, OrderReturned, CartAbandoned, QualifiedLead, RatingProvided and ReviewProvided.

Can I send Lead or Schedule for WhatsApp events?

No. Those are website names and are not on the chat list. Use LeadSubmitted instead of Lead. Schedule has no direct match, so use QualifiedLead for a booked lead or Purchase if money changed hands.

Are event names case sensitive?

Meta lists each name with a specific capitalization, such as LeadSubmitted, so copy it exactly. Meta’s guide does not say how strictly case is checked, so do not rely on a different case being accepted.

What if the conversion happened on my website or in my app, not in the chat?

Send it through website or app Conversions API instead. Meta’s guide says messaging events should only represent customer interactions that happen in the messaging thread.

Will fixing the event name fix all my chat events?

Not always. A chat event also needs the right messaging_channel, your WhatsApp Business Account ID and, for WhatsApp, the ctwa_clid from the chat. Meta’s guide says to send ctwa_clid whenever you have it.Built by Al-Fahad Hridoy, an Attribution & Tracking Consultant who fixes Meta Conversions API, WhatsApp click-to-chat, AppsFlyer and Firebase tracking for apps and websites.