Sol J. a11n

Hi there @angeklics

Thanks for your question.

Your server is sending an invalid fn parameters value for your ViewContent event. This may be because there was an error in the parameter value.

I checked the site on incognito browser window, and I didn’t see any error when using Facebook pixel helper:

Full Size: https://d.pr/i/7DdX8I

Could you please click troubleshoot pixel, as indicated with the arrow, and then share more info from Facebook side if there is any more specifi info on how to resolve it?

Look forward to your reply

Hi @jsmoriss

Thanks for your valuable feedback.

We’re trying our best to improve our plugin.

Anyway, I don’t see any actual issue mentioned here. We’re happy to look into detailed feedback you could provide for our improvement.

Feel free to provide us with more details of your issue so we can help further, or submit your ticket directly on WooCommerce.com by creating an account using WordPress.com

@th668

my woocommerce site been connected with the facebook page. everytime i import a new product to woocommerce, it works well to sync and also make the item available on the facebook catalouge.

That’s great!

but, i have deleted some items from the facebook catalogue accidentally.

Sure, the solution is to resync the product so the deleted products on your catalog can be re-created when WooCommerce makes another sync.

Please do this:

Navigate to Marketing > Facebook > Product sync, then press the sync product. Please check this screenshot if you’re still unsure.

Once that’s done.

Please go to your Catalog page in Commerce Manager in your Facebook Business Manager.

Do let me know if that resolves your issue.

Hi @drakars

That’s really odd.

I have my own test site and ViewContent event is fired correctly and shown in FB Pixel Helper.

I checked your product page source code, and found this:

`<!– Facebook Pixel Code –>
<noscript>
<img
height=”1″
width=”1″
style=”display:none”
alt=”fbpx”
src=”https://www.facebook.com/tr?id=3702133669867028&ev=PageView&noscript=1&#8243;
/>
</noscript>
<!– End Facebook Pixel Code –>

It appears to be an additional FB tracking script, can you please remove it from your Avada Footer Script?

That could undermine the FB for Woo plugin to work properly activating pixel events.

Also, please ensure clear any cache if you use caching plugins.

@cbetteley

Thanks for sharing your site status report.

The solution for this is to reset everything on Facebook for Woo and then try to reconnect.

To do that we need to manually empty the data used for the previous connection to Facebook.

Please go to https://yoursitedomain.com/wp-admin/options.php and then search the following fields, and empty each field value then scroll down to click the save button.

wc_facebook_external_business_id
wc_facebook_system_user_id
wc_facebook_business_manager_id
wc_facebook_commerce_merchant_settings_id
wc_facebook_page_access_token
wc_facebook_page_id
wc_facebook_pixel_id

Then please try to reconnect!

Let me know how it goes.`

@gronex

Please kindly create a separate forum thread so we can focus on a case at a time.

Hi @freshuk

Thanks for sharing more info on the context.

I checked your site homepage, and try the bundle product, which has a direct add to cart link, and yes it loads a bit longer.

However, it appears that you’re using this plugin: WPC Fly Cart for WooCommerce. Is that correct?

The best way to find out the real cause of that behavior is actually to do a conflict test, more on conflict test can be found here.

For now, I’d recommend you do the following:

• Disable WPC Fly Cart for WooCommerce, and test again if that resolves it. If not, do the next step.
• Disable all plugins except WooCommerce and Facebook for WooCommerce, if you’re not comfortable doing it on the production site, you can create a staging site and do it there. Please ensure that the sync mode is disabled on the staging site, for Facebook for WooCommerce, in this section Marketing > Facebook > Product sync (uncheck it), to avoid products from your staging get synced to Facebook catalog as well.
• Test again clicking the product bundle

I hope that helps!