Guide
GoHighLevel not getting your Facebook leads? Eight checks to run, in order
Short answer: First check that the lead exists in Meta at all. If it does, work through access and setup in this order: you are an admin of the Facebook Page, the form in Ads Manager is the form connected in GoHighLevel, its fields are mapped, LeadConnector has Leads Access in Meta, the connection hasn't expired, and the workflow trigger isn't filtered to a different page or form. Then test it.
Missing leads are the most expensive kind of bug, because you're paying for the ad and never see the person. I connect Facebook and Instagram lead forms to GoHighLevel as part of the build, so this is a list I know well. The steps below come from HighLevel's own troubleshooting guide and Meta's help pages, and I've kept HighLevel's names for its screens. HighLevel changes its screens often, so check the article if a menu has moved.
Check 1: Does Meta have the lead?
Start here, because it tells you which side the problem is on. Meta's help page on lead ads (opened 30 September 2026) says you can view your leads in the Meta Leads Center, or download them, or connect a CRM. If the lead is in Meta's Leads Center but not in GoHighLevel, the ad is fine and the connection is the problem. If it isn't in Meta either, look at the ad and the form, not the CRM.
Check 2: Are you an admin of the Facebook Page?
HighLevel's Facebook lead ad troubleshooting guide lists this first. The person who connects the integration must be an administrator of the Facebook Page running the ad. If it was set up by someone who has since lost that role, reconnect it with a current admin.
Check 3: Is it the same form in both places?
The guide says the lead form selected in Facebook Ads Manager has to match the one configured in the sub-account. It's easy to duplicate a form while editing an ad, so the ad now points to a new copy that the CRM has never seen.
Check 4: Are the form fields mapped?
In HighLevel, go to Settings, Integrations, Facebook form fields mapping and look for a blue checkmark next to your form. HighLevel says field mapping has to be in place beforehand, or lead data may not sync correctly. This is also where the sorting answers on your form land. On the US dealer build on our Work page, the budget, timeline and preapproval answers each map into their own CRM field, which is what lets the follow-up use them.
Check 5: Does the CRM have Leads Access in Meta?
Meta's page on leads access says that by default all Page admins and people with messaging permissions can download leads. But once someone with full control of the business portfolio starts customising who can access leads, new people, CRM systems or partners need to be added manually. HighLevel's guide gives the fix: in Meta Business Settings, go to Integrations, then Leads Access, then Assign CRMs, tick LeadConnector and click Assign. If someone tidied up the permissions recently, this is the likely cause.
Check 6: Has the connection expired?
HighLevel says the Facebook token can expire naturally, or when permissions are changed or removed. The fix is to disconnect and reconnect: in Settings, Integrations, click Connected under Facebook, then connect your Page again. The guide also says the person connecting needs Admin or Employee access in Business Manager and the Lead Access permission.
Check 7: Is the workflow trigger filtered to the right form?
If the contact arrives but nothing happens, look at the workflow. HighLevel's article on the Facebook Lead Form Submitted trigger says it has Page and Form filters. Only Pages connected in Settings, Integrations, Facebook appear in the dropdown, and one filter supports one form. With no filters, the workflow fires for every lead form submission across connected Pages, which can cause automations you didn't intend. For several forms, clone the trigger with a different filter, or use separate workflows.
This is the check that matters for follow-up. A lead that syncs but doesn't trigger the first reply is nearly as bad as a missing one, and the reason I care is in how fast you should reply to a new enquiry.
Check 8: Send a test lead
HighLevel's guide ends by recommending Meta's lead ads testing tool to test lead delivery and confirm the setup. Run a test after any change, then check the contact, the mapped fields and that the first reply went out. When several CRM integrations are attached to one Page, the guide also says to make sure LeadConnector is set as the primary receiver.
The eight checks on one page
| Symptom | Most likely check |
|---|---|
| Lead is in Meta, never in GoHighLevel | Checks 2, 5 and 6: admin role, Leads Access, expired connection |
| Some forms arrive and one doesn't | Checks 3 and 4: form match and field mapping |
| Contact arrives with empty fields | Check 4: field mapping |
| Contact arrives but no reply is sent | Check 7: the trigger's Page and Form filters |
| Everything worked, then stopped | Checks 5 and 6: someone changed permissions, or the token expired |
| Not sure which one it is | Check 8: send a test lead and follow it through |
How do you stop this happening again?
Test lead delivery on a schedule and after any change to the Page, the ad account or the permissions, not only when someone complains. If a run of leads was missed, download them from Meta and load them so nobody is left waiting. Then keep the return path too, so Meta learns which leads went further, which I cover in connecting Facebook lead ads to your CRM and back to Meta. And if the leads themselves are the problem, that's a different fix.
The connection is one part of the CRM and follow-up system I build for service businesses, which is described on the services page. If your customers are in Singapore, the setup is described on the GoHighLevel page for Singapore businesses.