AddToCart and Purchase: Duplicate events in API and also in pixel

Hi Jess

Just to let you know I have resolved this issue.

Previously I had the facebook for woocommerce plugin installed and fully integrated and was only getting the standard browser events sent through and no issues with duplicates.

Since upgrading there appears to be a new api conversion element within the plugin which is not obvious – it looks like the existing browser integration so really confusing. I have managed to turn it off so the issue with additional events has gone. There is still an issue to investigate as to why the conversion api was creating events which were then not showing in the event manager – because they were not showing we couldn’t edit them to prevent the duplication – so we have just had to turn it off.

I have configured the plugin on the main ‘configuration’ page ensuring the pixel ID, account, page details etc are all setup and then saved them but then I have disconnected the Facebook and woocommerce integration and this seems to have cut off the conversion api events – putting me back to where I was before was just the browser events coming through.

Obviously I want to get the conversion api setup at some point and the issue mentioned above needs investigating but this fix ensures onyl the correct events are coming through and hiopefully means we can get our ads back on track.

Hope this helps

Howdy @jesskumanovski,

I’m guessing that Facebook is showing you a message that indicates that event_id parameter is missing from the tracking data similar to:

If I’m understanding correctly, I’ve just done some testing of this on my own test site here: https://wctesting.tk/product/beanie-with-logo/. I used this plugin: https://github.com/WillBrubaker/maybe-route-request-through-moesif to capture the request that was sent to the FaceBook conversions API and I used the Facebook Pixel Helper Chrome browser extension to view the data that is sent using the FaceBook Pixel. With all of that in place, I added an item to my cart. The pixel event shows that the event_id parameter is populated:

https://d.pr/i/6VmwaF
Likewise, the request that was sent to the API also contains a value in the event_id parameter:

https://d.pr/i/PuImih
I also had a look at the issue tracker here: https://github.com/facebookincubator/facebook-for-woocommerce/issues for any reports of this type of behavior caused by the Facebook for WooCommerce but I was unable to find any. This leads me to believe that this is caused by something external to WooCommerce or Facebook for WooCommerce. If you are able to provide the exact steps that can be taken to reproduce this behavior under the following conditions:

1. n unmodified, default WordPress theme such as Twenty Twenty or Storefront active.
2. No other plugins except for WooCommerce and Facebook for WooCommerce active.

Please do provide those steps and we can take a closer look.
We do understand that placing a site under those conditions may be disruptive. Many people maintain a staging copy of their site for exactly this purpose. That way, testing and troubleshooting can be done on the staging copy without disrupting the operation of the live site. If your host does not provide an easy way to set up a staging site, you might want to use something like the WP Staging plugin for this purpose.

Did we get this resolved?

I am having the same issue and don’t understand how to fix it?

Hi there @basique,

If you still have issues after testing under the conditions mentioned above, please create a new forum thread with the detailed issue:

1.an unmodified, default WordPress theme such as Twenty Twenty or Storefront active.
2.No other plugins except for WooCommerce and Facebook for WooCommerce active.