The question comes up because setup checklists talk about a primary event as if it were a HighLevel field. It isn't one. This guide covers the two kinds of events HighLevel sends, how to set one up so it can carry a campaign, why a later-stage event goes missing, and how we weigh the choice, which no HighLevel or Meta page we've read settles for every business.
Sending an event and optimizing for it are two settings
A HighLevel workflow sends a conversion event when its trigger fires and its Meta Conversion API action runs. Connecting a conversion pixel doesn't decide when that happens. The workflow does.
Choosing which event a campaign optimizes for is a different decision, made with the campaign. Nothing in the workflow action marks one event as the one to chase. Labelling an event "primary" in a plan or a spreadsheet is a note for whoever sets up the campaign; it changes nothing in the account on its own.
HighLevel sends the events. The campaign decides which one it chases.
Funnel Events and Lead Events
HighLevel sorts what it sends into two kinds. The event you hope to optimize for has to be the right kind before anything else about it matters.
- Funnel Events report web activity, such as a checkout or a purchase on a HighLevel page.
- Lead Events describe a contact moving through your pipeline stages. HighLevel's conversion leads integration shares that CRM progression with Meta.
Setting up an event a campaign can use
Whichever event you plan to optimize for, it has to arrive reliably before it can do that job. The setup runs the same way for each one.
- Decide whether the activity is a web or funnel action, or a step in your pipeline. That decides whether it's a Funnel Event or a Lead Event.
- Pick a workflow trigger that fires on exactly that activity, and set the action's Event Type to match. Both have to describe the activity being reported.
- Choose the connection type in the Meta Conversion API action: Integrations or Ad Manager. Ad Manager can fill in the conversion pixel for you and manages the action's access token.
- Select the conversion pixel the event should go to.
- Before you map a later-stage event, such as a stage close to the sale, check that the attribution data it depends on is stored on the contacts who will reach that stage.
Why a later-stage event goes missing
An event fired near the end of the pipeline is only as good as the attribution data stored on the contact. When that data is missing, matching the conversion can fail even though the workflow ran without an error.
That's why we look at stored attribution on real contacts before a later stage becomes the event anyone plans a campaign around. A stage that fires often in HighLevel isn't much use to a campaign if the contacts reaching it carry nothing Meta can match.
How we weigh the choice
We haven't found a HighLevel or Meta page that names one event every business should optimize for. So we treat it as a judgment, made with your own pipeline in front of us, and we weigh four things:
- Which step a paying customer reaches that HighLevel can actually see and report.
- Whether that step is a Funnel Event or a Lead Event, and whether its trigger and Event Type are a true match.
- Whether the contacts who reach it have attribution stored, so the event can be matched at all.
- Whether it happens often enough to be worth optimizing toward yet. When it doesn't, an earlier step can carry the campaign for now, and the plan says when to look at it again.
Rather have it set up for you?
We map the events your campaign can choose from, build the workflows that send them and check each one arrives, starting with a 30-minute 1:1 with Rob.