> For the complete documentation index, see [llms.txt](https://docs.neodove.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neodove.com/admin-portal/integrations/facebook-integration/common-errors.md).

# Common Scenarios for errors in Facebook Integration

### **Scenario 1 :-**&#x20;

***

Multiple integration of the **Facebook same page.**

{% hint style="success" %}
**Answer ->**&#x20;

In NeoDove for **Facebook Integration** you connect a Facebook Page.&#x20;

All the leads coming through the **Ads** of selected **Facebook page** will be created in NeoDove through the **single integration**.&#x20;

If you create **multiple integration** using same Facebook Page then the **leads** will not be created under **NeoDove campaign**.
{% endhint %}

### **Scenario 2 :-**&#x20;

***

On the **Testing Page**, error is coming as **“Lead Access has been revoked”** while testing the integration.

<figure><img src="/files/hFYhB6NhftLkcCHhNQW7" alt="" width="563"><figcaption><p>Allow access to any CRM on Facebook</p></figcaption></figure>

{% hint style="success" %}
**Answer ->**

1. Then go to the “**Meta Business Suite**” of your Facebook account.
2. Go to the **Settings** on the bottom.
3. Go to the **Business Settings**.
4. Click on the “**Integration option**” on the left side Menu.
5. Click on the “**Lead Access**” option.
6. Then go to the option “**CRMs**”
7. Then select “**NeoDove**” and allow.
   {% endhint %}

### **Scenario 3 :-**&#x20;

***

**Custom Questions** in the Facebook Lead Form.

1. Check the **Form** under Facebook which is **active** on FB Ad. [Click here](https://business.facebook.com/latest/instant_forms/forms/)
2. Check the “**Question Type**” of the form.

<figure><img src="/files/4qRgHrudihJCyPrGVCYY" alt="" width="563"><figcaption></figcaption></figure>

3. If you are using the **custom questions** for collecting "name" & "phone number" then the **field name** of these questions will be **different** which NeoDove accepts by **default**.

<figure><img src="/files/7ylE95QHTmywy4eO5WYo" alt="" width="563"><figcaption><p>Field name of the questions in your Facebook lead forms</p></figcaption></figure>

4. Then you have to do the Facebook Integration with the “**Custom Form Field Names**” feature and **map** the same field name according to your **FB lead form**.

**Image 1**

<figure><img src="/files/GPOm3LWBmM33KAOFOaty" alt=""><figcaption></figcaption></figure>

**Image 2**

<figure><img src="/files/KbHxn4tbkUDLEEtjbvps" alt=""><figcaption></figcaption></figure>

### **Scenario 4 :-**&#x20;

***

Different **form field names** on Facebook Lead Form.

1. Check the **Form** under Facebook which is **active** on FB Ad. [Click here](https://business.facebook.com/latest/instant_forms/forms/)
2. Check the “**Settings**” of the form.
3. Go to the **field names**.

<figure><img src="/files/xHDPSUYnBe0z3KpoEAAS" alt="" width="563"><figcaption></figcaption></figure>

4. Check if there is any other **text** or **language** for the “Name” & “Phone Number” **question field**.
5. In this case you have to do the Facebook Integration with the “**Custom Contact field**” feature. (**Refer to the images of Scenario 3 > Point 4**).


---

# 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.neodove.com/admin-portal/integrations/facebook-integration/common-errors.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.
