We are experiencing several issues with the ‘Facebook Pixel’ app inside Funnelish - More specifically, the ‘Facebook Conversions API’ feature.
The issues include:
Duplication issues
“Poor” event match quality inside Facebook purchase events
“Purchase” is being triggered upon “complete payment” button - even if the purchase is unsuccesful
“Purchase” is being triggered when customers reach checkout page but don’t actually purchase
Could we please have some help to diagnose this issue? We suspect it could be issues with the “Geo-Funnels” feature that is messing with the conversions API
Is a better alternative to NOT use the ‘Facebook Pixel’ app to track API conversions? And INSTEAD use a third party tool such as google tag?
Hi @tez , we have it in our roadmap to work on improving the app and currently are collecting feedback on it.
As for the issues mentioned:
1. Duplication issues
Please provide some samples, screenshots or ways we can reproduce the issue, this will help us tremendously in pinpointing where the issue comes from.
2. “Poor” event match quality inside Facebook purchase events
This is something we plan to work on, generally we do not send “phone numbers” to Facebook for one reason: because when the phone number is invalid or of the wrong format, Facebook will then drop the entire event (so it wont track anything for that customer), however now that we have developed better phone number validation this should be addressed in the next few days just in time for Q4 scaling session.
3. “Purchase” is being triggered upon “complete payment” button - even if the purchase is unsuccesful
This shouldn’t happen, again if you got some more details it will help us resolve the issue quickly.
4. “Purchase” is being triggered when customers reach checkout page but don’t actually purchase
Again, this should not happen, though we are aware of one single case where it would happen from the script side, when a customer goes to checkout and tries to purchase, but then the purchase fails and the customer goes to another step directly, this will cause the app to think that the purchase was successful thus triggering the pixel from the browser side… A quick solution for this that’s being considered is disabling purchase event triggering from the browser side and only triggering it from the CAPI side thus it’s more accurate.
Again if you can provide more details on the issues you are facing with CAPI or our FB app in general we are always open to improving it.
we have the same issues. Since some days the attribution performance dropped suddenly and the event data is very poor. Big increase on duplicates, purchase trigger without purchases, etc. etc.