Setting Up Facebook Conversions API

With Workflows, you can add Facebook Conversion event actions in automation to send conversion data back to Facebook without anyone being cookied by a Facebook pixel.

FAQs:


Which initial Workflow Triggers can I use the FB Conversions event with?

The Facebook Conversions API action only works with the following initial workflow triggers:

  1. Form Submitted
  2. Survey Submitted
  3. Order Submitted
  4. Order Form Submission
  5. Customer Booked Appointment


What should the "Facebook Conversions API" action step "Event Type" be set to?

The "Facebook Conversion API" must be set as a "Funnel Event" when you are sending data from your FG Funnels subaccount to Facebook, using any of the workflow triggers listed below:

  1. Form Submitted
  2. Survey Submitted
  3. Order Submitted
  4. Order Form Submission
  5. Customer Booked Appointment

Which Event Details Parameters do we need to use?

Event Source URL


Which Customer Information Parameters can we use?

Client IP address - do not hash

Client user agent - do not hash

Email Address

First Name

Surname

Browser ID (fbp) cookie – do not hash

Click ID (fbc) cookie – do not hash


Can I use Custom Values for the Access Token and Pixel Id?

Yes, Custom Values will work in those fields.


Why don't I see test events in Facebook Business Manager?

If you don't see a test conversion, check the Diagnostics tab for any errors. A common issue we've seen is when FB has blocked the domain, so check Settings > Scroll to the bottom to "Domains In Your Allow List," where you can approve the domain. 


Does the 'Test Workflow' button work with testing FB conversions?

As of a recent update, the system now supports the "Test Workflow" button to test FB Conversion API workflows.


Why is Facebook reporting the conversion as "Custom Event" when I selected "Lead"?

This happens when you send test data ( we're not sure why Facebook does this ), but it will show "Lead" when you run a live conversion.