For PixelYourSite Professional click here

For Product Catalog Feed click here for the documentation, and watch video tutorials here.

For WordPress Feed for Dynamic Ads click here

For WooCommerce Cost of Goods click here

PixelYourSite has full support for Google Consent Mode V2: click here to find more

It’s possible for Meta to show warnings telling you to send more parameters like email, name, phone numbers, and so on with your API events.

What you must know is that we do this every time that is possible. That is, when we have such data about a user triggering an event. We can do it for logged-in traffic, WooCommerce or EDD clients, and users that send a form with such information. We can’t do it for anonymous visitors that simply view some pages on the site. 

That is why general events will have a lower EMQ score, while events closer to a conversion tend to have a better score.  

We have this dedicated page with more details, please check it!

PS. We will no longer answer general questions about the topic. Ex: “Why I have these warnings?”; “How can I send the data that Meta want’s me to send?”. 

Some users reported Meta warnings prompting them to send IPv6 format with their events. Please watch this video for more details.

In essence, we always send the IPv6 address if a user has it. However, not all users have IPv6 IPs, some internet providers still relying on IPv4 format only. There is not much you can do about it. 

It’s possible to encounter a warning about a lower percentage of events receiving the ‘fbc’ parameter. This parameter is included only for events initiated by visitors who arrive via Meta ads. Privacy settings may also influence its presence. For websites with diverse traffic sources, the occurrence of the ‘fbc’ parameter is expected to be lower. Additionally, general events like ‘PageView’ are likely to have a reduced incidence of this parameter because they are triggered by all visitors to your website.

First of all, these deduplication warnings can be a false positive. 

The deduplication parameter is the Event ID, and our plugin ALWAYS ads it to each event. 

First of all, test your events as explained in this video: WATCH VIDEO

If some of your events don’t get deduplicated, try to understand how are those fired, because they are most likely not added using our plugin.

Testing on a live website can be tricky. You will see a number of deduplicated server events from your real users, and probably some processed server events too. That’s because the testing tool will not show you events fired in a different browser session, but will show your server events as long as the testing code is used.

IMPORTANT: Don’t add events outside the plugin, don’t install the pixel by other means. This is quite common! So, don’t use GTM, don’t add events with Events Manager events tool, don’t enable automatic events inside Events Manager.

From time to time, Facebook will show some warnings related to CAPI events. Most of these warnings are false positives, probably related to bots. 

Please review this page, especially the second video and the last part of the text: click here

Please watch this video to learn how to control events values: click to watch

If you think your Facebook conversions are counted twice, please watch this video: click to watch

We also recommend you to read this article about possible conversion errors and how to fix them.

• If you have questions about Facebook Ads reports, please read this article about how to create custom reports and track each event individually

Facebook Pixel Helper can show you this message even when the events work fine. What you can do:

1. Test in an incognito browser window.
2. Test inside Events Manager, as explained in this video: watch video

Another common cause for the issue is a consent plugin that blocks the browser events before consent is given. We recommend watching this video: watch video

If you have errors reported by the Pixel Helper Chrome extension please read this article first

If you just installed the pixel on your site but you can’t see it with Pixel Helper, make sure that you delete the site cache and you don’t test with an excluded role. It’s also important not to use an ad blocker since some of them are blocking the pixel. Please read this short article to find out more possible causes and solutions.

In order for us to test the Purchase event, please do the following:

If you use WPML, it’s possible that the Purchase event is not fired for some languages, depending on your setup.

This can be related to a known issue with WPML because they fail to declare the translated checkout page as a WooCommerce checkout page. More details here: https://wpml.org/forums/topic/is_order_received-function-call-fails-with-wpml/

If you have this issue, please contact WPML support and ask them to fix the issue.

“Potentially Violating Personal Data” – if you see this warning on Facebook, please watch this video.

If you use our WooCommerce or EDD feed plugins and the feed is not fully generated, this is usually related to an issue with your WordPress Cron.

• Please install this plugin: WP Crontrol
• Open Tools, and click on “Cron Jobs”.
• Search for “feed”. If there are warnings or messages about the cron jobs being delayed, this confirms the cron issue. It’s best to contact your hosting’s support and ask them to look into it. 

If you have any issues with the WooCommerce AddToCart event or button behaviour, please change the option mentioned in the following video, clear caches, and test: Click to watch video

If the ConsentMagic initial consent popup is visible on every page even after the user interacts with it, it’s probably a cache issue. Open the plugin’s Settings page, enable the Cache option and save. Clear all caches, and test.