Facebook CAPI Qualified Lead Optimize
Conversion API (CAPI) is designed to create a connection between an advertiser's marketing data from various sources and Meta's system, optimizing ad targeting, reducing cost per result, and measuring outcomes.
Instead of maintaining separate connection points for each data source, you can leverage the Conversion API to send multiple types of events.
This article will guide you on setting up the Conversions API on AhaChat, allowing the chatbot to automatically send events when customers successfully place an order or when staff create an order for a customer directly to Meta. This helps businesses accurately track purchasing behavior, optimize ad campaigns, and increase conversion rates.
Terminology and Definitions
Dataset (Pixel): A data source from Meta to collect conversion signals from external sources. This data is referred to as "Events."
Event: Information describing customer (subscriber) actions. There are the following types of events:
- Purchase
- Lead Submitted
- Qualified Lead
- Order Created
- Order Shipped
- Order Canceled
- Order Returned
- View Content
- AddToCart
- Initiate Checkout
Conversion: Simply put, it is the transition from entity state A to state B. It represents the ratio of users clicking on an advertisement based on a specific goal. For example, they might visit to look for product information, place an order, make a payment, or register as a member. Depending on the fanpage's specific field, objectives can be set to increase the conversion rate accordingly.
Specific Example:
For a fanpage specializing in children's toys, a recent Click-to-Messenger ad campaign recorded 650 messages, of which 270 were purchase registrations. The conversion rate can be calculated as follows:
CR = 270/650 * 100% = 41%
1. Set up a Dataset on AhaChat.
Check out the full guide in this article
2. Create and send events from the Chatbot to Meta.
Case 1: Send events from the flow.
In a flow on AhaChat, you need blocks to collect information from customers, then connect the Facebook CAPI block at the final step of the flow.
Open the block and select the event listed in the Facebook CAPI block.
Click Send to check if the event is successfully sent. You will receive the result in JSON format.
You can create an additional conditional branch to check if the event has run successfully, including error messages, and send notifications to the administrator or another system.
Example:
To get the error notification content:
Case 2: Send events from an external CRM source.
To send events from an external source, you need to use AhaMake to send data to the Chatbot.
In this example, we use AhaMake to receive information from the SPA store's website when a customer fills out a booking form, then send it to the chatbot to trigger the CAPI block.
On AhaChat → Create a CAPI flow with the Event is: “Qualified Lead”
On AhaMake, create a Flow with the Trigger "Webhook Trigger"
Next, create the AhaChat app with the action "Send Broadcast Block." Retrieve the information from the “Webhook Trigger” to pass it along (see the guide for using actions with AhaChat here).
Note: To send data to the chatbot, you need to synchronize the customer's phone number on AhaChat with the phone number entered on the website.
With just two simple steps, when a customer fills out a booking form on the website, the information will be sent via AhaMake's “Webhook Trigger”, then forwarded to the chatbot to activate the CAPI block and send the event to Meta.
3. Results
If everything is done correctly, you will be able to view the results in the overview report section of the Event Manager.
