GoHighLevel Facebook ads conversion tracking: why only some leads reach Meta

Quick question for anyone running Facebook ads through HighLevel. What percentage of your leads do you think actually get reported back to Meta?

I'm asking because the honest answer is: it depends on how each lead walked in the door. And most people have never measured it.

HighLevel has its own Meta Conversions API action, and it's good at what it covers. The catch is what it covers. It sends pipeline events only for contacts that came from a Facebook lead form, or that have a stored fbclid.

So think about the four ways a lead can arrive. A Facebook lead form: reported. A website form where the fbclid got stored on the contact: reported. A website form where the click ID got lost on the way: silence. A call or chat with no click ID on the contact: silence.

The second and third look identical to the person filling in the form. Only one of them ever reaches Meta.

Let me make it concrete with a made-up month. 100 leads: 40 from Facebook lead forms, 35 from the website with the fbclid stored, 25 from the website where it got lost. Meta hears about 75 of them, and never about the other 25. Now suppose those 25 are your best ones, because they came from the retargeting campaign and had already visited twice. Meta never learns that retargeting works, so it quietly shifts money toward the audiences that happen to have clean plumbing.

That's the real cost, and it's why I think this problem hides so well. Nothing errors. The campaign just gets a picture of "who converts" that was shaped by plumbing, not by buyers, and stops getting better.

So where does the click ID go missing? Embedded forms that never see the page URL. A redirect that strips the parameter. A lead who clicks on Monday and comes back on Thursday. Safari, which caps cookies written by JavaScript at 7 days, and at 24 hours if the visitor arrived through a link from a known tracker. And my favourite: someone rebuilds a funnel and the hidden field quietly disappears.

And if you're an agency, remember the action is set up per sub-account. Twenty clients is twenty workflows, each able to break the next time a funnel changes, and each needing someone to notice.

What you can do about it, in order of effort. Make the click ID survive: hidden field, read the parameter on landing, save it on the contact at submit, and test it on the ugly paths, not just the demo. Add a hashed email or phone as a fallback so Meta can find the person without the click ID. Or accept the limit and tell your client the numbers cover the lead form path only. All three are legitimate. The only bad option is not knowing which one you're on.

If you're an agency, here's the sentence I'd give clients: "Meta only hears about leads that arrive through paths that keep the click ID, so the numbers in Ads Manager describe part of your leads, and here is which part." Saying that up front turns a hidden gap into a managed one, and it makes the fix an easy conversation instead of an awkward one.

Quick note on "why not just use my CRM's own sync?". Sometimes you should. If you run one account, most leads come from the platform's own lead forms, and you only need one ad platform, the built-in sync may be all you need, and you can stop reading here. Where it tends to fall short: coverage (some sync only reports leads with a stored click ID or from a specific lead form, and silently skips the rest), platforms (many cover one or two ad platforms, not four), scale (one setup per client or sub-account), and visibility (few tell you when a lead was skipped). If none of that affects you, the native option is the right call. If it does, that's where a dedicated layer earns its place.

One honest limit: connecting a sub-account is one click, but the website script and DNS record need access to the client's site, and that's usually the slow part per client.

If you run HighLevel: have you measured what share of your leads reaches Meta? I'd really like to hear the number, even a rough one.