> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/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/lead-source/facebook-lead-ads-integration.md).

# Facebook Lead Ads Integration

#### Step 1: Create Connection

* Go to **Lead Source**.
* Select **Facebook Lead Ads**.
* Click **Create Connection**.
* Click **Connect with Facebook**.

#### Step 2: Authorize Facebook Account

* Log in to your Facebook account.
* Select **All Current and Future Pages**.
* Grant the required permissions.
* Click **Continue** to authorize.

#### Step 3: Select Page & Form

* Choose your **Facebook Page**.
* Select the **Lead Form**.
* Add the **Webhook URL** (if required).
* Click **Finish Setup**.

#### Step 4: Configure Field Mapping

* Open the **Installed** tab.
* Go to **Field Mapping**.
* Map Facebook lead fields (Name, Email, Phone, etc.) to your CRM fields.
* Save the mapping.

#### Step 5: Configure Webhook (Optional)

* Create a **Custom Webhook** in the platform.
* Copy the Webhook URL.
* Add it to the Facebook Lead Ads integration.
* Select the required event and save.

#### Step 6: Test the Integration

* Use **Meta Lead Ads Testing Tool** to create a test lead.
* Verify that the test lead is received successfully.

#### Step 7: Monitor Logs

* Go to the **Webhook Logs** section.
* Review lead details, synchronization status, and any errors.

Your Facebook Lead Ads integration is now ready, and all new leads will automatically sync to your CRM.

{% embed url="<https://youtu.be/da8iN86QUkA>" %}


---

# 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/lead-source/facebook-lead-ads-integration.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.