> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/bot-builder/whatsapp-chatbot/whatsapp-conversions-api-setup.md).

# WhatsApp Conversions API Setup

Step 1: Open WhatsApp Channel Configuration

* Navigate to **Channels**
* Open **WhatsApp Channel Configuration**
* Click on the **WhatsApp Icon**

Step 2: Manage Data Set

* Select **Manage Data Set for Conversions API**
* Click on **Create New Data Set**
* Enter the data set name
* Click on **Create Data Set**

Step 3: Open Bot Builder

* Navigate to **Bot Builder**
* Open the required **Chatbot Flow**

Step 4: Add Conversion Event

* Select the node where you want to add the event
* Go to **Native Tools**
* Click on **Send Conversion Event**

Step 5: Configure Event Details

* Select the created **Data Set**
* Choose the required **Conversion Event**
* Add custom event data if needed

Step 6: Save and Publish

* Save the bot flow
* Publish the changes

Step 7: Track Events in Meta

* Events will automatically appear inside **Meta Ads Manager**
* Use them for:
  * Campaign optimization
  * Retargeting
  * Conversion tracking
  * Performance analysis

{% embed url="<https://www.youtube.com/watch?v=JCO65k_mE2A>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocumentation.gitbook.io/user-documentation/bot-builder/whatsapp-chatbot/whatsapp-conversions-api-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.