Home/HighLevel/Features/Integrations/How to add Facebook Conversion API actions in HighLevel workflows

Agency, Settings and Integrations

How to add Facebook Conversion API actions in HighLevel workflows

In short

The Facebook Conversion API trigger in HighLevel workflows lets you send conversion events directly to Meta when a contact meets a workflow condition. It works with triggers such as form submitted, appointment booked, tag added, or opportunity status change, provided the contact already carries Facebook attribution data.

AreaIntegrations · Facebook Integration
Used forReal estate agency, Ecommerce store, Coaching business
Guide typeOverview
Last updatedNovember 16, 2026

01Who this is for

  • Marketers who run Facebook ad campaigns and need server side conversion tracking without relying on browser cookies.
  • Agencies managing multiple client accounts that require consistent attribution across form submissions, appointments, and opportunity updates.

02Facebook conversions API triggers, explained

The Facebook Conversion API action is a workflow step that posts conversion data to Meta’s servers. It bypasses the need for a Facebook pixel on the landing page, sending the information from HighLevel instead. The action can be added to any workflow where the contact already has Facebook attribution data, such as fbclid or fbc.

03How businesses use Facebook conversions API trigger

  • Real estate agency. The agency creates a workflow that fires on "Customer Booked Appointment" after a prospect schedules a showing. The workflow sends a "Lead" event with the prospect’s email and IP address to Meta, allowing the agency to record the conversion without a pixel on the booking page.
  • Ecommerce store. When an order is submitted, a workflow runs the Facebook Conversion API action using the "Order Submitted" trigger. It includes the order amount via the {{Order.Amount}} custom value and sends the purchase event to Meta for accurate ad reporting.
  • Coaching business. A workflow triggers on "Contact Tag Added" after a lead is tagged as "Qualified." Because the contact originally arrived via a Facebook ad and holds fbclid data, the workflow posts a "Lead" event with the contact’s name and email to Meta.

04Before you start

  • The contact must already have valid Facebook attribution data, such as fbclid/fbc or a Paid Social (Facebook) attribution record.

05Settings that matter

  • Event Source URL. Specifies the URL where the conversion originated; it is sent to Meta as part of the event payload.
  • Client IP address. Sends the visitor’s IP address to Meta without hashing.
  • Client user agent. Provides the browser’s user agent string to Meta, also unhashed.
  • Email Address. Includes the contact’s email for matching in Meta’s system.
  • First Name. Adds the contact’s first name to the conversion payload.
  • Surname. Adds the contact’s last name to the conversion payload.
  • Browser ID (fbp) cookie. Sends the fbp cookie value to Meta without hashing.
  • Click ID (fbc) cookie. Sends the fbc cookie value to Meta without hashing.
  • Access Token. The token used to authenticate the API call; it can be supplied via a custom value.
  • Pixel Id. Identifies the Facebook pixel that should receive the event; it can be supplied via a custom value.

06Things to know before you rely on it

  • The {{Order.Amount}} custom value works only with the "Order Submitted" trigger because the amount is final after payment.
  • Test events may appear as "Custom Event" in Facebook Business Manager even when the event type is set to "Lead"; live events display correctly.
  • If a domain is blocked by Facebook, events will not register; the domain must be added to the "Domains In Your Allow List" section in Settings.
  • Event deduplication is automatic; no manual setup is required.

07If something goes wrong

  • Test conversion does not appear in Facebook Business Manager.. Open the Diagnostics tab in HighLevel to view errors, then add the domain to Settings > scroll to the bottom and place it in "Domains In Your Allow List."

08How 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 API trigger only works when the contact already carries Facebook attribution data. If the data isn’t there, the workflow will fire in HighLevel but Meta won’t register a conversion, which can lead to confusing reporting gaps.

When the data is present, the trigger gives you a way to push conversions to Meta without relying on a pixel. It’s useful for any business that runs Facebook ads and wants server side tracking that sidesteps cookie blockers.

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

Common questions

Common questions about Facebook conversions API trigger.

Which workflow triggers can fire a Facebook Conversion API event?

Triggers such as Form Submitted, Survey Submitted, Customer Booked Appointment, Order Form Submission, Facebook Lead Form Submission, Pipeline Stage Change, Contact Tag Added, Opportunity Status Changed, and other contact based triggers work as long as the contact has Facebook attribution data.

What customer information can I send with the conversion event?

You can include the client IP address, client user agent, email address, first name, surname, fbp cookie, and fbc cookie, all sent unhashed.

Can I use custom values for the Access Token and Pixel ID?

Yes, you may insert custom values into both the Access Token and Pixel ID fields.

Why does the {{Order.Amount}} custom value not work with the Order Form Submission trigger?

Because Order Form Submission fires before payment is captured, the order amount is not final. The {{Order.Amount}} value is only available after the Order Submitted trigger.

Do I need to do anything for event deduplication?

No. HighLevel generates an eventId for each funnel event and includes it in the API call, allowing Meta to automatically deduplicate server and browser events.

What happens if the contact lacks Facebook attribution data?

The workflow action will still run in HighLevel, but Meta may not receive or correctly attribute the conversion.

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.