Search

How to Verify That CAPI Events Were Successfully Sent

Article author
Learning Center Mekari
  • Updated

After configuring CAPI events and publishing the ad, make sure that the events sent from Mekari Qontak were successfully received by Meta. Verification is necessary to ensure that configurations such as the Pixel and conversion events are correct. Configuration errors do not always display an error message, so ads and conversations may continue to run even when the event is not sent.

In this guide, you will learn how to verify the CAPI events that are sent to ensure that conversion data has been correctly received by Meta.

A. Checking Through Meta Events Manager

  1. Open “Events Manager” through business.facebook.com/events_manager.
  2. On the left panel, select the “Datasets” used for your use case.
  3. Open the “Overview” tab. You will see a list of received events along with the time they were received. Make sure the following information is correct:
What to Check Expected Value
Event Name Matches your use case configuration, such as Purchase.
Connection Method Server: indicates that the event originated from the Conversion API.
Time of the Last Event Matches the time of your test.

  1. Check “Event Match Quality”. This metric indicates Meta’s ability to match events with users. A higher score indicates a better data match, which can support ad attribution and optimization.

B. Using Test Events

Meta provides the “Test Events” feature to check events directly without having to wait for the data processing.

  1. Open “Events Manager”, select “Set Data”, then open the “Test Events” tab.

  2. Run the test according to the procedure in the following section.
  3. Check the received event. The event will be displayed within a few seconds after Meta receives it.

This feature can help you verify the configuration at an early stage because the test results can be viewed immediately.

C. Checking Through Event Logs in Mekari Qontak 

Mekari Qontak provides a history of event deliveries through Event Logs. This information includes the status of each event and the reason for the failure if the event was not successfully sent. The mechanism is as follows:

To access the Event log page, follow these steps:

  1. Log in to your Qontak account, then select the “Settings” menu.
  2. Then select the Integrations tab and click “Channel Integration”.
  3. Then, in the Meta conversion API manager section, click “Manage”.
  4. Then select one of the Pixel name options and click “View details”.
  5. Next, click View event log”.
  6. You will then be directed to the ‘Event log’ page. On this page, you can check the status of successful data delivery.
     

D. Testing Procedure 

Perform the following test using your personal device to ensure that the CAPI event is successfully sent:

  1. Make sure your CTWA ad is live.

  2. Open Facebook or Instagram on your mobile device, then find the ad and click “Send Message”.

    Click the ad directly from the feed, not through the preview in “Ads Manager”. The preview does not generate ctwa_clid.

  3. Send an opening message in the conversation.
  4. Make sure the conversation appears in the Mekari Qontak “Inbox”.
  5. Trigger the event according to your use case configuration. For example, add the appropriate Room Tag or complete a transaction through Desty Commerce.
  6. Open “Events Manager”, then check whether the event has been received.
  7. For the received event, make sure that “Connection Method” shows “Server”.

If all steps are successful, your CAPI configuration is functioning correctly.

E. Quick Diagnosis of CAPI Event Delivery Issues 

Symptom Possible Cause
No events appear at all in “Events Manager” The Pixel ID is incorrect or the Business Manager connection has been disconnected.
The event appears but is not attributed to the ad ctwa_clid is unavailable or the conversation originated from an organic source.
The event appears in “Events Manager” but does not appear in the campaign report The event in the “Ads Set” differs from the event that was sent.
The event is counted twice There are overlapping use cases.
A Purchase event is sent without a transaction value The transaction value is unavailable from the trigger source.
“Connection Method” shows “Browser” The event originated from the Pixel code on the website, not from CAPI.

F. Regular Monitoring of Event Delivery 

Verification should not only be performed when the configuration is initially set up. Check regularly to ensure that events continue to be sent and that the received data matches your sales activity.

  • Weekly — check “Events Manager” to make sure that events are still being received normally.

  • Monthly — compare the number of Purchase events with your actual sales records.

If the difference between the number of Purchase events and actual transactions continues to increase, review the configuration and compliance with Room Tag implementation.
 

This concludes the explanation of how to verify that CAPI Events were successfully sent. 

Diskusikan fitur ini