50% of Value for Purchases are not showing on Facebook

Very unusual.

Please test your purchase events: place an order and user Pixel Helper Chrome extension to check the Purchase event value parameter. Do you see something wrong?

Value parameter is normal value:?265

I found other problems, Add to cart event is fired twice

https://imgur.com/prMHvsH

Event matching:

Click ID (fbc) 58.73%

View content Country Hashed:
You’re sending a hashed country code that can’t be found in the ISO 3166 set. To fix this issue, make sure you send a hashed country code as a two-letter code in lowercase. For example: us

I found other problems, Add to cart event is fired twice

The first ATC event in your screenshot is not fired by our plugin.

• Make sure you have Events Manager “events without code” option turned OFF.
• Make sure you don’t fire events by other means (custom code, other plugin, GTM, etc).

View content Country Hashed:
You’re sending a hashed country code that can’t be found in the ISO 3166 set.?

We take the country code from WooCommerce directly, and they are usually correct. It’s probably just a false positive.

Track events automatically without code option is disabled, i deactivated PixelYourSite and cleared cache then tested again and i didn’t find any code fired on add to cart so i believe the source is PixelYourSite.

Can it be a conflict with Litespeed Cache? do you have documentation on how to use both together?

I switched from WP Rocket to LiteSpeed Cache because it is much faster and since I did that I get many problems with the tracking codes

Like Reduce unused JavaScript, Serve static assets with an efficient cache policy, and Avoid long main-thread tasks?

Also Conversion API is sending twice the data sent by the browser tracking code, here in Egypt people don’t use Ad Blocker or iOS devices as much.

Also the browser console is showing errors in Facebook and Google code
https://imgur.com/cANL5JC

The source is absolutely not our plugin, that event doesn’t have our usual parameters.

This looks like a known bug Meta still has for some pixels where events are wrongly and automatically fired. They fixed the bug in the past, but it looks like it manifest itself for a small number of pixels. As far as I know, they are looking into it. Unfortunately there is nothing we can do on our end.

A possible solution is to replace the pixel with a new one. It’s not ideal, especially if you have an old pixel with valuable data.

Today i found problems when inspecting:

We detected event code but the pixel has not activated for this event, so no information was sent to Meta. This could be due to an error in the code, but could also occur if the pixel fires on a dynamic event such as a button click.Learn more

An error occured while the tag was fired: net::ERR_BLOCKED_BY_CLIENT

Something is defiantly wrong i think it’s a conflict with LiteSpeed Cache

What should i do? please help me.

It’s best to open a new topic for for each new problem.

And it would also help to share the site URL, so I can take a look. This might be cache related, or something else. A consent plugin can be the cause, but I need to be able to check.

You can also debug it yourself by disabling plugins one by one until the pixel gets fired. It will help you find out if there is a conflict with another plugin. Testing with a default theme can help too, in case the theme is the problem. I would start with the cache plugin, and any consent plugin you might use.