I am using the Meta for WooCommerce plugin and encountered several technical issues that affect my catalog health:

1. Source Conflict: The plugin creates multiple data sources (Feed and Batch API) for the same catalog, leading to a “property_blocked_by_source_prioritization_processor” error. This blocks attribute updates for all items.
2. Invalid Video Field: The plugin sends invalid values for the “video” property even when no video is present, resulting in “Invalid values: video” errors in Commerce Manager.
3. Product Matching: These issues cause a “Product matching events are missing” warning, as the pixel cannot reliably match events with catalog items due to the prioritization conflict.

Please fix the data synchronization logic to avoid these conflicts.

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.

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.

Still trying to connect this plugin to the facebook page… 2 days in… not working…. WTF is wrong with META?

I keep reporting many issues with this plugin but they don’t care or reply.

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.

This has to be one of the worst plugins in the WordPress repository. I can’t even get the configuration screen to load and whenever the plugin syncs with Meta it eats up almost all of my server’s resources (32 GB RAM, 8 core CPU…).

Adding one more review noting that it does not work. I get stuck in connecting the plugin through WordPress to my Facebook catalog. I get as far as clicking to continue to set up products – but it just closes the window for Facebook and takes me back to the admin page to ‘get started’ again with connecting my shop to Facebook & Instagram. I have wasted 2 days trying to figure out the issue, so I’m done with it. I will have to use something else.

Mala experiencia: duplica eventos, soporte inútil, pésima y paupérrima

Always error try again. The support seems be absent.