GoHighLevel Meta Conversions API Setup, Step by Step

01 • before you start

What do I need before setting up GoHighLevel's Conversions API?

A dataset is Meta's name for the container that receives your pixel and server events. Its ID is what GoHighLevel's action calls the Pixel ID.

02 • step 1

How do I create the CRM data source in Meta?

1. 1In Meta Events Manager, choose Connect Data Sources.
2. 2Choose CRM, then Next, and review the best-practices screen.
3. 3Create a new pixel (dataset) or select an existing one.
4. 4Choose LeadConnector as the CRM partner. HighLevel's article says you can ignore the partner login redirect.
5. 5In the dataset's Settings, copy the Dataset ID and click Generate Access Token. Copy the token and keep it private.

03 • step 2

How do I set up the first workflow (create the opportunity)?

1. 1In Automations > Workflows, create a new workflow.
2. 2Trigger: Facebook Lead Form Submitted (optionally filtered to specific forms).
3. 3Add the Meta Conversion API action with your access token, pixel ID and stage name.
4. 4Add a Create or Update Opportunity action, choosing the pipeline and starting stage.
5. 5Name the opportunity, for example with the lead's full name.
6. 6Turn on Allow Duplicate Opportunities, and Allow Multiple in workflow settings. Save and publish.

04 • step 3

How do I send pipeline stage changes to Meta?

1. 1Create a second workflow with the trigger Pipeline Stage Change.
2. 2Add the Meta Conversion API action and choose Lead Event as the event type.
3. 3Enter the access token and pixel ID.
4. 4For Stage Name, insert the opportunity's pipeline stage custom value, so Meta receives the real stage name.
5. 5Turn on Allow Multiple in workflow settings. Save and publish.

05 • step 4

How do I test the GoHighLevel to Meta connection?

1. 1Use Meta's Lead Ads Testing Tool to create a test lead on the right page and form.
2. 2Check workflow 1 ran and the opportunity appeared.
3. 3Move the test lead to another stage.
4. 4Check workflow 2 ran, then look for the event in Events Manager. HighLevel's article notes this can take up to a day.

06 • common mistakes

What are the common mistakes with GoHighLevel and Meta events?

• Allow Multiple left off, so the workflow only runs the first time a lead changes stage.
• The access token copied from the wrong dataset, or regenerated later without updating the workflow.
• Stage names typed by hand instead of using the stage custom value, so Meta receives inconsistent names.
• Old leads bulk-moved between stages, which fires a burst of events about people who are not new.
• Lead form field mapping switched off after a form change, so new leads stop arriving with their Meta lead ID.
• Funnel leads expected to match without the click ID being captured and stored.

07 • key terms

Which terms do I need to know?

Short, plain definitions of the terms used on this page.

08 • conversion leads

Will this let me use Meta's Conversion Leads optimisation?

Only if you meet Meta's requirements. HighLevel's article lists: instant-form lead ads with field mapping, the Meta lead ID mapped to your CRM, at least 250 leads a month, daily uploads, the target stage within 28 days, and a 1%–40% stage conversion rate. Meta's own developer page gives the lead minimum as 200. Details in Conversion Leads optimisation.

Website forms and funnels can also send events from GoHighLevel. HighLevel's article notes that stage events for funnel leads work if the Facebook click ID (fbclid) is captured, stored in a contact field and sent through custom mapping.