Send the leads to Keap Max Classic and treat Google Sheets as a record, not as the only road. A Google Sheets connection gives you a row per lead with its lead identifier and a status column, and a spreadsheet trigger then creates the contact in Keap. A direct connection from the lead ad form to Keap removes the middle step and is the better choice when nobody needs the sheet.
Which routes move a lead out of Meta
Meta lists six ways out of an Instant Form: manual download, a native CRM integration, middleware such as Zapier or LeadsBridge, a Google Sheets or Excel connection, webhooks with the Graph API, and Graph API bulk reads. Five of the six run unattended, which is the point, because a lead that waits for someone to download a file is a lead that goes cold.
| Route | Where it leaves you | Worth it when |
|---|---|---|
| Google Sheets connection | a row per lead, with lead identifier and status | a client wants a shared list or you need a record beyond Meta |
| Middleware straight to the CRM | a contact in Keap Max Classic, no sheet | one system, one mapping |
| Native CRM integration | contacts created by the CRM itself | your edition is listed in Meta’s directory |
| Webhooks or Graph API | full control of fields and timing | you have a developer and a Meta app |
The trade is the same in every case: each extra system is one more mapping to maintain, and one more place where a lead can sit unnoticed. Middleware and sheets both cost you a second account and a second set of field names.
Route one, with Google Sheets in the middle
- Connect the Instant Form to a spreadsheet. Meta’s own Sheets and Excel connection, or the Facebook Lead Ads trigger in your middleware, both produce a row per lead.
- Map the fields you cannot reconstruct later: the lead identifier, its creation time, the form, the ad identifier, the ad set and the campaign, then one column per question.
- Add a status column and fill it by hand or from your call notes. A row with no status is a lead nobody has claimed.
- Build the second step: when a new row appears, create or update the contact in Keap Max Classic, and put the form answers in the contact fields you will actually filter on.
- Store Meta’s lead identifier in a custom field on the contact, not only in the sheet, and keep the ad identifier beside it.
- Set a deduplication rule on email and phone before the first live lead, so a second submission updates the same contact instead of opening a twin.
The identifier is the part people skip. Meta’s guide to finding the lead identifier shows it arriving in the lead’s own id field over a webhook or the Graph API, in the id field of Zapier and LeadsBridge if you map it, in a Lead ID field in Make, and in the first column of a manual file. Without it you lose the one key that ties a contact back to the lead as Meta knows it, and any stage you later send back to Meta has to guess its match.
Route two, straight from the form to Keap
A direct connection is the same shape with one step removed, and it is usually the right call when the sheet exists only because nobody questioned it.
- In Meta Business Suite, open All tools, then Instant forms, and look for the CRM setup tab. Search for your CRM there before anything else, because a listing in Meta’s directory saves you the middleware.
- If your Keap edition is not listed, connect through middleware: the Facebook Lead Ads trigger, then an action that creates or updates the Keap contact.
- Keep the lead identifier and the ad identifier in the mapping, and test with one submission of your own before the campaign goes live.
- Note who owns the connection. A native integration set up from the CRM’s website cannot be edited or disconnected in Business Suite, so document where it lives.
- Turn the sheet on afterwards only if a client actually reads it.
Only admins of the Facebook Page with leads access can connect a CRM, and where someone with full control of the business portfolio has customized leads access, the CRM has to be assigned there before a lead arrives.
Why the spreadsheet is a record and not a CRM
A sheet accepts rows and stores a status, and that is the end of it. It does not merge duplicates, it does not fire a follow up, and it does not give anyone a queue. What it does well is survive: Meta keeps leads available for download for 90 days, and it recommends downloading often or using a CRM instead of treating the file as the archive.
Pair it with a follow up rule from the start. Whether the contact lives in Keap and the row in the sheet, or the other way round, someone has to be able to see which leads were called and which were not. Contact rate and qualification rate per creative are what tell you whether the leads were worth buying, and both need the follow up recorded somewhere queryable. Facebook lead quality sets out how to compute them, and the underlying mechanics of field mapping and permissions sit in Facebook lead ads CRM integration.
Keeping the ad attached to every contact
The lead identifier ties a contact to Meta. The ad identifier ties it to the creative and the campaign, which is the only way to compute a real cost per lead per ad once the data sits in a CRM. Two IDs on every contact, and the same two names in the sheet, make the numbers reconcile in a few minutes instead of an afternoon.
That is the practical reason to keep names consistent across campaigns, ad sets and ads, as covered in the lead gen account structure. When the ad identifier on the contact matches the naming you read in Ads Manager, a client asking which creative produced the calls gets an answer from the CRM rather than an estimate.
Sending outcomes back to Meta
If the campaign optimizes for conversion leads rather than raw leads, Meta needs to hear what happened afterwards, and the lead identifier is the key that makes the match reliable. That means the CRM is not only a destination but part of the optimization loop: a stage change has to leave Keap and reach Meta as an event.
Two things break that loop quietly. An integration that never stored the identifier cannot send it back, and a stage that exists in the sheet but not on the contact never reaches Meta at all. Decide on three or four stages that matter, map them once, and check monthly that events still arrive.
Checklist before the campaign goes live
- Does Meta’s directory list your Keap edition, or does the route need middleware?
- Does every lead carry Meta’s lead identifier and the ad identifier?
- Is the duplicate rule on email and phone set before the first live lead?
- Does a client actually read the spreadsheet, or does it only add a step?
- Do leads keep arriving after the time Meta stops serving them?
- Is the stage change mapped from Keap back to Meta, and verified?