Table of Contents
ToggleShort answer: your Meta Conversions API app event was sent without the action_source field. Meta lists this field as Required in its server event reference. For events that come from a mobile app, add "action_source": "app" to every event object. For events from a website, the value is "website".
This guide is for app developers and marketers who send app events to Meta through the Conversions API, either from their own server or through an MMP. Below you will find the exact wording from Meta’s documentation, a wrong and a corrected payload, the five most common causes, and the fix steps.
The button opens the mobile app attribution debugger with a sample payload that shows this exact error. Everything runs in your browser.

action_source as Required and describes it like this: “This field allows you to specify where your conversions occurred.”Meta also states that by using the Conversions API you agree that the value you send is accurate to the best of your knowledge. The documented values are:app: the conversion was made on your mobile appwebsite: the conversion was made on your websitebusiness_messaging: the conversion came from ads that click to Messenger, Instagram or WhatsAppemail, phone_call, chat, physical_store, system_generated and otheraction_source does not follow Meta’s documented event format. Depending on how you send it, the event can be rejected or flagged, and it may not count toward measurement or optimization the way you expect. Because the field is required, the safe approach is to treat a missing action_source as a blocking problem and fix it before you look at anything else. The mobile app attribution debugger reports it the same way: as a blocking finding.{
"data": [
{
"event_name": "Purchase",
"event_time": 1761570000,
"event_id": "order_10492",
"user_data": {
"em": ["HASHED_EMAIL_SHA256"]
},
"app_data": {
"advertiser_tracking_enabled": 1,
"application_tracking_enabled": 1,
"extinfo": ["i2","com.example.myapp","1.4.2","1.4.2.118","17.5.1","iPhone15,2","en_US","PDT","Carrier","1179","2556","3.00","6","128","64","America/Los_Angeles"]
},
"custom_data": {
"currency": "USD",
"value": 29.99
}
}
]
}
And the corrected version, with "action_source": "app" added to the event:
{
"data": [
{
"event_name": "Purchase",
"event_time": 1761570000,
"event_id": "order_10492",
"action_source": "app",
"user_data": {
"em": ["HASHED_EMAIL_SHA256"]
},
"app_data": {
"advertiser_tracking_enabled": 1,
"application_tracking_enabled": 1,
"extinfo": ["i2","com.example.myapp","1.4.2","1.4.2.118","17.5.1","iPhone15,2","en_US","PDT","Carrier","1179","2556","3.00","6","128","64","America/Los_Angeles"]
},
"custom_data": {
"currency": "USD",
"value": 29.99
}
}
]
}
All values above are placeholders. Replace the hashed email, bundle ID, versions and device details with your real data. Meta’s guide for app events through the Conversions API also requires event_id for deduplication, app_data.advertiser_tracking_enabled, and an extinfo array of 16 values in a fixed order, so check those too.actionSource, action-source or source are not action_source. Meta does not read them as action_source, so the field is effectively missing.data array. It belongs on every event.data array. Each one needs its own action_source."app" for mobile app events, or "website" for website events. Use the value that is true for where the conversion happened.action_source there instead of patching single events, so every event type inherits it.action_source before sending it.other just to make the error disappear. Meta asks you to send an accurate value, and app is the correct one for events that happen in your mobile app.action_source is present, and flag other problems in the same event. You can start from the sample first:Sending web or Click-to-WhatsApp events instead? Use the CAPI debugger. For more fixes like this one, go back to the debug hub.action_source as Required. Send it with every event.app. For events from a website, use website.data array, so every event needs its own value.app_data.advertiser_tracking_enabled and an extinfo array of 16 values, and it asks for event_id for deduplication.app for app events so that your data describes where the conversion really happened.