Home/HighLevel/Features/Marketing/HighLevel workflow for Meta Conversion API with Ad Manager setup guide

Marketing

HighLevel workflow for Meta Conversion API with Ad Manager setup guide

In short

Using HighLevel’s Meta Conversion API action, you can send server side conversion events back to Meta directly from a workflow. The Ad Manager connection type lets you pick the campaign objective, select a pre filled pixel, and include value and currency when the stage is Purchase.

AreaMarketing · Section
Used forDigital marketing agency, Ecommerce store, Service based business
Setup steps8 steps in 1 task
Last updatedNovember 16, 2026

01Who this is for

  • Digital advertisers who run Meta ad campaigns need reliable conversion tracking beyond browser pixels.
  • Agency owners managing multiple client ad accounts benefit from pre populated pixel selection and automated token handling.
  • Ecommerce operators tracking purchases can send value and currency for purchase events.

02Meta conversion API actions, explained

The Meta Conversion API action lives inside the Workflow builder. After adding the action, you select a connection type, either Integrations or the new Ad Manager option. The Ad Manager choice pulls in all pixels linked to your Meta ad accounts and handles the access token automatically.

When you set the event type, you can choose Funnel, Lead, or Instagram DM events based on the campaign objective. For Lead events, specifying a Stage Name of Purchase reveals Value and Currency fields, which are included in the payload only for that stage. Custom mapping for FBCLID or Facebook Lead ID is optional and must be toggled on.

03How businesses use Meta conversion API actions

  • Digital marketing agency. Create a workflow for each client, select the Ad Manager connection, choose the appropriate pixel from the dropdown, and map the Facebook Lead ID for lead generation campaigns. The workflow then sends CAPI events automatically.
  • Ecommerce store. Add a Meta Conversion API action, pick the funnel event type for a website traffic campaign, and enable the Value field with a static sales amount. HighLevel includes the amount and USD currency in the CAPI payload when the purchase stage is reached.
  • Service based business. Use the Lead event with the Stage Name set to Purchase, select the relevant pixel, and enable custom mapping to capture the FBCLID. When a booked appointment triggers the workflow, the server side conversion is reported back to Meta.

04Before you start

  • Create the Meta ad campaign in Meta Ads Manager.
  • Set up a conversion dataset (pixel) linked to the campaign.

05How to set up and use Meta conversion API actions in HighLevel

Set up a workflow that sends Meta Conversion API events via Ad Manager

  1. Open the Workflow builder and start a new workflow.
  2. Add an action and choose “Meta Conversion API”.
  3. Select the connection type “Ad Manager”.
  4. Pick the event type that matches the campaign objective (Website traffic = Funnel, Lead generation = Lead, Click to direct = Instagram DM).
  5. Select the desired pixel from the pre populated dropdown list.
  6. If using a Lead event with Stage Name “Purchase”, enter a static or custom Value and choose the Currency.
  7. Optionally toggle custom mapping and map FBCLID or Facebook Lead ID as needed.
  8. Save the workflow and activate it.

06What it looks like in HighLevel

07Settings that matter

  • Event Type. Determines whether the workflow sends a funnel, lead, or Instagram DM conversion to Meta.
  • Stage Name. Identifies the pipeline stage; when set to Purchase it enables value and currency fields.
  • Value. Static amount or custom field sent with the CAPI payload for purchase events.
  • Currency. Currency code attached to the Value; defaults to USD.
  • Custom Mapping. When enabled, lets you map FBCLID for funnel events or Facebook Lead ID for lead events, overriding default system values.

08Things to know before you rely on it

  • Value and Currency are sent only when Stage Name is set to Purchase; otherwise they are ignored.
  • Custom mapping is disabled by default and must be turned on to use FBCLID or Facebook Lead ID overrides.

09How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Be aware that the conversion API relies on server side data, so you must have your Meta campaign and conversion dataset set up first. Without those pieces the workflow can’t send any events, and you’ll see gaps in reporting.

When everything is in place, the Ad Manager option cuts out the back and forth of copying pixel IDs and managing tokens. It streamlines the flow so you can focus on the actual event data you want to push to Meta.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about Meta conversion API actions.

Do I need to generate an access token when using the Ad Manager connection type?

No. The platform automatically provides the token, removing the need for manual copy paste.

Which workflow triggers work with a Lead event in the Meta Conversion API action?

Only “Facebook Lead Form Submission” and “Pipeline Stage Change” triggers are supported for Lead events.

Can I send value and currency for events that are not a purchase?

Those fields are ignored unless the Stage Name is set to Purchase.

How does the Ad Manager option simplify pixel selection?

All pixels linked to your Meta ad accounts appear in a dropdown, so you do not need to copy and paste pixel IDs.

Is custom mapping required to send FBCLID for funnel events?

Custom mapping is optional. It is off by default and can be toggled on to map FBCLID.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.