Facebook Conversions API (CAPI) allows you to send conversion events from HighLevel workflows directly to Meta. This helps you track customer actions, such as form submissions, appointments, purchases, and lead updates, even when browser-based tracking is limited.
With the Facebook Conversions API workflow action, you can send conversion information to Meta based on the workflow triggers you configure.
This article explains which workflow triggers are supported, how to configure the Facebook Conversions API action, how conversion tracking works, and how to troubleshoot common issues.
TABLE OF CONTENTS
- What is Facebook Conversions API in Workflows?
- Supported Workflow Triggers
- How to Set Up Facebook Conversions API in Workflows
- Troubleshooting Facebook Conversions API Workflows
- Frequently Asked Questions
- Related Articles
What is Facebook Conversions API in Workflows?
Facebook Conversions API is a server-side tracking method that sends conversion events from HighLevel to Meta.
Unlike the Meta Pixel, which tracks activity through a visitor's browser, Conversions API sends event information through a server connection. This can help capture events that browser restrictions or ad blockers might otherwise prevent from being recorded.
You can use Facebook Conversions API workflows to:
Track form and survey submissions.
Track appointments booked through a calendar widget.
Send conversion events from order form submissions.
Send lead conversion events based on supported workflow triggers.
Track later customer actions using Facebook attribution information already associated with the contact.
Important: A workflow action running successfully does not always mean Meta can attribute the conversion to an advertisement. Valid Facebook attribution information is needed for the applicable event.
Supported Workflow Triggers
The workflow triggers you can use depend on the event type selected in the Facebook Conversions API action.
Funnel Event Triggers
For Funnel Events, you can use the following workflow triggers:
| Workflow Trigger | Description |
|---|---|
| Form Submitted | Runs when a contact submits a form. |
| Survey Submitted | Runs when a contact submits a survey. |
| Customer Booked Appointment | Runs when a customer books an appointment through a calendar widget. |
| Order Form Submission | Runs when a customer submits an order form. |
Important: For appointments booked through a calendar widget, use Customer Booked Appointment, not the general Appointment trigger.
The Customer Booked Appointment trigger is designed for widget-based bookings, while the general Appointment trigger covers broader appointment activities.
Lead Event Triggers
For Lead Events, commonly used workflow triggers include:
Facebook Lead Form Submission
Pipeline Stage Change
Other contact-based triggers, such as Contact Tag Added, Opportunity Status Changed, and Contact Changed, may also be used when the contact has valid Facebook attribution information.
However, available triggers and event eligibility may depend on the selected connection type and event configuration.
Important: The workflow trigger does not create Facebook attribution information. The contact must already have the relevant attribution data for Meta to associate the conversion with the Facebook interaction.
Example: Tracking a Later Customer Action
Suppose a customer submits a Facebook lead form and is added to HighLevel with Facebook attribution information.
Later, the customer moves to a different pipeline stage.
A workflow using the Pipeline Stage Change trigger can run a Facebook Conversions API action using the Facebook attribution information already stored against that contact.
This allows you to track later conversion activity without requiring the customer to submit another Facebook lead form.
How to Set Up Facebook Conversions API in Workflows
You can configure a Facebook Conversions API workflow by choosing a supported trigger, adding the conversion action, and providing the required Meta connection details.
Step 1: Create a Workflow
Open your HighLevel sub-account.
Navigate to Automation > Workflows.
Click Create Workflow.
Create a new workflow.
Click Add New Workflow Trigger.
Select the trigger that matches the customer activity you want to track.
Configure the required trigger filters and save the trigger.
For example, select Form Submitted when you want to track submissions from a specific form.
Step 2: Add the Facebook Conversions API Action
Click Add your first Action or the + icon in the workflow.
Search for Facebook Conversion API.
Select the action.
Choose the appropriate Event Type, such as Funnel Event or Lead Event.
Configure the connection and event settings.
The required configuration depends on your selected event type and connection method.
Step 3: Configure Your Meta Connection
If you are using a connection that requires manual credentials, you will need the Access Token and Pixel ID associated with your Meta data source.
To obtain the Access Token:
Open Meta Events Manager.
Select the appropriate data source.
Open Settings.
Locate the Conversions API section.
Generate and copy the Access Token.
Paste the token into the corresponding field in HighLevel.
To obtain the Pixel ID:
Open the same data source in Meta Events Manager.
Locate its Dataset ID or Pixel ID.
Copy the ID.
Paste it into the Pixel ID field in the workflow action.
If you use the Ad Manager connection option, available pixels are populated from the connected Ad Manager account, and you do not need to manually generate and enter the Access Token for that connection method.
Note: HighLevel also supports Custom Values in the Access Token and Pixel ID fields for configurations that use these fields.
For detailed connection instructions, see How to Set Up a Funnel Event Pixel for Facebook Conversion API.
Step 4: Save and Publish the Workflow
Review the selected workflow trigger.
Confirm the Facebook Conversions API action settings.
Save the action.
Save and publish the workflow.
Perform the corresponding customer action to test the workflow.
For example, if you selected Form Submitted, submit the associated form to check whether the workflow runs and sends the configured conversion event.
Troubleshooting Facebook Conversions API Workflows
If your Facebook Conversions API workflow is not working as expected, check the workflow configuration, selected trigger, event details, and available attribution information.
Issue 1: Facebook Conversions API Workflow Is Not Triggering
Possible causes:
The workflow has not been published.
An incorrect trigger was selected.
The trigger filters do not match the customer action.
The expected customer action has not occurred.
How to troubleshoot:
Open the workflow under Automation > Workflows.
Confirm that the workflow is published.
Review the selected trigger and its filters.
Perform the customer action associated with the trigger.
Check whether the workflow executes.
For Funnel Events, use the appropriate submission trigger:
Form Submitted
Survey Submitted
Customer Booked Appointment
Order Form Submission
Example: If you want to track a customer booking an appointment through a booking widget, select Customer Booked Appointment instead of the general Appointment trigger.
Issue 2: Purchase Event Is Not Working
Purchase events may require additional configuration depending on the selected event type.
For a Lead Event where the Stage Name is Purchase, HighLevel requires:
Value: The monetary value associated with the event.
Currency: The currency associated with that value.
The Value field supports a static value or a custom field, and the Currency field is selected from a dropdown.
These fields are required for the documented Lead Event Purchase configuration.
For other event configurations, check the available fields and requirements before leaving a purchase-related value blank.
Issue 3: Test Events Are Not Appearing in Meta Events Manager
If a conversion event does not appear in Meta Events Manager, review the event configuration and available diagnostics.
Open the appropriate data source in Meta Events Manager.
Check the Diagnostics tab for reported errors.
Confirm that the correct Pixel ID or dataset is configured.
Check that the Access Token is correct when using a manual connection.
Review the event configuration and attribution information.
Check whether the event's website domain is restricted.
A domain restriction may prevent events from being accepted.
To check domain permissions, open the data source's settings in Meta Events Manager and look for Domains in Your
Allow List.
If the relevant domain is restricted, review the domain settings and allow the appropriate domain.
Testing note — Needs Confirmation: Existing HighLevel documentation contains conflicting instructions about the Test Workflow button. One article confirms that the button works for Facebook conversions, while the older troubleshooting article advises against using it. Until this behavior is verified, use a published workflow and perform an actual qualifying customer action as the recommended troubleshooting method.
Issue 4: Facebook Attribution Information Is Missing
Facebook Conversions API workflows can use attribution information associated with the contact.
Relevant information may include:
Facebook Click ID (
fbclidorfbc)Paid Social (Facebook) attribution
Other supported customer information parameters
If a contact originally entered HighLevel through a Facebook advertisement, the relevant attribution information may already be stored against that contact.
A later workflow triggered by a tag change or opportunity update can use the available attribution information.
However, if the contact has no valid Facebook attribution information, the workflow action may execute without Meta
being able to attribute the conversion correctly.
Example:
A customer originally enters HighLevel through Google Search.
Later, the same customer interacts with a Facebook advertisement and submits a Facebook form.
The contact's latest attribution information may now include Facebook attribution data.
A subsequent workflow action can use that information when sending a conversion event to Meta.
Issue 5: Order Amount Custom Value Is Not Working
The {{Order.Amount}} custom value works with the Order Submitted trigger because the trigger is associated with a completed payment.
It does not work with Order Form Submission, which runs before the payment has been processed.
If you need the finalized order amount, use the appropriate completed-order trigger in a workflow configuration that supports it.
Frequently Asked Questions
Q. Which workflow triggers support Facebook Conversions API?
Supported triggers depend on the selected event type. Common Funnel Event triggers include Form Submitted, Survey Submitted, Customer Booked Appointment, and Order Form Submission. Lead Events can use supported contact-based triggers when valid Facebook attribution information is available.
Q. Why is my Facebook Conversions API workflow not working?
Check that the workflow is published, the correct trigger is selected, and the Facebook Conversions API action is configured correctly. Verify the Meta connection, Pixel ID, and any required attribution information. Check Meta Events Manager for diagnostic errors.
Q. Can I use the Test Workflow button to test Facebook Conversions API events?
Existing HighLevel documentation contains conflicting instructions about this feature. Until its current behavior is confirmed, the recommended approach is to publish the workflow, perform the actual customer action (such as submitting a form), and check the event in Meta Events Manager.
Q. Is Lead Value required when sending Purchase events?
For a Lead Event with the Stage Name set to Purchase, both Value and Currency are required. Other event configurations may have different requirements.
Q. How does Facebook Conversions API prevent duplicate events?
HighLevel automatically handles event deduplication for supported funnel events by sending an available event ID to Meta. Meta uses matching event IDs to identify browser and server events representing the same conversion, helping prevent duplicate counting.
- The associated domain is not blocked.
Related Articles
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article