Facebook Lead Ads in 2026: Setup, Form Types and CRM Sync

Facebook lead ads quietly changed jobs in 2026. The form part still works the way it has for years: someone taps your ad, a prefilled instant form opens inside Facebook or Instagram, and you get a name, an email and a phone number without them ever loading your site. What changed is the other end. Meta's About Performance Goals for Lead Ads page now opens with this: "Beginning April 2026, the qualified leads performance goal is no longer available for new campaign creation without Conversions API integration. Existing campaigns will be impacted beginning August 2026."

That turns "CRM sync" from a one-way pipe into a loop. Leads still have to get out of Meta and into your CRM fast, before they go cold and before Meta deletes them at 90 days. Now, if you want Meta to optimize for leads that actually turn into customers, your CRM also has to send each lead's stage changes back to Meta through the Conversions API for CRM. Most of the guides ranking for "facebook lead ads" were written before that change. They still describe a "Lead Generation" objective and stop at "connect a CRM."

Last verified: 2026-10-23. On that date we read Meta's Business Help Center articles on lead ads, form types, custom questions, conditional logic, SMS verification, organic leads, lead downloads, Leads Center, leads access, performance goals and CRM setup. We also read Meta's developer guides for creating lead forms, retrieving leads, webhooks, testing, and the full Conversions API for CRM integration, plus HubSpot's knowledge base articles on lead syncing and Meta conversion events. Every platform rule below links to the page it comes from.

What we did and didn't do. We built two original references from those docs: a matrix of every lead-quality filter Meta offers, with where it lives and what it costs you in reach, and a CRM sync check you can run before launch. We also charted Meta's published timeline for the Conversions API for CRM, including a place where two Meta pages disagree. We did not run a live lead campaign for this post, and it contains no cost-per-lead results of our own. For published cost-per-lead benchmarks, see our breakdown of how much Facebook ads cost in 2026. For the pre-launch basics that apply to every campaign, use the Facebook ads checklist.

1. What Facebook lead ads are in 2026

Meta's About Lead Ads page describes lead ads as ads "designed to help you find people who may be interested in your products or services and collect information from them." It lists three kinds:

This guide covers the first one, which is what most people mean by "Facebook lead ads." For AI agents that answer messaging leads, see our Meta Business Agent guide.

A few basics from Meta's docs that shape everything else:

• Placements. Meta says lead ads "can appear in Facebook Feed and Stories, Instagram Feed and Stories, in-stream reels, Marketplace and more." Some form features narrow this, as section 4 shows.
• Where you build them. You can create lead ads in Meta Ads Manager or Meta Business Suite, or as an Advantage+ leads campaign from Ads Manager. Meta's SMS verification article notes that when you pick the Leads objective in Ads Manager, you now start with an Advantage+ leads campaign by default.
• Who owns the lead. Meta's Lead Ads developer guide says "All leads generated via a lead ad belong to the Facebook Page." That includes leads from Instagram placements. This is why every CRM integration starts with Page access, not ad account access.
• How long Meta keeps them. Meta's download article says "Lead information is only available on Meta for 90 days, so older leads cannot be downloaded." Meta recommends downloading regularly.
• Saved-form limit. Meta's instant form creation article says you can only save up to 100 instant forms in Ads Manager. Once you pass 100, only the most recent 100 are kept.

2. What changed in 2026

The table below is the short version of what's different from the guides you'll find on page one of Google.

Meta also publishes its own performance claim for the qualified-leads route. The same performance goals page says lead ads that used the Conversions API for CRM and the qualified leads goal on instant forms "saw 21% lower cost per quality leads" than ads that used Maximize number of leads. Meta gives no sample, time period or methodology, so treat it as Meta's marketing claim, not a benchmark you can plan against.

3. Before you build: what you need

Get these in place first. Each one blocks either the launch or the lead download if it's missing.

Housing, employment and credit. Meta's About Lead Ads page adds a restriction that catches a lot of advertisers. If you use lead ads for housing, employment, or financial products and services in the US, or targeted to the US or Canada, you may not collect certain information. That includes age, gender, marital or relationship status, and location details such as street address, city and ZIP or postal code. Custom questions may ask about location preferences, but they may not mimic the prohibited prefill questions. If you're running real estate campaigns, our real estate Facebook ads guide covers the housing special ad category in full.

4. How to set up a Facebook lead ad in Ads Manager

This follows Meta's Create a Lead Ad with Instant Form article and its SMS verification walkthrough as of 2026-10-23. The steps are flat on purpose. Do them in order.

1. In Ads Manager, click + Create, choose Leads as the objective, and continue. You'll start in an Advantage+ leads campaign.
2. At the ad set level, in the Conversion section, select Instant forms as the conversion location.
3. Under Performance goal, keep the default or pick a different goal. Choose Maximize number of qualified leads only if your CRM is (or will be) connected through the Conversions API for CRM. Section 9 explains why.
4. Set budget, schedule, audience and placements as you would for any campaign. Our Meta ads account structure guide covers how many campaigns and ad sets to run.
5. At the ad level, build the creative and pick a call to action that matches the offer.
6. In the Destination section, click Create form, or select an existing form.
7. Pick a Form type: More volume, Higher intent or Rich creative. Section 5 compares them.
8. In Intro, optionally add a background image, a greeting headline and a description. The intro is mandatory for Rich creative forms.
9. In Questions, add up to 15 custom questions (multiple choice, short answer, conditional, appointment request, store locator), turn on conditional logic if you need it, explain how you'll use the information, and choose the contact fields to prefill.
10. In Privacy policy, add your URL and link text. Add a custom disclaimer if you need marketing opt-ins or legal notices.
11. In Ending, write a headline, a description, a link and call-to-action text that tell people what happens next. Optionally turn on Start conversations on Messenger.
12. Back in Destination, optionally check Require SMS verification to submit form. It's grayed out unless phone number is a required contact field.
13. If you haven't connected a CRM, Meta offers a Set up prompt here. Don't skip it if you plan to optimize for qualified leads.
14. Submit a test lead (section 10) before you publish. Then click Publish.

One thing that trips people up: Meta's conditional logic article says the feature "is only available through lead ad with instant form creation in Meta Ads Manager." If you build forms through a third-party tool or the Marketing API, check whether conditional logic survives. Meta's developer lead form guide documents question types, a higher-intent flag and an organic-lead filter, but not the Ads Manager logic builder that closes the form for non-leads.

5. The three instant form types

Meta's About Instant Form Types page is short, and it's the most important page in this guide. Here's what it says, side by side.

Soku's read (editorial): if a human has to phone the lead, start with Higher intent. The review screen costs you some volume, but More volume forms are built to minimize friction, and a form that takes two taps to submit is also a form that gets submitted by accident. Rich creative is the right call when the ad can't carry the explanation on its own, such as a multi-step service or a program with several tiers. Keep in mind its delivery is narrower than the other two.

6. Lead-quality filters: the matrix

This is the original element of this post. Meta gives you about a dozen ways to raise lead quality, spread across five help articles and two developer guides. None of them is free: each one costs you volume, reach, or setup time. We put them in one table, with where each one lives and what it costs, all sourced to Meta's own pages.

Three things stand out when you read the rows together.

Most quality filters shrink where your ad can run. Higher intent, SMS verification and Rich creative each come with a mobile-only delivery note. That's usually fine, since instant forms are built for mobile, but expect less delivery on some surfaces.

Conditional logic is the only filter that refuses a lead. Every other filter makes submitting harder. Conditional logic can close the form on someone who answers "just browsing" or picks a budget below your floor, and you won't receive their information at all. Test it carefully, and give the Close form ending something useful, such as a self-serve link.

The cheapest filter is the one you already have. Restricted sharing is the default. If someone on your team switched a form to Open to "get more leads," those extra leads come from people outside your targeting, and they don't show up in Ads Manager results, which makes your cost per lead look better than your CRM says it is.

Which filters to stack, by offer

7. Writing the form itself

Meta's best practices and custom questions pages are more specific than most third-party guides:

• Keep it short. "Ask as few questions as possible to make it easier for people to submit your form." You can include up to 15 questions in total.
• Prefer prefill. Prefill questions take information from a person's Facebook or Instagram profile. People can still edit prefilled answers.
• Use ranges in multiple choice. Meta's own example: instead of offering 2001, 2002, 2003 and 2004 as four options, offer "2001–2004" as one.

One more practical note. If you plan to sync leads to a CRM, name your custom questions with the CRM in mind. HubSpot, for example, turns each custom Facebook field into a property named after the field label. Its field mapping article says "How did you hear about us?" becomes how_did_you_hear_about_us. It also says form fields "that do not contain any English characters will not be synced to HubSpot." A Japanese-only or Arabic-only question label can silently drop answers.

Photo: Vitaly Gariev on Unsplash.

8. Getting leads out of Meta

There are seven ways to get leads out, and they differ in speed, fields and limits. This is the table we wish Meta published.

Details from Meta's developer docs that matter even if you never write code:

• Webhooks aren't instant. Meta's retrieving guide says that on success, "real-time pings occur on events with a delay of up to a few minutes." The webhook only carries IDs. Your system still has to fetch the answers.
• A form can have more leads than its ad. Leads exist on both the ad and the form. "Because a form can be re-used for many ads, your form could contain far more leads than an ad using it." Reconcile by form when you count.

Whatever route you choose, don't treat Meta as storage. A lead you forgot to export in July is gone by October.

9. CRM sync, both directions

Direction one: leads into your CRM

Meta's developer guide on connecting your CRM to download leads ranks the options: partner integrations if your CRM is supported, a custom webhooks integration if it isn't or you want more control, Graph API bulk read, and manual download as a last resort that is "not recommended." It adds one instruction for every method: "ensure that the 15–17 digit Meta Lead ID is included in the downloaded data."

That lead ID requirement is the part most teams miss, and it decides whether direction two works later.

Worked example: HubSpot

HubSpot is a common pairing and it's one of the Conversions API for CRM partners Meta lists on its CRM connection page. HubSpot handles both directions itself:

HubSpot's Facebook lead ads FAQ lists the permissions the connecting user needs: Ads Publish permission in HubSpot, admin access on the Facebook ad account, admin access on the Page, and Lead Access on the Page. Its troubleshooting article adds that the ad account and the Page must be owned by the same Business Manager, and that HubSpot must be selected as the connected CRM in the Page's CRM setup.

Two HubSpot details change the setup:

• Create a conversion event for every lifecycle stage. HubSpot says "you must create a conversion event for each lifecycle stage in HubSpot, including Others." Meta needs several stages to learn, not just "Customer."
• Install the Meta pixel only once. HubSpot recommends installing the pixel only through HubSpot and removing any manually added pixel code. Otherwise, it warns, you can get "duplicate events and inconsistent data."

On the Soku side: our HubSpot integration page explains what HubSpot itself offers. Section 12 of this post is the precise list of what Soku does with HubSpot today.

Direction two: lead quality back to Meta

This is the Conversions API for CRM, and it's what the qualified leads goal now depends on. Meta's developer docs and HubSpot still call that goal "Conversion Leads"; Ads Manager calls it Maximize number of qualified leads. They're the same thing. Meta's overview calls it "a separate integration from your current Conversions API setup because the required parameters are different and the data comes from your CRM system rather than your web servers." If you already send website events, this doesn't replace them. Our Meta Pixel and Conversions API integration page covers the website side.

Is your business a good fit? Meta's guidelines, from the overview and FAQ:

The 1% to 40% rule matters more than it looks. If you optimize for "Closed won" and only 0.5% of leads close, Meta's guideline says that stage is too rare to learn from. Pick an earlier stage, such as "Qualified" or "Meeting booked," that lands inside the band. Meta's funnel configuration page says the system "optimizes for all down-funnel stages as well," and may optimize for a different stage than the one you picked if that performs better.

The payload. Meta's payload specification requires event_name (your free-form stage name), event_time, action_source set to system_generated, user_data with at least one customer parameter, and two custom_data fields: lead_event_source (the name of your CRM) and event_source set to crm. Meta's example looks like this:

{
  "event_name": "Marketing Qualified Lead",
  "event_time": 1761945743,
  "user_data": {
    "lead_id": 1234567890123456
  },
  "action_source": "system_generated",
  "custom_data": {
    "lead_event_source": "HubSpot",
    "event_source": "crm"
  }
}

The rules that break most integrations, all from Meta's FAQ and developer implementation page:

• Send every stage, including the raw lead. "If a lead reaches the final 'Converted' stage, then all previous stages should have been sent beforehand."
• Keep event_time after the lead time. Otherwise "your events may be discarded." You can backfill up to 7 days.
• Batch carefully. Each batch can include up to 1,000 events, and "if there is an error in the batch, the whole batch will be discarded." Use small batches with retries.
• Use a valid lead ID or none. An invalid lead_id gets the event rejected. Email and phone must be hashed.
• Don't reuse a web payload. Meta says a web-format payload "would be accepted by the Conversions API and appear in Events Manager, but it will not be recognized for this integration."
• Never switch Pixels. "Changing Pixels will start a new integration and restart the training process."

How long it takes. Meta publishes a step-by-step timeline. Two of its own pages disagree about the last step: the overview's table says the learning phase takes 2–4 weeks, while the FAQ says that after funnel analysis "there is a training period of 1-2 months before your integration is added to the production model." We charted both.

In practice: with a partner such as HubSpot you can be sending events within a day. Building it yourself means about a month of engineering. Either way, allow one to two months before the qualified leads goal performs the way Meta describes. You can run campaigns on it during training, but Meta says you "will not benefit from the full performance lift until the training period is complete."

10. The CRM sync check

This is the second original element: a pre-launch check that covers both directions. Meta's tools are good, but they're scattered across the developer site, Events Manager and Business Suite. Run these in order, and don't spend real budget until the first eight pass.

Two warnings about the testing tool, from Meta's testing page: you can only have one test lead per form at a time, so delete it before you create another, and test leads are "organic leads that are not associated with any ad." So a test lead proves your pipe works. It doesn't prove ad IDs or campaign names will arrive, so check those again on the first real lead.

And one about SMS verification: when it's on, Meta adds a phone_number_verified column to downloaded leads, but its SMS article warns that "when you retrieve the leads data via your CRM integration, you may not see the new column." Don't build CRM routing rules on a field your integration may never receive.

11. Common problems and fixes

12. Where Soku fits, and what it can't do

Soku is an AI agent that connects to your ad accounts. Here is exactly what it does with Meta lead ads today, checked against our code on 2026-10-23.

What Soku can do:

• List and read instant forms. Soku lists the forms on a Facebook Page (name, status, questions, privacy policy, ending page, locale) and reads one form by ID after checking it belongs to the Page you named. These are read-only.
• Read leads. Soku reads the leads a form or an ad collected, including each lead's field_data, ad ID, form ID and platform. If you give it an ad ID whose direct read fails, it finds the form behind the ad and reads from that instead. This is an on-demand pull when you ask, using the Page token from your Meta connection with the leads_retrieval permission.
• Draft a new form. Soku can create an instant form on a Page with your questions, privacy policy, follow-up URL, optional context card and thank-you page, and the Higher intent setting (is_optimized_for_quality). The create call waits on a review card until you approve it.
• Archive a form. Meta has no form delete. Soku can archive a form, which also needs your approval. Leads already collected stay readable.
• Check a lead ad before it goes out. When Soku creates a lead ad, it first checks that the ad set uses the On-ad destination and the Lead generation goal, that the campaign uses the Leads objective, and that the form is active and belongs to the Page.
• Send a single Conversions API event. Soku can draft one server event, including one with the system_generated action source, and send it after you approve it. It rejects unhashed email, phone and other personal fields.
• Work with HubSpot on request. HubSpot is one of the apps you can connect to Soku through Composio-managed OAuth. The agent can read HubSpot records and, after you approve each change on a review card, write records such as a contact you ask it to create from a lead.

What Soku can't do today:

• No always-on CRM sync. Soku doesn't subscribe to the leadgen webhook. It doesn't push every new lead into HubSpot or any other CRM in the background. Use HubSpot's own lead syncing, a Meta CRM partner, or a webhook integration for that.
• No Conversions API for CRM pipeline. Soku doesn't upload daily stage changes, track lead coverage or manage the CRM dataset. One approved event isn't an integration.
• No Qualified leads ad sets. Soku's lead ad check only accepts the Lead generation goal, so it can't launch an ad set on the Qualified leads goal (QUALITY_LEAD in the API) today.
• No conditional logic, SMS verification or organic-lead filter. Conditional logic is Ads Manager only. Soku's form creation doesn't pass the SMS or Restricted-sharing settings, so set those in Ads Manager.
• No incremental lead reads. Soku reads leads in pages but doesn't filter by time, so it can't fetch only "leads since yesterday." It also doesn't return the organic-lead flag.
• Nothing older than 90 days. Soku reads through Meta's API, so it sees what Meta still holds.

On our HubSpot integration page: it describes what HubSpot itself offers, such as attribution, audience sync and lead scoring. The list above is the precise scope of what Soku does with HubSpot.

If you run lead ads for real estate, our real estate video ads use case walks through video creative for Meta lead campaigns. For how an agent fits into day-to-day Meta work more broadly, see the Facebook ads AI agent guide.

The short version

• Pick the performance goal first. If you want Meta to optimize for qualified leads, the Conversions API for CRM has been mandatory for new campaigns since April 2026, and existing campaigns are affected from August 2026.
• Pick the form type for the follow-up, not the volume. If a person has to call the lead, start with Higher intent.
• Add quality filters on purpose. Each one costs volume or reach. Conditional logic is the only one that actually refuses a lead.
• Get leads out within days. Meta deletes them after 90.
• Store the Meta lead ID on every CRM record. It's the best match key for sending stages back.
• Send every stage, daily, including the raw lead, and aim for at least 60% lead coverage.
• Run the 12-step sync check before you spend.