Facebook Conversion API Events Are Not Firing from a Workflow

If your workflow includes a Facebook Conversion API step and no events appear in your Facebook Events Manager, the cause is almost always how the workflow is being tested or which trigger is used.

Do not rely on the test button

The workflow Test button runs a simulated pass and does not send a real conversion. Instead:

1. Save and Publish the workflow.
2. Complete a real action that matches the trigger, such as submitting the actual form with a test contact.
3. Check Events Manager for the event, allowing a few minutes.

Use a trigger that carries visitor data

Conversion events work best when the trigger comes from a real visitor action. Reliable choices include:

• Form Submitted
• Survey Submitted
• An appointment booked through the booking widget
• A two-step order form submission

Appointment trigger gotcha

For booked appointments, choose Customer Booked Appointment, not the general Appointment trigger. The general trigger covers many appointment changes, while Customer Booked Appointment is the one fired by the booking widget.

Lead value for purchases

If your step sends a Purchase event, a lead value is required. For other event types you can leave it blank. A missing value is a common reason purchase events are rejected.

Checklist

1. Workflow is published, not just saved as a draft.
2. Trigger is one of the input-based triggers listed above.
3. The booking trigger is Customer Booked Appointment.
4. Lead value is filled in for Purchase events.
5. Your Facebook account and pixel or dataset are connected in Settings > Integrations.
6. You tested using a real submission, not the test button.

Still not working?

Open the workflow's Execution Logs to confirm the contact reached the step, then compare the event name and pixel ID with what Events Manager expects.

Good to know: Allow several minutes for new events to appear, and filter Events Manager by the exact event name you configured.