Meta Conversions API Setup for Lead-Gen Businesses

01 • the problem

Why do my Meta ads get credit for form fills, not sales?

Most lead-gen ad accounts only tell Meta one thing: someone filled in a form. That event, usually called Lead, is recorded by the Meta pixel, a small piece of code on your website that reports visitor actions back to Meta. What happens next, the phone call, the inspection, the deposit, the signed contract, happens in your CRM (the system where you keep and track leads) or in your inbox, where Meta cannot see it.

So Meta's delivery system does exactly what it is told: it finds more people who fill in forms. If many of those people never answer the phone, the ads still look successful inside Ads Manager while your sales team sees junk. That gap between 'leads' in Ads Manager and customers in your bank account is the problem this service fixes.

02 • the fix

How does the Conversions API send real sales back to Meta?

The Conversions API (often shortened to CAPI) is Meta's way for your server or CRM to send events directly to Meta, instead of relying only on the visitor's browser. Meta calls the browser pixel plus the Conversions API sending the same events a 'redundant setup', and recommends it in its developer documentation.

For lead-gen businesses the important part is step 4. Meta's Conversions API for CRM lets you send lead stages, such as 'qualified', 'appointment booked' or 'sold', from your CRM back to Meta. Meta's own page says this 'may yield higher quality leads that are more likely to convert'. That is Meta's wording, and it is a possibility, not a promise.

03 • what i set up

What exactly do you set up?

Hashing means turning an email address or phone number into a scrambled code before it is sent, so Meta can match it to an account without receiving the plain text. Meta's best-practices page explains that its Business SDK hashes these values automatically, and that you must hash them yourself if you do not use the SDK.

If your leads live in GoHighLevel, the setup uses GoHighLevel's built-in Meta Conversion API workflow action. See GoHighLevel CRM setup. If you would rather own a simple CRM outright, I can build one on Supabase. See GoHighLevel vs a custom CRM.

04 • choosing the right event

Which pipeline stage should I send as the quality event?

Pick the earliest stage that reliably separates good leads from bad ones. Too early (a form fill) and you learn nothing new. Too late (a signed contract three months later) and Meta's learning window has closed. Meta's Conversions API for CRM guidance asks for a target stage that happens within 28 days of the lead, with a conversion rate between 1% and 40%.

Each industry lands somewhere different. A roofer might choose 'inspection booked', a gym 'trial attended', a solar company 'site survey booked'. The niche pages below go through this in detail.

05 • the honest limits

What are the limits of Conversions API tracking?

Good tracking is not magic, and some limits are set by Meta or by law. You should know them before you pay anyone.

• Volume. Meta's Conversion Leads optimisation needs enough leads to learn from. Meta's developer page says at least 200 leads a month; GoHighLevel's help article says at least 250. Below that, CRM events still improve your reporting, but the 'optimise for quality' option may not be available.
• Instant forms only. Meta's page says the Conversion Leads goal works only with Facebook and Instagram lead ads (instant forms). Website-form campaigns can still receive CRM events, but they optimise differently.
• Timing. Meta's server event documentation says events can be sent up to 7 days after they happened. Older events are rejected. So CRM events need to be sent daily, not once a month.
• Health and wellness. Meta restricts data sharing for some businesses it classifies as health-related. If that applies to you, some events or details may not be used. See Meta's health and wellness restrictions.
• Consent. In the UK and EU, advertising pixels generally need the visitor's consent before they run. See Meta ads tracking and consent.
• Your data quality. If your team does not move leads through stages consistently, Meta learns from bad data. Part of the setup is making stages easy to keep up to date.

06 • who it suits

Who is Conversions API setup for?

It suits businesses where a lead is not a sale, and where the steps in between happen offline or in a CRM. That covers most service businesses that run Meta ads for enquiries.

• Roofers, remodelers and HVAC companies, where an inspection or quote sits between the lead and the job.
• Solar and pool builders, with long, high-value sales cycles.
• Gyms and fitness coaches, where a trial, a visit or a sales call comes before payment.
• Wedding venues, where a tour and a date hold come before the contract.

I do not offer this tracking service to med spas or other health businesses, because of Meta's health and wellness restrictions and the legal risks around health data. For med spas I build websites only: see med spa website design.

07 • how it works

How does the setup process work?

1. 1Free tracking check. You share view access to Events Manager (and your CRM if you like). I send a short written summary of what Meta receives today and what is missing.
2. 2Plan. We agree which events matter: your lead event, your quality stage and your purchase or 'won' stage, and how each is named.
3. 3Build. I set up the pixel, the Conversions API, deduplication and the CRM events, and connect consent handling where needed.
4. 4Test. Every event is checked in Meta's Test Events tool and in Events Manager, which Meta says usually shows new server events within about 20 minutes.
5. 5Report. You get a plain-English document listing every event, where it comes from and how to check it yourself, plus a short screen recording if helpful.

Everything is set up in your own Meta Business account and your own CRM. You keep full control, and you can remove my access at any time.

08 • before you hire anyone

How can I check my current tracking myself?

1. 1Open Meta Events Manager and choose your dataset (the pixel ID).
2. 2Look at the Overview: which events arrive, and under 'Connection method', whether they come from the browser, the server or both.
3. 3Check whether you see anything after 'Lead'. If not, Meta is optimising for form fills only.
4. 4Open an event and look at its Event Match Quality score, Meta's rating out of 10 for how well it can match events to people.
5. 5Compare one week of Leads in Ads Manager with the same week in your CRM. Big gaps point to tracking or duplication problems.

Want a rough sense of what untracked, uncontacted leads cost you? Try the ad cost leak calculator with your own numbers.