---
url: https://docs.corbitaltech.dev/products/fblead-addon-for-whatsmarks-saas/faq.md
description: >-
  Frequently asked questions and troubleshooting for the Facebook Leads
  Integration & Sync Addon for WhatsMark SaaS. Fix lead sync failures, Meta
  permissions errors, FB Page connection, and template message delivery issues.
---

# Frequently Asked Questions

Find answers to the most commonly asked questions about the Facebook Leads Integration & Sync Addon for WhatsMarkSaaS.

## 📦 Installation & Setup

### Q: What are the system requirements for Facebook Leads Integration & Sync Addon?

**A:** The Facebook Leads Integration & Sync Addon requires:

* WhatsMarkSaaS (Latest Version)
* PHP 8.0 or higher
* MySQL 8.0 or higher (MySQL 8.\* minimum required)
* Facebook Business Account with Lead Ads access
* WhatsApp Business API configured
* Composer for dependency management

### Q: How do I install the Facebook Leads Integration & Sync Addon?

**A:** Follow our detailed [Installation Guide](/products/fblead-addon-for-whatsmarks-saas/installation.md) for step-by-step instructions.

### Q: Can I install this addon on multiple domains?

**A:** The license is typically for one domain. For multiple domains, you'll need to purchase additional licenses. Check the license terms on CodeCanyon for specific details.

## 🔧 Configuration & Integration

### Q: How do I connect my Facebook Lead Ads?

**A:** You need to:

1. Create a Facebook App in Facebook Developers
2. Add Lead Ads product to your app
3. Configure the app credentials in Facebook Leads Integration & Sync Addon settings
4. Set up webhooks for real-time lead sync

Detailed steps are available in our [Facebook Integration Guide](/products/fblead-addon-for-whatsmarks-saas/facebook-integration.md).

### Q: What Facebook permissions do I need?

**A:** The addon requires these Facebook permissions:

* `leads_retrieval` - To access lead data
* `pages_read_engagement` - To read page engagement
* `pages_manage_metadata` - To manage page metadata
* `business_management` - For business account access

### Q: Can I use multiple Facebook ad accounts?

**A:** Yes, the Facebook Leads Integration & Sync Addon supports multiple Facebook ad accounts. You can configure multiple accounts in the settings and manage leads from all of them in one dashboard.

## 💬 WhatsApp Integration

### Q: Do I need WhatsApp Business API for this addon?

**A:** Yes, you need WhatsApp Business API access. The addon doesn't work with regular WhatsApp or WhatsApp Business app. It requires the official WhatsApp Business API.

### Q: Can I customize the WhatsApp message templates?

**A:** Absolutely! The addon provides a template management system where you can:

* Create custom message templates
* Use variables like {{name}}, {{email}}, etc.
* Create different templates for different scenarios
* Support multiple languages

### Q: How quickly are WhatsApp messages sent after lead capture?

**A:** Messages can be sent immediately upon lead capture or with custom delays. You can configure:

* Immediate sending (within seconds)
* Scheduled delays (minutes, hours, days)
* Business hours restrictions
* Custom automation sequences

## 📊 Lead Management

### Q: How are leads synchronized from Facebook?

**A:** Leads are synchronized in real-time using Facebook webhooks. When someone submits a lead form, Facebook sends the data immediately to your system, typically within 1-2 seconds.

### Q: Can I import existing Facebook leads?

**A:** Yes, the addon provides an import feature to bulk import existing leads from your Facebook ad accounts. This is useful when setting up the addon for existing campaigns.

### Q: What lead data is captured?

**A:** The addon captures all data from Facebook lead forms including:

* Standard fields (name, email, phone)
* Custom questions from your lead forms
* Campaign and ad set information
* Lead source and timestamp
* Facebook lead ID for tracking

**Important Note**: We do not provide support for Meta/Facebook permission approval processes. All Meta-related configurations and approvals must be handled directly with Meta.