Open Meta Business Suite, go to All tools, then Instant forms, and check the CRM setup tab for Agile CRM. If the CRM is listed there, connect it from the CRM side and new leads arrive without anyone downloading a file. If it is not listed, send the leads with middleware such as Zapier, LeadsBridge or Make, or with a webhook on the Graph API, and store Meta’s lead ID on every record either way.
The six ways a lead can leave an Instant Form
Meta documents six routes out of an Instant Form. Only the first one is manual, and manual is the one Meta itself calls not recommended.
| Route | Speed | Effort | What reaches you |
|---|---|---|---|
| Manual download | whenever someone downloads | nothing to set up, repeated by hand | lead ID, ad, ad set and campaign IDs, form ID, answers |
| Native CRM integration | automatic, Meta says real time | low, connect once from Business Suite | whatever the CRM maps, tracking parameters included |
| Middleware | automatic | low, no code, plus an account with the tool | the fields you map, lead ID included if you map it |
| Google Sheets or Excel | automatic | low | a row per lead with a lead ID and a status column |
| Webhooks with the Graph API | near real time, a few minutes | a developer, a Meta app, App Review, Business Verification | lead ID, ad ID, form ID, Page ID and time, then the answers |
| Graph API bulk read | on your schedule | a developer | the same fields, as fresh as your last run |
For Agile CRM the choice is usually between the second and the third rows, with the fifth as the route when you want the data on your own server.
Route one: the native integration, if Agile CRM is in the directory
- In Meta Business Suite, open All tools, then Instant forms.
- Select the CRM setup tab and search for your CRM.
- Click Connect from website and finish the steps on the CRM’s side.
Entries marked “through Zapier” connect through Zapier instead, so the badge tells you which engine runs underneath. Only admins of the Facebook Page with leads access permission can connect a CRM. If someone with full control of the business portfolio has customized leads access, assign the CRM there before the first lead arrives, or nothing will show up. An integration set up from the CRM’s own website cannot be edited or disconnected in Business Suite, and you manage it on the CRM side.
Before you rely on it, ask one question: does it store Meta’s lead ID? Not every integration does. Meta’s own table shows the Salesforce and HubSpot and Zoho integrations differ on exactly this point, and without the lead ID, sending stages back to Meta later loses its best match key.
Route two: middleware in front of Agile CRM
This is the route that works the same day, with no developer. The trigger is the Facebook Lead Ads form, the action is a contact or a lead in Agile CRM, and the work sits in the field mapping:
- The lead identifier, in a field you can search and export.
- The ad identifier, plus ad set and campaign identifiers if you report above ad level.
- The form name or identifier, which tells you which offer produced the lead.
- The creation time, taken from Meta rather than from the moment the tool ran.
- Each answer, mapped to the matching custom field rather than dropped into a note.
Send one test lead through the whole chain before you switch the campaign on. Open the record in Agile CRM, confirm the identifiers arrived, then send a second one and check that you did not create a duplicate contact. Middleware costs you a second account and a second set of field names, and every field added later has to be mapped in both places.
Route three: webhook and Graph API
The webhook gives you control and the closest thing to real time that Meta offers outside a native integration. A ping carries the lead ID, the ad ID, the form ID, the Facebook Page ID and the time, and the answers come from a separate Graph API read. Meta notes two limits: a rate limit per Facebook Page, and a token whose owner needs leads access. Building it requires a Meta app, App Review and Business Verification, so it is a project rather than an afternoon.
Where this route wins is when the lead has to touch your own system before the CRM: scoring, deduplication against an existing customer list, or a routing rule based on the ad that produced the lead.
What to store on every lead
Two identifiers carry the whole measurement:
- Meta’s lead ID, so your CRM can send pipeline stages back to Meta and the conversion leads goal has a key to match on.
- The ad ID, so you can join leads to spend and compute cost per lead per ad.
The second one is easy to lose with Instant Forms, because there is no URL and no click parameter to carry it. Get it from the lead record itself, and see how to track the Facebook ad ID in your CRM for the landing page version of the same problem. The wider set of routes, with the limits of each, is in Facebook lead ads CRM integration.
Why a download folder is not a route
Meta keeps leads downloadable for up to 90 days. After that the file is gone: pull the same March leads in July and you get zero rows, while the Results column still shows the count. The other traps in a manual export are the extras. Organic leads appear in the Business Suite file but not in Ads Manager, test leads appear as well, and neither counts in Results, which is why a download rarely matches the number in the ad set. Leads Center exports stop at contact fields, stage, source and owner, with a maximum of 10,000 leads per file.
Checklist before you go live
- Agile CRM connected, or the middleware Zap tested with a real submission.
- Lead ID stored in a named field, not in a note.
- Ad ID, form ID and creation time stored next to it.
- Answers mapped to fields your sales team actually filters on.
- One person responsible for checking the first day of leads arrived.
- The same test repeated after any change to the form, because a new form is a new source.
If you want a worked example of the middleware version, Facebook lead ads into Google Sheets and then Keap Max Classic walks through the same mapping decisions, and leads, CRMs and follow-up covers what happens after the record exists.