Silent failure during setup caused by blocked third-party cookies
After struggling with this setup for far too long, and after the usual experience of trying to get help from the Meta Help Center (which was, unsurprisingly, not very helpful), I finally found the actual issue. The connection process fails if your browser blocks third-party cookies. The setup appears to work, shows that WooCommerce is connected to Facebook, and then the popup just goes black or gets stuck. There are no useful error messages, no clear indication of what went wrong, and the plugin logs only show that the access token is missing afterwards. The solution was to temporarily allow third-party cookies in the browser, complete the Meta connection, and then disable them again. A simple warning in the setup screen would have saved hours of troubleshooting. Expecting users to diagnose a silent OAuth failure caused by browser privacy settings is not exactly a great user experience.
Fatal error caused by JSONResponse
I’m experiencing a fatal error related to the JSONResponse constructor in the Facebook for WooCommerce plugin. The plugin calls this function without the required argument, causing a site-breaking error when used alongside Elementor. Deactivating the plugin resolves the issue. Both plugins are up to date, but this conflict still exists.Additionally, I’m currently unable to create a support topic on the official forum to report this problem, which makes getting help difficult. Please look into this critical issue and provide a fix soon.
Causes new and new problems in every day
With every update this is getting worst
Crash my website
I spent more than 7 hours today trying to keep a WooCommerce store online. The server was stuck at 100% CPU, pages hung for minutes, and in the end the only thing that worked was restoring an older backup. It was an exhausting day, with a client waiting for a store that needs to sell. While troubleshooting, one thing that concerned me was how much work is tied to product updates. With Meta for WooCommerce, saving a product can trigger catalog sync work. A store with around 40 products and 220 variations means hundreds of saves on any bulk CSV import or stock update, and on modest hosting that kind of load is risky. What I'd like to see: All catalog sync moved to a background queue (Action Scheduler), batched and rate-limited An option to pause syncing during bulk imports Clear logs showing what the plugin is doing and how long each step takes Until sync is fully decoupled from product saves, I can't recommend it for stores on shared hosting. I build WooCommerce stores professionally. If the Meta team wants help designing an optimized, queue-based sync, I'm available to be hired for that.
devdantas
October 3, 2026
|
1 reply
Caused multiple site crashes
Not built with the performance or stability of larger WooCommerce stores in mind whatsoever. We ran this on a dedicated VPS with 8 CPU cores and 24 GB RAM, and its catalogue/feed syncing brought the site to its knees on more than one occasion. The plugin handles catalogue syncing, feed generation, Meta tracking and related background processes, but provides no useful control over batching, throttling or scheduling resource-intensive sync jobs. In our case, catalogue/feed activity coincided with extremely aggressive meta-externalads crawling of the store, including hundreds of requests per minute. Combined with the plugin's own sync/background workload, this generated enough load to destabilise Redis/object caching and make both the storefront and WordPress admin extremely slow or unavailable. Disabling the plugin immediately restored normal performance. There are also numerous reports from other users involving failed feed-generation jobs, repeated scheduled-action retries, excessive CPU usage and heavy catalogue syncing. For a small catalogue it may be fine, but I would be very cautious about running it on a larger WooCommerce store. We ultimately replaced it with separate dedicated plugins for Meta Pixel/CAPI tracking and catalogue feed generation, giving us much better control over each process.
Jonas
August 20, 2026
|
1 reply
Not Connecting
Still trying to connect this plugin to the facebook page… 2 days in… not working…. WTF is wrong with META?
Crash my website
I spent more than 7 hours today trying to keep a WooCommerce store online. The server was stuck at 100% CPU, pages hung for minutes, and in the end the only thing that worked was restoring an older backup. It was an exhausting day, with a client waiting for a store that needs to sell. While troubleshooting, one thing that concerned me was how much work is tied to product updates. With Meta for WooCommerce, saving a product can trigger catalog sync work. A store with around 40 products and 220 variations means hundreds of saves on any bulk CSV import or stock update, and on modest hosting that kind of load is risky. What I'd like to see: All catalog sync moved to a background queue (Action Scheduler), batched and rate-limited An option to pause syncing during bulk imports Clear logs showing what the plugin is doing and how long each step takes Until sync is fully decoupled from product saves, I can't recommend it for stores on shared hosting. I build WooCommerce stores professionally. If the Meta team wants help designing an optimized, queue-based sync, I'm available to be hired for that.
devdantas
October 3, 2026
|
1 reply
Not a good plugin
Warning: This plugin may cause your pixel to disappear from Ads Manager and affect your campaigns. If this happens, you will need to reconnect it through your Business Manager settings. It is not compatible with PixelYourSite, even though PixelYourSite claims otherwise.
isaacureta
September 6, 2025
|
1 reply
Caused multiple site crashes
Not built with the performance or stability of larger WooCommerce stores in mind whatsoever. We ran this on a dedicated VPS with 8 CPU cores and 24 GB RAM, and its catalogue/feed syncing brought the site to its knees on more than one occasion. The plugin handles catalogue syncing, feed generation, Meta tracking and related background processes, but provides no useful control over batching, throttling or scheduling resource-intensive sync jobs. In our case, catalogue/feed activity coincided with extremely aggressive meta-externalads crawling of the store, including hundreds of requests per minute. Combined with the plugin's own sync/background workload, this generated enough load to destabilise Redis/object caching and make both the storefront and WordPress admin extremely slow or unavailable. Disabling the plugin immediately restored normal performance. There are also numerous reports from other users involving failed feed-generation jobs, repeated scheduled-action retries, excessive CPU usage and heavy catalogue syncing. For a small catalogue it may be fine, but I would be very cautious about running it on a larger WooCommerce store. We ultimately replaced it with separate dedicated plugins for Meta Pixel/CAPI tracking and catalogue feed generation, giving us much better control over each process.
Jonas
August 20, 2026
|
1 reply
Caused multiple site crashes
Not built with the performance or stability of larger WooCommerce stores in mind whatsoever. We ran this on a dedicated VPS with 8 CPU cores and 24 GB RAM, and its catalogue/feed syncing brought the site to its knees on more than one occasion. The plugin handles catalogue syncing, feed generation, Meta tracking and related background processes, but provides no useful control over batching, throttling or scheduling resource-intensive sync jobs. In our case, catalogue/feed activity coincided with extremely aggressive meta-externalads crawling of the store, including hundreds of requests per minute. Combined with the plugin's own sync/background workload, this generated enough load to destabilise Redis/object caching and make both the storefront and WordPress admin extremely slow or unavailable. Disabling the plugin immediately restored normal performance. There are also numerous reports from other users involving failed feed-generation jobs, repeated scheduled-action retries, excessive CPU usage and heavy catalogue syncing. For a small catalogue it may be fine, but I would be very cautious about running it on a larger WooCommerce store. We ultimately replaced it with separate dedicated plugins for Meta Pixel/CAPI tracking and catalogue feed generation, giving us much better control over each process.
Jonas
August 20, 2026
|
1 reply
Not Connecting
Still trying to connect this plugin to the facebook page… 2 days in… not working…. WTF is wrong with META?
They don’t care or maintain this plugin.
I keep reporting many issues with this plugin but they don’t care or reply.
