Connect to Facebook Lead Ads on Zapier
Facebook Lead Ads uses OAuth to authenticate your account on Zapier.
- Log into Facebook Lead Ads to authenticate.
- Grant Zapier permission to access your account if prompted to.
Note- Due to changes in Facebook authentication, offers two versions of Zapier’s Facebook Lead Ads app: Facebook Lead Ads and Facebook Lead Ads (for Business Admins). These apps require different permissions based on your Facebook account. Learn more about the permissions needed to use Facebook Lead Ads to determine which app is right for you.
- If you’ve updated to a Meta Business Suite account, you’ll need to reconnect to any previously connected Facebook accounts in your Zapier account. Learn more about how to reconnect your account and prevent disruption to your Zaps.
About Facebook Lead Ads's app
| Are self-hosted or cloud-hosted accounts supported? | Cloud-hosted accounts only | |
| Is a paid Facebook Lead Ads plan required? | No | |
| Are any special account permissions required? | Yes |
You may need to contact the Page Owner or Business Manager admin to request those permissions. |
| Are there usage limits? | No | |
| Are there pagination limits? | No | |
| Do trigger samples use real data from your account or generic data? | Real trigger samples | If your newly created form has not received any submissions yet, you'll see generic data in the Zap editor. To test your Zap, create sample leads using the Facebook Lead Ads testing tool. |
| Are custom fields supported? | Yes | |
| Do update actions overwrite or append to existing data? | Not applicable | |
| Is there any additional info? | Yes |
Guidance on mapping fields: raw vs regular
When selecting fields to map data to your other apps, you will notice that there are two types of fields available: "raw" and "regular".
The difference between the two is how the data is processed:
- Raw fields: These are unformatted fields, meaning it’s the exact data provided by the Meta API.
- Regular fields: These are formatted fields, meaning they are structured and uniform making them easier to work with.
In this example, you can see there are two fields available to map for an email address.
Both types of fields are valid, and in some cases may be the same, depending on how the user inputted the data.
Zapier recommends using regular fields, to reduce formatting issues once the Zap is live.