Solution guide · GoHighLevel

Facebook leads not syncing to GoHighLevel: why it happens and how to fix it

Facebook leads not syncing to GoHighLevel? Fix lead access, form mapping, expired connections and workflow filters step by step, then recover missed leads.

Facebook leads not syncing to GoHighLevel: why it happens and how to fix it — guide thumbnail

Key takeaways

  • When Facebook leads stop syncing to GoHighLevel, the leads still exist in Meta; one link in the chain — permissions, leads access, form mapping or the workflow trigger — has broken.
  • The most common fix is in Meta Business Settings: Integrations → Leads access → your Page → CRMs → Assign CRMs → LeadConnector.
  • In HighLevel, every lead form must be mapped and set to Active under Settings → Integrations → Facebook Form Field Mapping, or its leads are never collected.
  • Meta’s Lead Ads Testing Tool shows within seconds whether LeadConnector received a test lead, so you know which side is broken before changing anything.
  • After the fix, use HighLevel’s Troubleshoot → Sync Leads option to pull in the leads you missed; Meta only keeps lead data for 90 days.

When Facebook leads stop syncing to GoHighLevel, the leads are not lost. Meta still records every Instant Form submission; one link between Meta and HighLevel has broken — usually LeadConnector’s leads access, an expired connection, or a form that is not mapped as active. Fix that link, then use HighLevel’s Sync Leads option to pull the missed leads back in.

In this guide I show you how to find the broken link in two minutes with a test lead, then fix each of the six causes I see when I audit ad accounts, with the exact menu paths and settings. It is the same checklist I run when I connect lead ads as part of a GoHighLevel CRM setup.

How a Facebook lead reaches GoHighLevel

Every lead passes through four links, and all four have to hold:

  1. Meta records the lead when someone submits your Instant Form on Facebook or Instagram.
  2. Meta notifies LeadConnector (HighLevel’s Meta app) — but only if LeadConnector has leads access to that Page.
  3. HighLevel creates the contact — but only if the form is mapped and set to Active in the sub-account.
  4. A workflow runs on the Facebook Lead Form Submitted trigger and texts, emails or assigns the lead.

If the lead appears in Meta but not in HighLevel, links 2 or 3 are broken. If the contact appears in HighLevel but nobody follows up, it is link 4.

Meta’s Lead Ads Testing Tool sends a fake lead through the real connection and tells you whether each CRM received it.

  1. Open developers.facebook.com/tools/lead-ads-testing while logged in as a Page admin.
  2. Select your Page and the Form your ad uses.
  3. If a test lead already exists, click Delete lead — Meta allows only one test lead per form.
  4. Click Create lead, then Track status. Click it again after a few seconds until the status changes from pending.
  5. Read the result:
    • LeadConnector is not listed at all — LeadConnector has no access to this Page. HighLevel confirms that a missing App ID means no access. Go to cause 1.
    • LeadConnector shows failed or an error — the connection or permissions are broken. Go to causes 1 and 2.
    • Success, but no contact in HighLevel — the form is not mapped or not active. Go to cause 3.
    • Contact created, but no text or email went out — go to cause 5.
What you see Likely cause Where to fix it
LeadConnector missing in the testing tool No leads access Meta Business Settings → Integrations → Leads access
“Facebook connection has expired” email Token expired or permissions changed HighLevel Settings → Integrations → Facebook
Test lead succeeds, no contact Form not mapped or not Active Settings → Integrations → Facebook Form Field Mapping
New ad’s leads missing, old ones fine New form never mapped Facebook Form Field Mapping
Contact created, some fields blank Unsupported field type or renamed field Form field mapping
Contact created, no follow-up Workflow filter or Draft status Automations → Workflows
Leads from one Page only Page deselected on reconnect Reconnect with every Page selected

Cause 1: LeadConnector has no leads access

This is the cause I find most often, especially after someone new joins the business portfolio or an agency changes. Once leads access is switched on, Meta only lets assigned CRMs receive leads: existing Page admins and CRMs keep access, but a CRM added later gets nothing until someone with full control assigns it.

Fix (as of October 2026):

  1. Log in to Meta Business Settings as someone with full control of the business portfolio.
  2. Go to Integrations → Leads access and select the Page that runs the ads.
  3. Open the CRMs tab. If LeadConnector is missing, click Assign CRMs, tick LeadConnector and click Assign, as described in Meta’s Leads Access Manager guide.
  4. If LeadConnector is listed but leads still fail, HighLevel suggests clicking Restore Default Access and checking again.
  5. On the People tab, make sure the Page admin who connected HighLevel still has leads access. Meta warns that if that person loses access, the CRM fails to fetch data.
  6. Run the testing tool again. LeadConnector should now show success.

Cause 2: the Facebook connection has expired

HighLevel emails you when the connection drops. Its multi-page troubleshooting article lists the usual triggers: a Facebook password change, natural token expiry, removing the app, logging out of Facebook, or changing Page permissions. HighLevel also recommends that the same user owns the Page and the ad account.

Fix:

  1. In HighLevel, switch to the sub-account named in the email and go to Settings → Integrations.
  2. On the Facebook card, click Connected to disconnect, then click Connect.
  3. Log in as a Page admin who also has access to the ad account, and approve every permission LeadConnector asks for.
  4. On the Page selection screen, keep every previously authorised Page ticked. HighLevel warns that deselecting a Page during reconnection can remove its access.
  5. If Pages are still missing, open Facebook Settings & privacy → Settings → Business integrations, check LeadConnector is listed with your Pages, and if not, remove it and connect again from HighLevel.
  6. Back on the Facebook card, click Troubleshoot. A warning icon means permissions are still missing; there should be none.

Cause 3: the form is not mapped or not Active

Lead access only gets the lead to HighLevel’s door. HighLevel only collects leads from forms that are mapped and marked Active. This is why a new campaign often breaks when the old one kept working: the new ad uses a new or duplicated form that nobody mapped.

Fix:

  1. Go to Settings → Integrations → Facebook Form Field Mapping. HighLevel’s setup guide covers Facebook and Instagram forms in the same place.
  2. Find the form your live ad uses — check the form name in Ads Manager, as duplicates often share a name.
  3. Map each form question to a HighLevel field: name, email and phone to the standard fields, other questions to custom fields.
  4. Avoid radio and timezone fields — HighLevel says neither can be mapped to Facebook lead forms. Use a single-line text or dropdown field instead.
  5. Set the form to Active and save.
  6. Don’t rename questions in the Facebook form afterwards; HighLevel notes that changing field names can break the mapping.

Cause 4: leads come in from one Page but not another

Agencies and multi-location businesses often connect several Pages to one sub-account. If one Page’s leads stop, it is usually because that Page was deselected during a reconnect or its form was never mapped. HighLevel’s multiple Pages article shows a warning icon on the Facebook card for each problem.

Fix:

  1. On Settings → Integrations → Facebook, look for the two warning icons: one for unmapped forms, one for missing permissions.
  2. Click the mapping warning to go straight to the unmapped form and map it as in cause 3.
  3. Click the permissions warning to open Troubleshoot and grant the missing access, then repeat cause 1 for that Page in Meta.
  4. Send a test lead from each Page with the testing tool.

Cause 5: the contact arrives but the workflow doesn’t run

If the contact is in HighLevel, the integration works and the problem is automation. The Facebook Lead Form Submitted trigger has two filters: Page Is and Form Is. One trigger covers one form, so a new form needs its own trigger.

Fix:

  1. Open Automations → Workflows and the workflow that should handle the lead.
  2. Open the trigger and check Page Is and Form Is point to the Page and form the live ad uses.
  3. For a second form, click Add New Trigger, choose Facebook Lead Form Submitted again and set its filters, rather than building a separate workflow.
  4. Check the workflow is Published, not Draft, and turn on Allow Re-entry if the same person may submit twice.
  5. If it still doesn’t fire, work through my workflow not triggering checklist.

If the first step texts the lead, the number must be registered for A2P — see my A2P 10DLC campaign rejected guide. Texting rules also vary by state, for example under Florida’s telemarketing rules. This is not legal advice.

Step 2: recover the leads you missed

Once the test lead arrives, bring back the real ones. HighLevel’s Sync Leads option processes leads that were never delivered for every mapped form on every linked Page.

  1. Go to Settings → Integrations, click Troubleshoot on the Facebook card.
  2. Choose Sync Leads and a time range — for example the past 7 or 30 days — covering the whole outage.
  3. Check the new contacts in Contacts, filtered by source.
  4. For leads older than HighLevel’s range, download them from Meta and import them as a CSV. Meta keeps lead data for 90 days from submission, so do this straight away.

Why a broken sync costs more than it looks

Every hour a lead sits in Meta is an hour nobody calls them. In Harvard Business Review’s analysis of 1.25 million sales leads, firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as those that tried even an hour later, and more than 60 times as likely as firms that waited 24 hours or longer. A sync that silently fails over a weekend puts every lead into that last group.

ChartHow much likelier a lead is to be qualified when contacted within an hour
  • vs. contacting an hour later7×
  • vs. waiting 24 hours or more60×

HBR reports “nearly seven times” and “more than 60 times”; bars show those multiples.

Source: Harvard Business Review, The Short Life of Online Sales Leads (2011)

Confirm it is fixed

Mistakes to avoid

  • Launching a new form without mapping it. The most common reason a campaign “suddenly” stops sending leads.
  • Connecting with a staff member’s login. When they leave, the sync breaks with them.
  • Deselecting Pages on reconnect. It quietly removes access to Pages that were working.
  • Running Sync Leads with the workflow on. Week-old leads get an instant “thanks for enquiring” text.
  • Leaving leads in Meta for weeks. After 90 days they cannot be downloaded at all.

Get every paid lead into your CRM

A Facebook lead is only worth what you spent on it if someone follows up in minutes. I connect lead ads, map every form, test them and build the follow-up workflow as part of a GoHighLevel CRM setup, build the landing pages and funnels that sit alongside your ads, and can add a Voice AI agent that calls new leads the moment they arrive. If leads already reach HighLevel but calls slip through, my missed call text back guide closes that gap too.

Hunaid Zia

Hunaid Zia

GoHighLevel Expert, Developer & Automation Specialist

I have built GoHighLevel systems, AI agents and websites for 50+ businesses since 2021, and written this guide from that work. Questions about your own setup? Book a free call.

References

  1. Facebook Lead Ad Integration & Troubleshooting Guide — HighLevel Support Portal
  2. Set Up Facebook and Instagram Lead Ads in HighLevel — HighLevel Support Portal
  3. Multiple Facebook Pages — Troubleshooting CTA and Sync Lead Features — HighLevel Support Portal
  4. Facebook Multi Page Troubleshoot — HighLevel Support Portal
  5. Connect Facebook Business Account to HighLevel Ad Manager — HighLevel Support Portal
  6. Workflow Trigger — Facebook Lead Form Submitted — HighLevel Support Portal
  7. Enable Leads Access in Meta Business Suite — Meta Business Help Centre
  8. Assign or remove permissions in Leads Access Manager — Meta Business Help Centre
  9. Lead Ads — Testing and Troubleshooting — Meta for Developers
  10. Download or Retrieve Your Leads Data from Meta — Meta Business Help Centre
  11. Edit or remove business integrations from Facebook — Facebook Help Centre
  12. The Short Life of Online Sales Leads — Harvard Business Review

FAQ

Quick answers.

The questions people ask most about facebook leads not syncing to gohighlevel.

Ask me directly

Usually because LeadConnector lost leads access to the Page, the Facebook connection expired, the form is not mapped and active in HighLevel, or the workflow is filtered to a different form. The leads still sit in Meta, so nothing is lost once you fix the broken link and sync them back.

As of October 2026, go to Meta Business Settings → Integrations → Leads access, choose the Page, open the CRMs tab, click Assign CRMs, select LeadConnector and click Assign. Only someone with full control of the business portfolio can do this. If LeadConnector is already listed, try Restore Default Access.

Meta records the lead when the form is submitted, whatever happens next. If HighLevel lacks permission, the form is not mapped as active, or the connection has expired, Meta never delivers the lead to HighLevel. Run a test lead with Meta’s Lead Ads Testing Tool to see where it stops.

Once the connection is fixed, go to Settings → Integrations, click Troubleshoot on the Facebook card and use Sync Leads with a time range such as the past 7 or 30 days. HighLevel says to use it only when leads are not syncing automatically. For anything older, download the leads from Meta within 90 days and import them.

HighLevel lists password changes, natural token expiry, removing the app, logging out of Facebook and changing Page permissions as common causes. Disconnect the Facebook integration under Settings → Integrations, connect again with a Page admin, and keep every previously authorised Page selected.

Check that the contact actually arrived in HighLevel first — if it did not, the problem is the integration, not the workflow. If the contact is there, the trigger’s Page Is or Form Is filter usually points at an old form, or the workflow is still in Draft. One trigger covers one form, so add a trigger per form.

Yes. Meta says you must be an admin of the Page with leads access to connect a CRM, and the admin who granted LeadConnector its permissions must keep that access or the CRM stops fetching leads. HighLevel also recommends the same user owns the Page and the ad account.

The field is either not mapped or mapped to a field type HighLevel cannot fill. HighLevel says radio custom fields and timezone fields cannot be mapped to Facebook lead forms. Map each question to a text, dropdown or standard field instead, and do not rename fields in the Facebook form after mapping.

Yes. Instagram lead ads use the same Meta Instant Forms and the same Facebook Page connection, so HighLevel documents them together. The same leads access, mapping and trigger checks apply.

Rather have it fixed?

I can do thisfor you.

If you would rather not work through this yourself, tell me what is going on and I will fix it — usually faster than reading the guide twice.

Spots fill fast — most weeks I take on two new builds.

Chat with Hunaid Zia on WhatsApp (+92 340 422 2101), opens in a new tab