HLAI Experts
Book a 1:1 with Rob

Meta Conversions API

Meta Conversions API in GoHighLevel, with the right primary event

Rob Eason, a HighLevel Certified Admin, and his team send Meta conversion events from your GoHighLevel (GHL) workflows, so the ads learn from what your buyers do after the form. We map one primary event, on the deepest paid step you can track, and no more than five events in all.

Book a 1:1 with Rob30 minutes, free

What we set up

The events, the workflows and the checks

Built with HighLevel's Meta Conversion API workflow action, sending into the dataset in your own Meta Business Manager.

  • An event map: one primary event and up to four supporting ones, each tied to a HighLevel trigger
  • Funnel events from your HighLevel forms, surveys, order forms and booked appointments
  • Lead events that start at a Facebook lead form and fire again as the opportunity changes pipeline stage
  • Stage names that match your pipeline, so the events Meta receives read like your sales steps
  • Value and currency on the Purchase stage, the one stage where HighLevel requires them
  • The dataset ID and access token from Events Manager, held in custom values
  • Matching event IDs, so a conversion the browser pixel also saw is counted once
  • Test leads run through every stage and checked in Events Manager before ads spend on it

How a setup runs

From your sales steps to events Meta can use

  1. A 1:1 with Rob

    Thirty minutes with HighLevel and Events Manager open. Rob asks what a paying customer does last: pays a deposit, books a paid consult, signs. That step is the candidate for your primary event.

  2. The event map, in the plan

    The plan document lists each event with its HighLevel trigger, the stage name Meta will see and the reason it is there. You approve it before we build. Campaigns launch optimizing on leads, and the plan says when the primary moves to the deeper step, once that step happens often enough for Meta to learn from it.

  3. Built on triggers that work

    Booked appointments go through Customer Booked Appointment, because HighLevel's general appointment trigger does not work for funnel events. Order values come from the Order Submitted trigger, since the amount is not final when the order form is submitted. Allow Multiple stays on in each workflow, so a returning lead can fire again.

  4. Tested before launch

    We create test leads with Meta's Lead Ads Test Tool, move them through the stages, and confirm each workflow ran and the event arrived. The QA report shows the event map, the workflows and Events Manager receiving each one, with screenshots.

  5. Changes after launch

    Adding an event or moving the primary? You hear first whether it sits inside the scope you approved or is new scope, before anything changes in the account.

What you bring

What the setup needs from you

Your own Facebook connection

You connect Facebook inside HighLevel from your own login, with admin rights on the Page. We never connect it from ours: our Facebook user reaches other businesses' ad accounts, and their leads would show up in yours.

Access to Events Manager

Add our team to your Business Manager so we can open the dataset, copy its ID and generate the access token HighLevel needs.

Your real sales steps

The stages a lead goes through on the way to paying, in the words your team uses. They become the pipeline stage names that travel to Meta.

Where it stops

We don't promise cheaper leads or more sales; Meta decides who sees your ads. On store pages where patients order prescription treatments, we keep the pixel and all third-party analytics off. Nothing on this page is legal advice.

By business

Where this gets set up

Commercial roofing contractors

Inquiries from building owners checked on the building before an expert calls back, and an AI voice agent on the calls your team misses.

See Commercial roofing contractors

Telehealth and online prescription clinics

A prescription store inside your own HighLevel account, an approval stage every order passes through, and ad reporting that needs no pixel.

See Telehealth clinics

Commercial solar qualification

A gate on building size, utility spend, ownership, roof condition and tax position before the expert callback, with a qualified-lead event sent back to Meta.

See Commercial solar qualification

Meta lead-form pipeline and 30-day nurture

Homeowners who fill in a Meta lead form land in a five-stage opt-in pipeline and get seven sets of follow-up over 30 days.

See Lead-form pipeline and nurture

Lead qualification pipeline

Roof and solar inquiries sorted by size, power spend, ownership and roof issue before an expert callback is booked.

See Lead qualification pipeline

Purchase tracking without pixels

Each paid order sent from a HighLevel workflow to your ad-attribution tool, so your ads learn what sold while the store pages stay free of pixels.

See Purchase tracking without pixels

Guides

Read first

Choosing a primary CAPI event

Why HighLevel has no primary switch, how Funnel and Lead Events differ, and what to check before a campaign leans on an event.

Read the guide

HighLevel triggers for CAPI events

Which workflow triggers can send Funnel Events and Lead Events to Meta, and the conditions on stage changes, bookings and orders.

Read the guide

Who connects Facebook in HighLevel

Why the client connects Facebook from their own login, what HighLevel needs, and how to fix a connection that syncs nothing.

Read the guide

Questions

What people ask about the Conversions API in HighLevel

What should our primary event be?
The deepest paid step you can track in HighLevel, such as a paid booking, a deposit or a purchase. If the primary is a form fill, Meta goes looking for more people who fill in forms. Supporting events, such as a submitted lead or a qualified lead, cover the steps in between.
Why five events at most?
More events add noise to what Meta optimizes on. One primary and up to four supporting events cover the path from first click to payment for a service business, and each one has a written reason in the plan document.
Do we still need the pixel if HighLevel sends the Conversions API?
Yes. Meta recommends running the Conversions API alongside the pixel. Meta treats a browser event and a server event as one when their event name and event ID match, and only within 48 hours of the first. HighLevel funnels send their event ID with the action, so funnel events are matched without extra setup.
Our test conversions show as Custom Event in Facebook. Is it broken?
Not necessarily. HighLevel's help center says test data may appear as Custom Event rather than Lead. If test conversions never arrive, check the Diagnostics tab in Events Manager; a blocked domain is a known cause, approved under Domains In Your Allow List.
Events Manager says it is waiting for seven days of CRM events. Why?
For lead events from HighLevel, its help center says Meta needs data sent every day: at least 50 events over seven days, in at least two pipeline stages, with test events not counted. New events can also take up to a day to show. Until real leads build that volume, the setup waits.
Have you built this in HighLevel before?
Yes. For a commercial solar installer we set up a new pixel and the Conversions API under the company's own Business Manager. A qualified-lead event fires when an inquiry passes the questions about the building, before an expert calls back.
Rob Eason

Who you talk to

Rob Eason

Rob runs HLAI Experts and takes the 1:1 calls himself.

He is a HighLevel Certified Admin with the second-most reviews in HighLevel's Certified Admin Directory worldwide, all of them 5 out of 5.

He won HighLevel's Top New Subaccounts via AI Employee award in its 2025 Summer of AI Awards and taught HighLevel's official masterclass on its AI Employee.

Before HighLevel, he co-owned a 60-employee financial services firm and sold his share.

On the call he looks at your account, not a script.

5/5 across 83 reviews in HighLevel's Certified Admin Directory

Pick your primary event with Rob

Thirty minutes with your ad account and HighLevel open. Rob names the step that should be your primary event and the workflow that would send it.

Book a 1:1 with Rob