Meta CAPI Error 2804131: 5 Easy Fixes

Short answer: Meta CAPI error 2804131 comes back with code 100 when Meta cannot find a Page tied to the dataset your chat event was sent to. The usual reasons are a page_id inside a WhatsApp event, or an event sent to a dataset that is not the one linked to your WhatsApp Business Account. Check the dataset ID in the URL, then check what is inside user_data.

This guide is for developers, marketers and agencies who send WhatsApp, Messenger or Instagram events to Meta through the Conversions API for Business Messaging. Below you will find what the response looks like, who gets it, a wrong and a fixed payload, five causes with a way to confirm each one, and how to confirm the fix.

Check this example in the debugger

The button opens the CAPI debugger with a sample error response that contains subcode 2804131. Everything runs in your browser.

What Meta CAPI error 2804131 looks like

Your request reaches the Graph API, and the response body carries an error with code 100 and error_subcode 2804131. The message text is short. The wording I have seen reported is “No Page associated to the dataset”. The CAPI debugger words it as “No Page is linked to this dataset”, which means the same thing.

{
  "error": {
    "message": "No Page associated to the dataset",
    "type": "OAuthException",
    "code": 100,
    "error_subcode": 2804131
  }
}

Please note what is and is not confirmed. Meta’s public documentation for business messaging does not list this subcode or its message text. The wording above comes from developer reports, so the exact text may differ slightly in your response. Match on the subcode number, not on the sentence.

Who gets this error

In practice, people who send WhatsApp events with Messenger fields in them, people who send chat events to a dataset that is not linked to the right account, and people who reuse code written for one channel on another. A website pixel dataset is a common wrong destination, because it looks like a normal dataset ID but has no WhatsApp account behind it.

Wrong payload vs fixed payload

Here is a WhatsApp Purchase event with a page_id in user_data. Page ID is a Messenger and Instagram field, and this is the pattern developers have reported alongside Meta CAPI error 2804131:

{
  "data": [
    {
      "event_name": "Purchase",
      "event_time": 1761570000,
      "event_id": "order_58213",
      "action_source": "business_messaging",
      "messaging_channel": "whatsapp",
      "user_data": {
        "page_id": "112233445566778",
        "ctwa_clid": "ARAExampleClickId0123456789"
      },
      "custom_data": {
        "currency": "USD",
        "value": 49.0
      }
    }
  ]
}

And the fixed version, with the WhatsApp Business Account ID in place of the Page ID:

{
  "data": [
    {
      "event_name": "Purchase",
      "event_time": 1761570000,
      "event_id": "order_58213",
      "action_source": "business_messaging",
      "messaging_channel": "whatsapp",
      "user_data": {
        "whatsapp_business_account_id": "123456789012345",
        "ctwa_clid": "ARAExampleClickId0123456789"
      },
      "custom_data": {
        "currency": "USD",
        "value": 49.0
      }
    }
  ]
}

All IDs above are made up. Use your own values. The fixed event goes to https://graph.facebook.com/v26.0/DATASET_ID/events, where DATASET_ID is the dataset linked to your WhatsApp Business Account.

Meta CAPI error 2804131 dataset and Page link diagram

5 causes of Meta CAPI error 2804131 and how to fix them

Each cause of this error says how well it is supported. “Meta docs” means it follows from Meta’s Conversions API for Business Messaging guide. “In practice” means it comes from developer reports or from how the pieces fit together, and Meta does not state it.

1. A page_id inside a WhatsApp event

Support: in practice. Meta’s guide lists page_id as a Messenger field and whatsapp_business_account_id as the WhatsApp field. A public developer repository reports that moving from page_id to whatsapp_business_account_id removed the error.

Fix: on the ctwa_clid path, build user_data from whatsapp_business_account_id and ctwa_clid only.

One exception to know: Meta’s guide says an event sent without a click ID, using hashed customer information, must include page_id. If you are on that path and see this error, the dataset in your URL is the first thing to check (cause 2).

How to confirm: open the event you sent and look for page_id inside user_data on a WhatsApp event. Paste it into the debugger, which flags it as rule R-WA-04.

2. The dataset is not linked to your WhatsApp Business Account

Support: Meta docs for how datasets are created, in practice for the error itself. Meta’s guide says the dataset for WhatsApp is created with your WhatsApp Business Account ID and access token, and that a separate call retrieves the dataset ID. An ID that came from somewhere else, such as a website pixel, is a different dataset. One developer report saw this error after sending to a website pixel.

Fix: send to the dataset that belongs to your WhatsApp Business Account.

How to confirm: take the ID in your URL and compare it with the dataset ID returned by the retrieve call in Meta’s guide, using your WhatsApp Business Account ID. In practice the dataset ID is also shown in Events Manager under Data sources. If the two IDs differ, you found it.

3. The URL has the wrong ID

Support: in practice, and not confirmed to return this code. Meta’s endpoint is /DATASET_ID/events. Putting a WhatsApp Business Account ID or a Page ID there is a common mistake, and the debugger flags it as rule R-ENV-13. I could not confirm that Meta answers it with 2804131, so treat it as a related mistake. You may see a different error.

Fix: POST to /DATASET_ID/events with the dataset ID.

How to confirm: read the ID between v26.0/ and /events in your request URL, and check it against the dataset ID from cause 2.

4. Messenger or Instagram events sent to a dataset with no Page connected

Support: partly Meta docs. Meta’s guide says a Messenger dataset is created with a page_id, and that you can only link one dataset to a Page. It does not say what happens when a Messenger or Instagram event reaches a dataset that has no Page. The link between that situation and this error is a reasonable reading of the message, not a Meta statement.

Fix: create or retrieve the dataset for your Page as Meta’s guide describes, and send to that dataset.

How to confirm: check that the dataset you send to is the one created for your Page, and that the event carries that same Page ID.

5. A copied template that mixes channels

Support: in practice. Merged samples and reused code are a common way to end up with page_id in a WhatsApp event, or WhatsApp fields in a Messenger one.

Fix: build each event from one channel’s sample only. Meta’s guide shows separate sample user_data for each: Messenger uses page_id and page_scoped_user_id, WhatsApp uses whatsapp_business_account_id and ctwa_clid, and Instagram uses instagram_business_account_id and ig_sid.

How to confirm: compare the field names in your user_data and your messaging_channel against the list above. Any field from another channel is a leftover.

How to confirm the Meta CAPI error 2804131 fix

  1. Add test_event_code to the request, at the top level next to data, using the code shown in the Test Events tab of Events Manager.
  2. Send one event to /DATASET_ID/events and check that the response no longer contains error_subcode 2804131.
  3. Open Test Events and check that the event appears.
  4. Remove test_event_code before you go live, so your real events are not sent as test traffic.

test_event_code is the standard Conversions API testing parameter. Meta’s business messaging guide does not describe it, so rely on what you see in Events Manager.

Check your own Meta CAPI error 2804131 response

Paste your error response or your payload into the CAPI debugger, and it will explain the subcode and flag other problems in the same event. It finds and explains the problem, it does not change your payload.

Check this example in the debugger

The check runs in your browser and nothing is uploaded. If the findings are more than you want to fix yourself, use the buttons under the report to request a written fix plan. For a related error, read the error 2804066 guide, or go back to the debug hub. Source for the dataset and field names: Meta, Conversions API for Business Messaging.

Frequently asked questions

What does Meta CAPI error 2804131 mean?

It is a code 100 error with subcode 2804131, reported with a message such as “No Page associated to the dataset”. In plain words, Meta cannot find a Page tied to the dataset your event went to. Meta’s public docs do not list this subcode, so the meaning comes from the message and developer reports.

Why do I get it on a WhatsApp event?

The most reported cause is a page_id in user_data on a WhatsApp event, or a dataset that is not linked to your WhatsApp Business Account. Use whatsapp_business_account_id and ctwa_clid on the click ID path, and send to the dataset linked to your WhatsApp Business Account.

Does a WhatsApp event ever need page_id?

Meta’s guide says an event sent without a click ID, using hashed customer information, must include page_id. On the ctwa_clid path, leave it out. Meta says to send ctwa_clid whenever you have it.

Where do I find my dataset ID?

Meta’s guide describes a call that retrieves the dataset ID using your WhatsApp Business Account ID and access token. In practice it is also shown in Events Manager under Data sources.

Can the wrong ID in the URL cause this error?

It is a common mistake, and the endpoint should use the dataset ID. I could not confirm that it returns 2804131 specifically, so you may see a different error.

How do I test that the fix works?

Send one event with test_event_code, check that the response has no error and that the event appears in Test Events, then remove the code before going live.

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.