Table of Contents
Toggleaction_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.
The button opens the debugger with this exact error already decoded. Everything runs in your browser.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, ViewContentOrderCreated, OrderShipped, OrderDelivered, OrderCanceled, OrderReturnedCartAbandoned, QualifiedLead, RatingProvided, ReviewProvidedLead, Schedule, CompleteRegistration and Contact work for the web pixel but are not on the chat list.LeadQualified and AppointmentBooked. The current list has QualifiedLead instead.purchase and leadsubmitted do not match Purchase and LeadSubmitted as Meta lists them.
{
"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.event_name exactly as it left your server.event_name that is not on the list before it is sent.| If you were sending | Send this instead |
|---|---|
Lead | LeadSubmitted |
LeadQualified | QualifiedLead |
Schedule or AppointmentBooked | No direct match. Use QualifiedLead for a booked or converted lead, or Purchase if money changed hands. |
CompleteRegistration or Subscribe | There is no chat version. Use Purchase for a paid signup, or send it through website or app CAPI instead. |
Cancel | OrderCanceled |
| Order placed | OrderCreated |
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.