--- title: "Troubleshoot Meta Conversions API" slug: "troubleshoot-meta-conversions-api" description: "Fix Meta CAPI connection errors, missing or rejected events, dataset issues, and missing ad attribution in Kommo." tags: ["Meta Events Manager", "Event Attribution"] status: "new" updated: 2026-11-03T12:00:41Z published: 2026-11-03T12:00:41Z canonical: "support.kommo.com/troubleshoot-meta-conversions-api" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.kommo.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshoot Meta Conversions API > [!NOTE] > What you’ll need > > - Access to the affected pipeline trigger or Salesbot. > - Access to the Facebook account used to authorize CAPI and the relevant Meta business assets and datasets. > - An affected lead card to check the sending result. > > Keep in mind > > - CAPI supports [Facebook Messenger](/resources/docs/facebook-overview), [Instagram](/resources/docs/instagram-overview), and [WhatsApp Business](/resources/docs/whatsapp-business-overview) sources. > - WhatsApp events are sent only for leads from Click-to-WhatsApp ads. > - Delivery can take up to 30 minutes, and the dataset can take up to a day to update. > - The source determines the dataset. You cannot choose it manually. Use this guide when you cannot connect Meta Conversions API (CAPI), an event does not reach Meta, or a received event does not appear in your ad results. The checks apply to both pipeline triggers and Salesbot actions unless stated otherwise. > [!WARNING] > **Important:** Kommo has no test mode for CAPI. Any event you send while checking the integration reaches Meta as a real event. ## Find the problem you’re seeing Start with the symptom that matches your situation: | **What you see** | **Go to** | | --- | --- | | The connection fails or Meta shows an authorization error | [The Meta account will not connect](/resources/docs/troubleshoot-meta-conversions-api#the-meta-account-will-not-connect) | | The field you want is not available when mapping data | [A Kommo field is missing from the mapping list](/resources/docs/troubleshoot-meta-conversions-api#a-kommo-field-is-missing-from-the-mapping-list) | | No event appears in Meta Events Manager | [An event does not appear in Meta Events Manager](/resources/docs/troubleshoot-meta-conversions-api#an-event-does-not-appear-in-meta-events-manager) | | Meta rejects an event because purchase data is missing | [Meta rejects a Purchase, Order Created, or Order Shipped event](/resources/docs/troubleshoot-meta-conversions-api#meta-rejects-a-purchase-order-created-or-order-shipped-event) | | The event is not in the dataset you were checking | [An event is missing from the dataset you expected](/resources/docs/troubleshoot-meta-conversions-api#an-event-is-missing-from-the-dataset-you-expected) | | The event arrived, but there is no conversion in the ad results | [An event appears in Events Manager but not in your ad results](/resources/docs/troubleshoot-meta-conversions-api#an-event-appears-in-events-manager-but-not-in-your-ad-results) | A **dataset** is where Meta receives and organizes your events. **Ad attribution** means Meta connects an event to an interaction with an ad. Receiving an event and attributing it to an ad are separate steps. ## The Meta account will not connect **Why this happens:** The Facebook session may no longer be valid, or Meta may return an error during authorization. **What to do:** 1. Open the affected CAPI trigger or Salesbot action in Kommo. 2. Use the authorization link to authorize the connection again. 3. After authorization, select the Facebook Pages, Instagram accounts, or WhatsApp numbers you need. 4. If authorization still fails, contact Kommo support. Include the error message or report shown by Meta. ## A Kommo field is missing from the mapping list **Why this happens:** The field type may be unsupported, incompatible with the selected Meta parameter, or already included in a default mapping. **What to do:** 1. Check the Kommo field’s type against the supported types below. 2. If its type is unsupported, store the information in a supported field, such as **Text** or **Numeric**. 3. If you selected a Meta parameter first, choose one compatible with the field. Alternatively, clear the Meta parameter and select the Kommo field first. 4. For contact phone numbers and email addresses, review the default mapping instead of adding a custom pair. **Supported field types:** Text, Numeric, Select, Multiselect, Date, Birthday, Date and time, URL, Text area, Radiobutton, Short address, Multitext, and UTM. > [!NOTE] > **Note:** Kommo sends all contact phone numbers and email addresses with every event. The four default mapping pairs cannot be deleted, but you can change the Kommo field that supplies the data for each predefined Meta parameter. ## An event does not appear in Meta Events Manager **Why this happens:** The automation may not have run, the primary contact may not have an eligible messaging profile, an integration may be disconnected, or Meta may still be processing the event. **What to do:** 1. Check your automation. For pipeline automation, confirm the trigger is active and its execution conditions match the lead. For Salesbot, confirm the bot started through its configured condition and reached the CAPI action. 2. Open the lead card and check the sending result in the lead feed. 3. Check the selected sources. Pipeline triggers have **no sources selected by default**. Salesbot actions have **All selected by default**. 4. Check that the lead’s primary contact has an eligible messaging profile from one of those sources. A source is the connected Facebook Page, Instagram account, or WhatsApp number. 5. Confirm the relevant Facebook Messenger, Instagram, or WhatsApp Business integration is still connected in Kommo. 6. If CAPI is no longer authorized, authorize it again in the CAPI settings. 7. For WhatsApp, confirm the lead came from a **Click-to-WhatsApp ad**. Kommo does not send events for other WhatsApp leads. 8. Allow up to **30 minutes** for delivery and up to **a day** for the dataset to update, then check Meta Events Manager again. If the lead feed shows a rejection, follow the rejected-event instructions below. If it identifies a dataset different from the one you expected, follow the dataset instructions. ## Meta rejects a Purchase, Order Created, or Order Shipped event **Why this happens:** Currency is missing, or a **Purchase** event has no purchase value. Meta may return these codes when currency is missing: | **Event** | **Error code for missing currency** | | --- | --- | | Purchase | 2804010 | | Order Created | 2804081 | | Order Shipped | 2804085 | **What to do:** 1. Open the affected lead card. 2. Check the currency next to the lead’s **Sale** amount. If it is missing or incorrect, ask your Kommo admin to check **Currency** in **Settings > Workspace settings > General settings**. This setting applies across the workspace. See [Manage workspace settings](/resources/docs/manage-workspace-settings). 3. For **Purchase**, enter the final amount in **Sale**, which supplies the event value with the default mapping. If you changed that mapping, check the field selected for **Value** instead. 4. After correcting the data, check the lead feed for a new sending result. 5. If the event is still rejected or no new result appears, contact Kommo support to confirm how to resend it. Include the affected lead and error code. > [!WARNING] > **Important:** Do not resend an event Meta already accepted to fix missing ad attribution. Check the dataset and ad account connection instead. ## An event is missing from the dataset you expected **Why this happens:** You may be looking at a different dataset, Kommo may have created a new one, or the dataset may belong to another business portfolio. The Facebook account used for authorization may also lack access. **What to do:** 1. Open the lead card and check the lead feed for the dataset that received the event. 2. Find that dataset in **Meta Events Manager**. If no dataset was linked to the source, Kommo creates one with the same name as the source. 3. Check that the dataset belongs to the business portfolio connected to Kommo. 4. Confirm the Facebook account used to authorize CAPI has access to the dataset. 5. If access is missing, grant it in Meta or authorize CAPI again with an account that has access. The event’s source determines its dataset; you cannot select the destination manually. For WhatsApp, the dataset belongs to the **WhatsApp Business Account (WABA)** that owns the number and is separate from a website pixel. If the primary contact has several eligible messaging profiles from selected sources, Kommo sends an event for each profile to its corresponding dataset. ## An event appears in Events Manager but not in your ad results **Why this happens:** Meta received the event but could not connect it to a Click-to-Message ad interaction, or the dataset is not connected to the correct ad account. **What to do:** 1. Confirm that the lead or conversation came from a **Click-to-Message ad**. Kommo’s CAPI integration does not provide attribution for other ad types, such as website conversion campaigns. 2. Open the lead feed and identify the dataset that received the event. 3. In **Meta Business Manager**, check that this dataset is connected to the correct ad account. 4. If the source and dataset are correct but attribution is still missing, contact Kommo support. Ask them to check whether the identifier needed to match the event to the ad interaction is available. > [!NOTE] > **Note:** Facebook Messenger and Instagram events can reach Meta even when Meta cannot attribute them to an ad. Successful delivery does not guarantee ad attribution. ## Before contacting Kommo support Confirm that: - The relevant messaging integration is connected, and CAPI is authorized. - The required sources are selected. - The pipeline trigger conditions match the lead, or Salesbot started and reached the CAPI action. - Mapped fields use supported, compatible types. - Required data is present: **value and currency for Purchase**, and **currency for Order Created and Order Shipped**. - You checked the sending result and destination dataset in the lead feed. - You allowed time for delivery and dataset updates. For the complete setup and delivery-check instructions, see [Set up Meta Conversions API (CAPI)](/resources/docs/set-up-meta-conversions-api-capi). When contacting support, include the **affected lead**, the **pipeline trigger or Salesbot action**, and any **error message or code shown in Kommo or Meta**. ## Related - [Meta Conversions API (CAPI)](/meta-conversions-api-capi.md) - [Meta Conversions API (CAPI) overview](/meta-conversions-api-capi-overview.md)