I recently faced a frustrating issue with the Facebook Conversion API Workflow trigger not firing correctly during testing. After some trial and error, I learned a few important things that helped resolve the issue, and I want to share them with you so you don’t waste time troubleshooting the same things. If you’re running into the same problem, here’s what you need to know to fix it quickly.
Don’t Use the Test Workflow Button
The most common mistake I made, and many others make, is using the test workflow button when testing the Facebook Conversion API. This will not trigger the API as expected. Always make sure to save and publish your workflow before testing.
Choose the Right Triggers
To make sure the Facebook Conversion API Workflow trigger works properly, you need to choose an input trigger.
Here are some valid options:
- Form Submission
- Survey Submission
- Appointment Submission (from booking widget)
- Two-step order form
For appointments, be careful. Use “Customer Booked Appointment” as the trigger, not just “Appointment”. The general “Appointment” trigger won’t work for the widget. This distinction is crucial to getting the workflow to fire properly.
Lead Value Is Required for Purchase Events
If you plan to use a Purchase event in your workflow, ensure that you set the lead value. If you’re not using a purchase event, you can leave this field blank.
Test and Confirm
Once you’ve made these adjustments, test your API Workflow trigger again. After saving and publishing your workflow, it should trigger as expected with one of the correct input triggers.
Conclusion
To avoid running into issues with the Facebook Conversion API Workflow trigger not firing, follow these steps carefully. Save and publish your workflow, use the correct triggers, and ensure the lead value is set when necessary. These simple fixes should help your workflow run smoothly.
