Facebook Lead Ads to GoHighLevel: Setup Guide (2026)
Facebook Lead Ads to GoHighLevel: Setup Guide (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 15 August 2026 · 9 min read
A working GoHighLevel Facebook Lead Ads integration takes about fifteen minutes to connect and roughly an hour to make reliable. The connection itself lives under Settings > Integrations in the sub-account, where you authorise the LeadConnector app against your Facebook profile and then choose which Pages it may read leads from. That second step is the one most people skip, and it is the reason so many accounts show a green "Connected" badge while no leads arrive.
The rest of the work is unglamorous but decides whether the build survives contact with a real campaign: mapping instant-form questions to custom fields, normalising Australian mobile numbers so SMS actually sends, tagging leads by campaign and form so you can attribute spend, and building a workflow that responds inside sixty seconds. Below is the sequence I use on client sub-accounts, the failure modes I see most often when auditing an inherited build, and an honest comparison of the native integration against Zapier, Make and raw webhooks. Everything here assumes a standard sub-account with a connected Twilio (LeadConnector) number and Mailgun for email.
Connecting the GoHighLevel Facebook Lead Ads integration
Go to Settings > Integrations inside the sub-account (not the agency view) and select Facebook. You will be asked to log in with a personal Facebook profile. GoHighLevel does not connect to a Page directly; it connects to a person, and inherits whatever that person is permitted to do. This matters enormously for continuity, which I will come back to.
After authorising, you are shown a list of Pages that profile can administer. Select every Page that will run lead forms, then save. If a Page is greyed out or missing, the connecting profile does not hold the right role on it. Once saved, open the Facebook integration again and confirm the Page shows as connected and that "Leadgen" or lead access is enabled against it. A connection that authorises the account but never selects a Page is the single most common cause of silence.
Permissions and Business Manager roles that actually matter
The connecting profile needs, at minimum, a role on the Page that includes managing leads. In the current Business Manager model that means a Page role with Leads Access, or full Page admin. If the client runs ads through a Business Manager, the Page should be owned by the Business, the ad account should be linked to the same Business, and your connecting profile should be an employee or admin of that Business with task-level access to the Page.
The permissions GoHighLevel requests during OAuth include pages_show_list, leads_retrieval, pages_manage_metadata and ads-related scopes. If a client's security team strips permissions during review, lead retrieval silently stops. Ask for the full scope set at connection time rather than negotiating it later.
One practical rule for agencies: never connect using a staff member's personal profile that might leave the business. Use a durable admin profile, document who it belongs to, and note the renewal in your handover. Meta's own documentation on lead ads access and permissions is worth reading once so you can explain the requirement to a client without guessing.
Why leads stop flowing
Four causes account for almost every "the leads stopped" ticket I receive. First, the connecting profile lost its Page admin role — usually because someone tidied up Business Manager. Second, token expiry: Meta access tokens are long-lived, not permanent, and password changes, session invalidation or a Meta security review will kill them. Third, re-authorisation after a permission change, where the account reconnects but nobody re-selects the Pages, so the connection looks healthy and delivers nothing. Fourth, a new Page or a new form on an existing Page that was never added to the selection.
Build a monitoring habit rather than relying on someone noticing. I set a recurring task on the sub-account to open Settings > Integrations monthly and confirm each Page is still listed, and I run a workflow that alerts the account owner if no contact with the tag fb-lead has been created in 48 hours on an account with live spend. A quiet CRM during a running campaign is a fault until proven otherwise.
The Facebook Lead Form Submitted trigger
In Workflows, add the trigger "Facebook Lead Form Submitted". Left unfiltered it fires for every form on every connected Page, which is fine for a single-offer account and disastrous for a business running six lead magnets. Add a filter on the specific Page and, more importantly, on the specific form. Meta creates a new form ID whenever a form is duplicated or edited beyond a certain point, so a filtered workflow can go quiet after a routine creative refresh. Whenever the media buyer duplicates a form, the workflow filter needs updating — put that in the campaign launch checklist.
My preferred pattern is one intake workflow per offer, not per form. The intake workflow handles field tidy-up, tagging and the speed-to-lead sequence; downstream nurture lives in separate workflows triggered by tag. That keeps changes contained. If you are new to how triggers, filters and actions interact, the mechanics are covered in more depth in this guide to GoHighLevel workflows, triggers and actions.
Mapping instant-form questions to custom fields
Standard questions — full name, email, phone number, postcode — map to GoHighLevel's standard contact fields automatically. Everything else needs a home before the campaign goes live. Create the custom fields first under Settings > Custom Fields, then open the trigger's field mapping and pair each instant-form question to its field. Single-choice questions map cleanly to a dropdown or single-line text; multi-choice answers arrive as a delimited string, so use a multi-line text field unless you intend to parse them.
Three cases deserve attention. Custom questions must exist as custom fields before mapping, or the answer is discarded at the point of capture and cannot be recovered later. Conditional questions may arrive empty for some leads by design — never make a downstream workflow depend on one being populated. Hidden fields, which Meta populates from URL parameters or from the form's own configuration, are how you carry campaign, ad set and creative identifiers into the CRM; map each to its own custom field rather than concatenating them, because you will want to filter on them individually when reporting.
Test the mapping before spend starts. A missing field discovered on day one costs you an afternoon; discovered on day thirty it costs you a month of attribution data. If you also capture leads through GoHighLevel's own forms, keep the field names identical across both sources so your reporting does not fracture — the approach I use for GoHighLevel forms and surveys for lead capture applies here unchanged.
Australian phone numbers and the +61 problem
Meta returns whatever the lead's profile holds, which in Australia is usually 0412 345 678, sometimes +61412345678, occasionally 61412345678 with no plus. LeadConnector and Twilio require E.164, so a leading-zero number will fail to send and the failure is often quiet.
Handle it in the intake workflow with an Update Contact action driven by conditional logic: if the phone starts with 04, strip the leading zero and prefix +61; if it starts with 61 without a plus, prefix the plus; if it already starts with +61, leave it alone. Strip spaces and brackets in all branches. Landlines follow the same pattern with area codes 02, 03, 07 and 08. I add a tag such as phone-invalid on anything that matches none of these branches and route those contacts to a manual review list rather than letting them disappear into a nurture sequence that can never reach them.
Tagging, attribution and Ad Manager reporting
Attribution is a tagging discipline, not a feature you switch on. In the intake workflow, apply a source tag (fb-lead), an offer tag, and a campaign tag drawn from the hidden field carrying the campaign name. Set the contact Source field to something consistent like Facebook Lead Form, and create the opportunity in the correct pipeline stage in the same workflow so pipeline value can be traced back to spend.
GoHighLevel's Ad Manager view pulls Meta and Google campaign metrics into the sub-account and, where attribution data is present, shows leads and conversions against campaigns without leaving the CRM. It is useful for a weekly read on cost per lead by campaign, though I still reconcile against Ads Manager before invoicing a client. The setup and its limits are covered in this walkthrough of the GoHighLevel Ad Manager for Meta and Google Ads.
Duplicate contacts
GoHighLevel deduplicates on email and phone at the sub-account level, so a lead who submits two forms typically lands on one contact record with both submissions in the timeline. That is the behaviour you want, but it creates a trap: a returning lead will not re-enter a workflow configured to allow contacts through only once. If a repeat enquiry should trigger a fresh response, set the workflow to allow multiple entries and add your own guard — for example, skip the SMS if the contact was messaged in the last 24 hours. Where a lead uses a different email each time, dedupe on phone and merge manually; automatic merging across mismatched identifiers causes more damage than it prevents.
Speed-to-lead automation that fires inside sixty seconds
The commercial argument for this whole build is response time. A Facebook lead is warm for minutes, not hours. My standard intake sequence: normalise the phone, apply tags, create the opportunity, then send an SMS within seconds that names the business and the specific offer the person enquired about. Thirty seconds later, an email via Mailgun with a booking link. At the sixty-second mark, a call connect action that rings the sales mobile and bridges to the lead when answered.
Two refinements matter. Add business-hours logic so a 2am lead receives the SMS and email but the call attempt is queued for the morning — a missed call at dawn undoes the goodwill the fast reply just earned. And route inbound replies properly: if nobody is available to answer, a Conversation AI bot can hold the conversation, qualify and book, provided you have given it clear scope and a handover rule. The same reflex applies to phone enquiries, which is why I pair every lead ads build with missed call text back on the same number.
Australian SMS compliance, briefly
A2P 10DLC registration is a United States requirement and does not apply to Australian numbers. What applies here is the Spam Act 2003, administered by ACMA. In practice: you need consent, and a Facebook lead form submission is generally inferred consent for messages about the thing they enquired about, not a licence to broadcast unrelated offers. Every commercial message must clearly identify the sender and who authorised it, and must contain a functional unsubscribe that you honour within five working days. Alphanumeric sender IDs cannot receive replies, so for a two-way speed-to-lead conversation use a standard mobile number. Do-not-call rules also apply to the phone call leg for numbers on the Do Not Call Register, though enquiries you have solicited are usually treated differently — check your specific case rather than assuming.
Native, Zapier, Make or webhook
The LeadConnector native integration is the default for good reason: no per-lead cost, no third-party hop, and the trigger is available inside Workflows. The alternatives earn their place when you need to enrich, route across multiple systems, or write to a platform GoHighLevel does not speak to. Costs below are illustrative only — check the vendors' current pricing pages before quoting a client.
| Path | Typical latency | Cost shape | Best for |
|---|---|---|---|
| LeadConnector native | Seconds | Included in the sub-account | Standard lead capture into one GoHighLevel sub-account |
| Zapier | Seconds to minutes, depending on plan polling | Per-task, tiered | Fan-out to several tools with minimal build effort |
| Make | Seconds to a few minutes | Per-operation, tiered | Branching logic, enrichment, cheaper at high volume |
| Direct webhook to inbound webhook trigger | Sub-second | Build time only | Custom apps and high-volume routing where you control the sender |
A note on the middle two: instant triggers for Facebook Lead Ads exist on both platforms, but polling-based configurations on lower tiers introduce delay measured in minutes, which defeats the point of speed-to-lead. If you go this route, confirm the trigger is instant. The trade-offs are compared in detail in this piece on GoHighLevel webhooks and Zapier integrations.
Testing with Meta's Lead Ads Testing Tool
Do not test with real spend. Meta's Lead Ads Testing Tool lets you select a Page and form and submit a synthetic lead, which travels the full path into GoHighLevel. Watch for four things: the contact is created; every mapped custom field is populated, including hidden fields; the phone number arrives in E.164 after your normalisation step; and the SMS actually delivers to a real handset you control. Then delete the test lead so it does not pollute reporting. GoHighLevel's own Facebook integration help documentation lists the current connection requirements if Meta changes the flow again.
Common mistakes to avoid
- Connecting the integration with a staff member's personal Facebook profile that leaves with them, taking lead retrieval with it.
- Authorising the account but never selecting the Page, which produces a "connected" status and zero leads.
- Leaving the Facebook Lead Form Submitted trigger unfiltered, so every form drops into one sequence with the wrong follow-up message.
- Mapping fields after the campaign launches, which permanently loses the answers submitted before the mapping existed.
- Sending SMS to Australian mobiles in
04format instead of E.164, then assuming the silence means the leads are poor quality. - Applying US A2P 10DLC assumptions to an Australian sub-account instead of the Spam Act consent, sender identification and unsubscribe rules that actually apply.
If you want your Facebook Lead Ads wired into GoHighLevel with speed-to-lead automation that actually fires, book a strategy call with the HL Growth Partner team.
Frequently asked questions
How long does the GoHighLevel Facebook Lead Ads integration take to set up?
The connection under Settings > Integrations takes ten to fifteen minutes including Page selection. Budget another hour for custom field creation, form mapping, phone normalisation, tagging and the speed-to-lead workflow. Testing with Meta's Lead Ads Testing Tool adds fifteen minutes and is not optional.
Why did my leads stop arriving without any error message?
Almost always one of four things: the connecting profile lost its Page admin or Leads Access role, the access token expired, the account was re-authorised without re-selecting Pages, or a new form was created that the workflow filter does not match. Check the Page selection first, then the trigger's form filter.
Do I need A2P 10DLC registration to send SMS to Australian leads?
No. A2P 10DLC applies to United States numbers. Australian sending is governed by the Spam Act 2003 under ACMA, which requires consent, clear sender identification and a working unsubscribe honoured within five working days. Use a standard mobile number rather than an alphanumeric sender ID if you want leads to reply.
Should I use the native HighLevel Facebook lead form integration or Zapier?
Use the native integration unless you have a specific reason not to. It is faster, included in the sub-account and has no per-lead cost. Reach for Zapier or Make when a lead must reach several systems at once, needs enrichment before it lands, or must be routed across multiple sub-accounts by rules the native trigger cannot express.
What happens when the same person submits two lead forms?
GoHighLevel deduplicates on email and phone, so both submissions usually attach to one contact record. The catch is that a workflow set to allow only one entry per contact will not fire again. If a repeat enquiry needs a fresh response, allow multiple entries and add a guard so the contact is not messaged twice in a short window.
