Zapier + Facebook Conversions API Not Working

Hi @evanvance Nice to e-meet you.  While I don’t have too much familiarity with connecting to the Facebook Pixel via Zapier, one thing I have noticed is that sometimes, submitted a real response helps with testing the zap (versus having no actual responses submitted in the form). Would you mind submitting a real response on your form to see if this helps? 

Hi Liz, thanks for your prompt response. I did in fact submit real data minutes before doing any of this :(

Hi @evanvance Hm, shoot. One thing you could do in the meantime is look at the Task History to see if the data is passing into Zapier from Typeform or not at all. If you don’t mind sharing screenshots of the task history, I can take a look at it with you. 

A couple of things worth checking before you assume it's you.

First, Zapier successfully sending a test just means the API call didn't error out, it doesn't mean Facebook accepted the event as valid. Those are two different things, which is why you can get a green checkmark in Zapier but nothing in Test Events. Facebook can silently drop an event if the payload doesn't have enough matching data, even if the request itself went through fine.

That's probably the actual difference between your two Zaps. With Calendly you're sending name, phone, and email, so Facebook has enough to match against a user. With Typeform you're only sending name and phone. If that phone number isn't formatted correctly (E.164, and hashed properly), Facebook may just be discarding the event rather than throwing a visible error.

The other thing worth noting is that this won’t really get you a great event match quality score. 

On top of sending full personal data (name, email, phone) you also need to be sending things like the Facebook Click ID, Meta Cookie ID, IP address, User Agent, etc. None of which you can do with Zapier because it doesn’t capture them from the visitors browser. 

There are dedicated tools for this like Converly (note: I created it). It’s basically Zapier but dedicated to conversion tracking. It sends the name, email, phone, etc to Meta as well as the FBCLID, Meta Cookie IDs, IP address, etc which will get you a much better match rate (which will likely fix the issue you’re experiencing)