Table of Contents
ToggleShort answer: a chat conversion from a Click to WhatsApp, Messenger or Instagram ad should carry the business_messaging action_source. If your payload says website, app, chat, other or system_generated instead, the event describes a different kind of conversion. The fix is one line: set "action_source": "business_messaging" and add messaging_channel with whatsapp, messenger or instagram.
This guide is for developers, marketers and agencies who send chat conversions to Meta’s Conversions API and find the wrong action_source in their payload. Below you will find what the business_messaging action_source means, a wrong and a fixed payload, five causes with a fix and a check for each, how to confirm the fix, and a short FAQ.
The button opens the CAPI Debugger with a WhatsApp event that wrongly uses action_source “website”. The check runs in your browser and nothing is uploaded.
Meta’s server event parameters page lists nine action_source values and says this field lets you specify where your conversions occurred. The values that get mixed up with chat conversions are these:
| Value | Meta’s description |
|---|---|
business_messaging | Conversion was made from ads that click to Messenger, Instagram or WhatsApp. |
chat | Conversion was made via a messaging app, SMS, or online messaging feature. |
website | Conversion was made on your website. |
app | Conversion was made on your mobile app. |
other | Conversion happened in a way that is not listed. |
The same page says that by using the Conversions API, you agree that the action_source parameter is accurate to the best of your knowledge. So the value is not a label you pick freely: it has to describe where the conversion really happened.
Meta’s Conversions API for Business Messaging guide uses the business_messaging action_source together with messaging_channel in all three of its samples: whatsapp, messenger and instagram. The guide also says messaging events should only represent customer interactions that occur in the messaging thread. A conversion on your website or in your app goes through the matching Conversions API product instead.
What happens with a wrong value: Meta’s documentation does not say whether Meta rejects a chat event with another action_source, or accepts it and does not tie it to the ad. This guide does not guess. What is clear is that the event then describes a conversion that did not come from an ad that clicks to WhatsApp, Messenger or Instagram, which is the one case the business_messaging action_source is defined for.
Most often, teams that already had website tracking and then added Click to WhatsApp ads. The website Conversions API setup works, so it gets reused for chat sales, and its action_source comes along. Agencies that send events from a CRM or an automation tool see it too, because one template serves every client and every channel. If you also send app events and are missing action_source there, that is a different problem, covered in the missing action_source guide.
Here is a WhatsApp Purchase event with the wrong action_source and no messaging_channel:
POST https://graph.facebook.com/v26.0/<DATASET_ID>/events?access_token=<ACCESS_TOKEN>
{
"data": [
{
"event_name": "Purchase",
"event_time": <UNIX_TIMESTAMP_IN_SECONDS>,
"action_source": "website",
"user_data": {
"whatsapp_business_account_id": "<WHATSAPP_BUSINESS_ACCOUNT_ID>",
"ctwa_clid": "<CLICK_TO_WHATSAPP_CLICK_ID>"
},
"custom_data": {
"currency": "USD",
"value": 49
}
}
]
}And the fixed payload, with the business_messaging action_source and the channel:
POST https://graph.facebook.com/v26.0/<DATASET_ID>/events?access_token=<ACCESS_TOKEN>
{
"data": [
{
"event_name": "Purchase",
"event_time": <UNIX_TIMESTAMP_IN_SECONDS>,
"action_source": "business_messaging",
"messaging_channel": "whatsapp",
"user_data": {
"whatsapp_business_account_id": "<WHATSAPP_BUSINESS_ACCOUNT_ID>",
"ctwa_clid": "<CLICK_TO_WHATSAPP_CLICK_ID>"
},
"custom_data": {
"currency": "USD",
"value": 49
}
}
]
}Everything in angle brackets is a placeholder. Never publish a real token, ID or click ID.

Each cause below says where the evidence comes from. Causes 3 and 5 rest on Meta’s own documentation. Causes 1, 2 and 4 are common causes seen in practice, not statements from Meta.
Support: common cause in practice. Meta defines website as a conversion made on your website, which a sale closed in a WhatsApp chat is not.
Fix: give chat events their own payload builder, with the business_messaging action_source and a messaging_channel, instead of reusing the website event code.
How to confirm: log one real chat event before it is sent and read the action_source value. If it says website, look for a shared function or constant that sets it for every event.
Support: common cause in practice. Many integrations and templates fill action_source with a fixed default, and that default is rarely business_messaging.
Fix: open the step that builds the request and set action_source to business_messaging and messaging_channel to the channel of the conversation. If one flow serves website and chat sales, branch it so each gets its own value.
How to confirm: check the run history of the flow and read the request body it actually sent, not the field mapping on screen.
Support: Meta’s server event parameters. Meta defines chat as a conversion made via a messaging app, SMS, or online messaging feature, and other as a conversion that happened in a way that is not listed. Only business_messaging is defined as a conversion from ads that click to Messenger, Instagram or WhatsApp.
Fix: for a conversion that started from a Click to WhatsApp, Messenger or Instagram ad, use the business_messaging action_source, not chat or other.
How to confirm: ask where the conversation started. If it started from one of those ads, and you have its click ID or the matching customer data, the value is business_messaging.
Support: common cause in practice. Meta defines app as a conversion made on your mobile app.
Fix: keep app events and chat events in separate code paths. A sale inside a WhatsApp conversation is a chat event, even if your app team owns the server that sends it.
How to confirm: search the codebase for where action_source is set and check that chat events never pass through the app event code.
Support: Meta’s Conversions API for Business Messaging guide pairs the business_messaging action_source with messaging_channel in all three samples, with the values whatsapp, messenger and instagram. Meta’s documentation does not state what happens when it is missing.
Fix: always send messaging_channel, in lowercase, matching the channel where the conversation took place: whatsapp for WhatsApp, messenger for Messenger and instagram for Instagram Direct.
How to confirm: compare each event with Meta’s sample for its own channel. A WhatsApp event should carry whatsapp and the WhatsApp Business Account ID, not a Messenger or Instagram field.
test_event_code before you go live. For the full setup, see the Meta Conversions API for Business Messaging guide.Paste your payload into the CAPI Debugger. It checks chat events only. If the business_messaging action_source is not set, it tells you the event is not a chat event and points you to Meta’s Payload Helper for website or app events. It also flags a missing or wrong messaging_channel as an error. The check runs in your browser and nothing is uploaded, but replace the real token with a placeholder before you paste.
For other chat event problems, go back to the debug hub.
For a conversion from a Click to WhatsApp ad, use business_messaging. Meta defines it as a conversion made from ads that click to Messenger, Instagram or WhatsApp, and its Business Messaging samples use it with messaging_channel set to whatsapp.
No. Meta defines chat as a conversion made via a messaging app, SMS, or online messaging feature. Only business_messaging is defined for conversions from ads that click to Messenger, Instagram or WhatsApp.
Meta’s documentation does not say whether such an event is rejected or accepted without being tied to the ad. Either way, it describes a website conversion, so set the business_messaging action_source for chat conversions.
Meta’s Business Messaging samples use whatsapp, messenger and instagram, one for each type of ad. Send the one that matches the conversation.
No. Meta says messaging events should only represent interactions in the messaging thread. A conversion on your website or in your app goes through the matching Conversions API product.
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.