How to Connect Facebook Lead Ads to Your CRM

Facebook lead ads are the cheapest leads most businesses ever buy, and the ones most often left sitting in a spreadsheet for two days. The form is easy. Getting each lead into your CRM the moment it arrives, with the campaign it came from, is where most setups break.

This guide covers every way to connect Meta lead ads (instant forms) to a CRM, what actually happens behind each one, how to test it without spending on ads, and how to fix the errors that stop leads arriving.

If your connection already exists and leads have stopped showing up, go straight to Facebook lead ads not syncing to your CRM.

The short answer

Method	Best for	Speed	What you need
Your CRM's built-in Meta connection	Most businesses	Seconds	A CRM that supports Meta lead ads, admin access to the Facebook Page
Zapier or Make	CRMs with no Meta connection	Seconds to minutes	A paid Zapier plan (lead ads is a premium trigger) or a Make account
Webhook and Graph API (custom build)	Developers building their own system	Seconds	A Meta app with lead permissions that has passed App Review
Manual CSV download	Testing, very low volume	Whenever you remember	Nothing, but leads expire after 90 days

Whatever you choose, three things decide whether it works: the Page must be connected by someone with the right role, the CRM must be allowed in Lead Access, and every lead must carry the campaign, ad set, ad and form it came from.

How leads get from Meta to your CRM

It helps to know what happens under the hood, because almost every error traces back to one of these steps.

Someone submits your instant form.
Meta sends a notification (a "leadgen" webhook) to every app subscribed to that Page. The notification doesn't contain the answers. It only carries IDs: the lead ID, the form ID, the ad ID, the ad set ID, the Page ID and the time.
The receiving app calls Meta's Graph API with that lead ID and gets the actual answers (name, email, phone and any custom questions).
The app creates or updates the contact in your CRM.

Step 3 is why permissions matter so much. The notification can arrive fine while the request for the answers is refused, and from the outside it just looks like "leads aren't coming through".

Method 1: your CRM's built-in connection

Most CRMs that sell to businesses running Meta ads have a native connection. The flow is nearly always the same:

In your CRM, open its integrations and choose Facebook or Meta lead ads.
Log in with a Facebook profile that is an admin of the Page running the ads, or has advertiser-level access to it.
Pick the Page, then the forms you want to sync. Many tools also let you sync all current and future forms.
Map the form fields to CRM fields: full name or first and last name, email, phone, and each custom question.
Choose where new leads land: which pipeline, which stage, which owner.
Send a test lead (see "Test it without spending on ads" below).

What to check before you rely on it:

Does it save the campaign, ad set, ad and form on each lead? Without them, every Facebook lead in your CRM has the same source and you can't tell which ad works.
Does it catch up on leads it missed, for example after a token expired? If not, gaps will happen silently.
Can it trigger an automation instantly (a text, an email, an assignment)? Speed is most of the value.

Method 2: Zapier or Make

If your CRM has no Meta connection, a middleware tool can bridge it.

Zapier:

Create a Zap with Facebook Lead Ads, New Lead as the trigger. It's a premium trigger, so it needs a paid plan.
Connect a Facebook account that is an admin of the Page.
Choose the Page and the form.
Test the trigger. Zapier needs at least one lead on that form to pull sample data, so create a test lead first.
Add the action, for example "Create contact" in your CRM, and map each field.
Turn the Zap on. You need one Zap per form unless you build it to handle several.

Make has an equivalent Facebook Lead Ads module and works the same way.

The catch: middleware only captures leads from the moment it's switched on. Older leads have to be exported and imported by hand. And it's one more thing whose login can expire.

Method 3: build it yourself with the webhook

For developers. The outline:

Create a Meta app and add the lead ads use case. Without that use case, the lead permission doesn't even appear in the token tools.
Request the permissions: leads_retrieval, pages_manage_metadata, pages_show_list, pages_read_engagement and ads_management.
Subscribe your app to the Page's leadgen field with a Page access token from someone who can advertise on that Page: POST /{page-id}/subscribed_apps?subscribed_fields=leadgen.
Set up an HTTPS endpoint that receives the webhook and verifies it.
On each notification, call GET /{leadgen-id}?fields=created_time,ad_id,form_id,field_data with a Page access token to read the answers.
Submit the app for App Review. Until it's approved and live, it can only read leads from people who have a role on the app, which is fine for testing and useless for real ads.

Common developer errors:

"This method must be called with a Page Access Token" (#190): you used a user or system user token. Exchange it for the Page's own token first.
Webhooks never arrive: the Page isn't subscribed, or the subscription was removed when someone reconnected the Page.
Leads stop after a few weeks: a token expired or was invalidated by a password change or a role change.

Method 4: download the leads

You can download leads as a CSV or Excel file from three places:

Ads Manager: on the lead ad, click the leads count in the Results column and download.
Instant forms: in Meta Business Suite, open your forms, choose the form and download new leads or a date range.
Leads Center: in Meta Business Suite, the leads list can be exported. Each export is limited to 10,000 leads.

Leads are only available for 90 days after each person submits the form. After that Meta deletes them and there's no way to recover them, not through support and not through the API. If you're downloading by hand, put it in the calendar.

Lead Access: the permission that breaks most setups

Meta has a separate control that decides which people and which apps can read the leads of a Page. It lives in Business Settings, Integrations, Lead Access (the label has varied over time).

How it behaves:

By default, any Page admin and the apps they connect can read leads.
The moment anyone customises the list, the Page switches to restricted mode. From then on, only the people and CRMs on the list can read leads, even existing Page admins who aren't on it.
If your CRM isn't on a customised list, the lead notification still arrives but the request for the answers is refused. The testing tool shows this as "CRM access has been revoked" (error 103).

To fix it: go to Lead Access, choose the Page, open the CRM tab, and add or re-enable your CRM. If the CRM doesn't appear in the list, the person connecting it doesn't have enough access to the Page. There's also a "Restore default access" option that removes all customisation; use it carefully, because it's a reset for everyone.

Test it without spending on ads

Meta has a free Lead Ads Testing Tool at developers.facebook.com/tools/lead-ads-testing.

Pick the Page and the form.
Click Create lead to send placeholder answers, or Preview form to fill it in yourself.
Click Track status to see whether each subscribed app received the lead, and any error code.

Things to know:

You need an advertiser or admin role on the Page.
Each form can only have one test lead at a time. Delete it before creating another.
Error 103 means Lead Access is blocking the CRM. Error 190 usually means the CRM's token expired and it needs reconnecting.

Set the form up so it maps cleanly

A lot of messy CRM data starts with the form.

Choose the right form type:

Form type	What it does	Use it when
More volume	Short, prefilled from the person's profile, submits in one tap	You want the most leads and will qualify them fast
Higher intent	Adds a review screen where the person confirms their details. Mobile feeds only	Lead quality matters more than volume
Rich creative	Adds images, colours and a mandatory intro	Brand matters, or you need to explain the offer

Build it with the CRM in mind:

An instant form can have up to 15 questions and must include a privacy policy link, or Meta won't publish it.
Use Meta's standard fields (full name, email, phone) rather than custom questions for contact details, so they map automatically.
Name custom questions the same way across forms, for example always "Budget" not "Budget?" in one form and "Monthly budget" in another. Every variation is another field to map.
Use multiple-choice answers for anything you'll want to filter or route on, such as service or budget band. Free text is hard to automate.
Conditional logic can screen people out inside the form, but disqualified people don't count as leads, which can raise your cost per lead.

What to do in the first five minutes

Getting the lead into the CRM is half the job. The other half is what happens next. The often-quoted "respond within five minutes and you're 100 times more likely to reach them" comes from a 2007 study of one vendor's sales data, and it measured how often leads were contacted, not how often they bought. It's directionally right: leads cool fast. But treat the exact multiplier with care.

What works in practice:

Send an instant confirmation by text or email that names the offer they asked about.
Assign an owner automatically based on location, service or round robin.
Call or message within minutes during business hours.
Follow up more than once. Many lead ad leads don't answer the first attempt.
Record the outcome in the CRM. Qualified, booked, won, lost. This is what tells you which ads bring real customers, and it's what Meta needs if you want to try conversion leads.

Connecting Meta lead ads to Inflowave

Inflowave receives Meta lead form submissions in real time through Meta's leadgen webhook, then fetches the answers and creates the lead.

Attribution is saved on every lead: the campaign, ad set, ad and form it came from, tagged with facebook as the source and paid as the medium. You can report on cost and results per ad without spreadsheets.
Name, email and phone map automatically. All other answers are kept with the lead and are available to workflows.
Missed leads are caught up. A background job checks every 12 hours for submissions that didn't arrive, for example during a token problem.
Workflows can start the moment a lead arrives, using the "Facebook lead form submitted" trigger. It carries the form ID and all the answers, so you can route by form or by answer, send a WhatsApp, SMS or email, and assign an owner.
The Meta lead ID is stored with each submission.

New lead ad leads arrive in the New stage. To send leads from different forms to different pipelines or owners, use a workflow on the form submitted trigger.

Questions people ask

How do I connect Facebook lead ads to my CRM?

Use your CRM's built-in Meta lead ads connection if it has one: log in with a Facebook profile that is an admin of the Page, choose the Page and forms, map the fields, and send a test lead with Meta's Lead Ads Testing Tool. If your CRM has no connection, use Zapier or Make.

How long are Facebook leads available to download?

90 days from the moment each person submits the form. After that, Meta deletes them permanently. The clock runs per lead, not per form or campaign.

Why aren't my Facebook leads showing up in my CRM?

The usual causes are an expired connection that needs reconnecting, the CRM missing from the Page's Lead Access list, the Page no longer subscribed to lead notifications, or the wrong Page or form selected in the integration. Meta's Lead Ads Testing Tool shows which one it is.

What does "CRM access has been revoked" mean?

Someone customised the Page's Lead Access list and your CRM isn't on it. Add it back under Business Settings, Integrations, Lead Access, then send a test lead.

Do I need a developer to connect Facebook lead ads?

No, if your CRM has a Meta lead ads connection or you use Zapier or Make. You only need a developer for a fully custom integration built on the webhook and Graph API.

Is the Facebook lead ads Zapier integration free?

No. Facebook Lead Ads is a premium trigger in Zapier, so it needs a paid plan.

Can I get old Facebook leads into my CRM?

Only those submitted in the last 90 days, by downloading them as a CSV and importing. Most connections, including Zapier, only capture leads submitted after they were switched on.

How do I test Facebook lead ads without running ads?

Use Meta's Lead Ads Testing Tool at developers.facebook.com/tools/lead-ads-testing. Create a test lead on your form and use Track status to confirm your CRM received it.

Does the webhook include the lead's answers?

No. Meta's lead notification only contains IDs. Your app has to request the answers from the Graph API with the lead ID.

Should I use More volume or Higher intent forms?

More volume if you can qualify leads quickly by phone or message. Higher intent if you're getting too many leads who don't answer, since the extra confirmation screen filters out accidental submissions. Higher intent forms only show on mobile feeds.

Does Meta have its own CRM?

Leads Center in Meta Business Suite is a basic lead list where you can set statuses and download leads. It only holds Facebook and Instagram leads, so most businesses connect a proper CRM to see every channel together.

How to Connect Facebook Lead Ads to Your CRM (Every Method, Tested)