> For the complete documentation index, see [llms.txt](https://docs.patagon.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patagon.ai/en/marketing-and-attribution/meta-ads.md).

# Meta Ads

Everything you need to run and measure WhatsApp campaigns with Meta — from connecting your account to building the campaigns themselves.

There are two parts:

* [**How to connect Meta and map conversions**](/en/marketing-and-attribution/meta-ads/meta-conversions-api.md) — link your Meta account so Patagon AI can send your *qualified-lead* conversions back to Meta's Conversions API, and Meta's optimization can learn from them. This is also where you'll find what data Patagon AI sends and how to set up the dataset your Click-to-WhatsApp campaigns need.
* [**How to create Meta campaigns**](/en/marketing-and-attribution/meta-ads/meta-campaigns.md) — build the campaigns that drive WhatsApp conversations: Landing → WhatsApp (attributable on your own page) and Click-to-WhatsApp (opens WhatsApp straight from the ad).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.patagon.ai/en/marketing-and-attribution/meta-ads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.