Integrate Meta highlevel CRM conversion tracking app

In this guide

The native route The webhook and server route Which to choose Agency tips Common problems A worked example: an agency with several clients Terms you will see Frequently asked questions

Key takeaways

HighLevel workflows can send events to the Meta Conversions API and can call webhooks for your own server.
Capture fbc, fbp and the hashed e-mail on the contact at the form.
Agencies often combine HighLevel with a server container to cover more platforms and keep cookies alive.

HighLevel is widely used by agencies and local service businesses, with funnels, forms, a pipeline and automation in one place. That makes it a natural place to send lead stages back to Meta. It has its own Conversions API action in workflows, and it can also post to a webhook. This page explains when to use which, and how a server container fits. See the pattern in CRM data to Meta with webhooks and the Meta details in how to set up the Conversions API. Features differ by plan and change, so check HighLevel's documentation.

The native route

Connect Meta to HighLevel

Link your Meta business account and choose the dataset.

Build a workflow

Trigger on a pipeline stage change or a form submission.

Add the Meta Conversions API action

Choose the event name, such as Lead or Purchase, and map the contact fields.

Check the match fields

Ensure e-mail, phone, fbc and fbp are passed.

Test

Use Meta's Test Events.

This is the fastest way to a result for a one-platform agency.

Data in, clean out

Raw events in. Clean events out.

Open Tracked collects each event on your own domain, removes the noise and sends what is left to Meta, Google Ads, TikTok.

The webhook and server route

If a client advertises on Meta and Google, or you want longer cookies and stored data, send a webhook from the workflow to your tagging server. The container turns it into events for each platform. The identifiers come from the contact: store fbc, fbp and the Google click ID in custom fields at the form. Open Tracked's Cookie Keeper and Click ID Restorer (on every plan) help keep them until the form is submitted, and the Data Store and Enricher add stored hashed data for returning visitors.

Which to choose

Choose The native action if

one client, one platform
you want results in a day
you are comfortable with HighLevel's field mapping

Choose The webhook route with a server container if

you run several platforms for the client
you want one set of event rules for all clients
you need to control the data

The short version

3 things to remember

Scroll and the points stack up.

HighLevel workflows can send events to the Meta Conversions API and can call webhooks for your own server.

Capture fbc, fbp and the hashed e-mail on the contact at the form.

Agencies often combine HighLevel with a server container to cover more platforms and keep cookies alive.

Agency tips

Use one naming scheme for stages across clients, so reports and workflows are reusable.
Keep a checklist per client with tokens, dataset IDs and who owns them. See the agency handbook.
Send only stages that predict revenue.
Re-test after any form or funnel change.

Common problems

SymptomEvents do not match

Likely causeThe contact lacks fbc or fbp.

FixAdd hidden fields in the funnel form and fill them with a script.

SymptomDuplicates

Likely causeBoth the native action and the server send the same event.

FixChoose one route per event.

SymptomWrong value

Likely causeThe opportunity value is empty.

FixSet a value per stage if the real one is unknown.

0 of 5 done

Meta is connected and the dataset is chosenThe workflow triggers on the right stageContacts carry identifiersOne route sends each eventTest Events shows the event

A worked example: an agency with several clients

A small agency runs Meta ads for twelve local businesses, each in its own HighLevel sub-account. For the first clients they used the native Conversions API action. It worked, but each client needed its own set-up and the team could not control the data. For the clients who also use Google Ads, they moved to a webhook that sends each stage to a client-specific path on a shared server container. The container sends the same stage to Meta and Google with the identifiers saved on the contact. Adding a new platform for a client became a tag change, not a rebuild of twelve workflows.

The lesson for agencies is to standardise. Use the same stage names, the same custom field names and the same checklist for every client. The less each client differs, the less you have to remember, and the easier it is to hand a client to a colleague. Keep a simple sheet of which client uses which route, who owns the tokens and when each was last tested.

Terms you will see

Sub-account: A separate HighLevel workspace for one client.
Workflow: An automation that runs when something happens to a contact.
Opportunity: A deal in the HighLevel pipeline.
Custom field: A field you add to store extra information on a contact.
Dataset: Meta's place for events, once called a pixel.

Every few months, run a full test for one client from the funnel form to the event in Meta, and write down the result. Workflows in no-code tools get edited by many people, and a small change in a form or a stage name can silently break the link. A dated test note per client is a cheap insurance policy, and it gives you something concrete to show when a client asks whether their tracking is still working.

Trusted

Brands that grow on cleaner data

Stores and agencies use Open Tracked to see which ads earn the sale.

Frequently asked questions

Does HighLevel support the Meta Conversions API?

Yes. Its workflows can send events to the Conversions API, depending on your plan.

Where do I store fbc and fbp?

In custom contact fields, filled from hidden form fields.

Should an agency use a server container too?

If clients advertise on several platforms or need longer cookies, yes.

How do I avoid duplicate events?

Choose one route for each event and keep a shared event ID.

Does Open Tracked integrate with HighLevel directly?

Through webhooks to your tagging server. There is no packaged app.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Integrations →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...