Issue with Facebook Pixel – Review potentially violating health data

Hi @developer12345 ,

Can you please let us know what’s the permalink structure of your site? You can check it by going to WP Admin > Settings > Permalink. If it is set to ‘Plain’ then please try setting it to ‘Post Name’ and then check if that resolves the issues.

Hi @wpnomad, thanks for your quick reply.

My permalink structure is a custom structure, it is set to /news/%postname%/

I just changed it to ‘Post name’, but this didn’t change anything. Do you have any other ideas?

Hi there @developer12345 ??

My permalink structure is a custom structure, it is set to /news/%postname%/

I just changed it to ‘Post name’, but this didn’t change anything. Do you have any other ideas?

Thanks for reaching back, clarifying further.

A picture is worth a thousand words, as the saying goes, therefore, could you also share a screenshot of the permalinks screen, please? https://snipboard.io/ is a good (online) tool of choice for sharing it here.

In order to investigate things further, could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select Get system report and then click the Copy for support button.?You can either paste it in your response here, or use https://pastebin.com/ for pasting it there and sharing it with us (as it provides additional paste settings).

Also, could you please navigate to WooCommerce > Status > Logs and from the dropdown on the right side, please see if there are any logs starting with the words fatal-error.

If so, please select View and copy and paste them into your reply here.

Looking forward to hearing from you!

Hi @anastas10s, thanks for your reply.

I made a screenshot of my permalink screen here: https://snipboard.io/kY06RX.jpg

The system statuscan be found here: https://pastebin.com/3vNiQnv9

For the logs, there are no logs at all.

If I understand correctly, the PageView events shouldn’t trigger on the checkout and search pages by default?

Hi there @developer12345,

Thank you for providing further information on this. The permalink settings are “textbook”.

The store’s System Status Report (SSR) points at a necessary plugin update, though.

Kindly update the Facebook for WooCommerce: door Facebook – 2.6.30 plugin to the latest version; currently version 3.0.6, directly linked here.

If I understand correctly, the PageView events shouldn’t trigger on the checkout and search pages by default?

Could you provide some further information on how you are testing for this, after updating the plugin to the latest version, please?

I trust that points you in the right direction, but if you have more questions, let us know. We’re happy to help.

Hi @anastas10s, I will update the plugin on the live environment. Tomorrow I will check this by logging into Facebook if we still have the error.

Hereby a screenshot of the error: https://snipboard.io/5Ecym0.jpg

I’ll let you know if the error is resolved after this, or if we still have issues. Thanks.

Hi @anastas10s, we still have the same error in Facebook Business. Please view attached screenshot: https://snipboard.io/2G5EXe.jpg

Just to be clear, the issue here is that we get an error in Facebook. It’s saying that we are sending personal data through the parameter values to Facebook. This is caused (i think) by the Pageview events.

One fix would be to disable these events on specific pages, like the checkout page. But we can’t change this since the events are fired from within the Facebook for Woocommerce plugin

Hello @developer12345,

Just to be clear, the issue here is that we get an error in Facebook. It’s saying that we are sending personal data through the parameter values to Facebook. This is caused (i think) by the Pageview events.

I only found this doc from Facebook and it only explains what the error is for.

At this point, a conflict test would be the best option to understand what’s causing the problem as your site is heavily customised.

You can perform one by:

Temporarily switch your theme to Storefront

Disable all plugins except for WooCommerce

Repeat the action that is causing the problem

If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

Let us know how it goes!

Hi @babylon1999, could you tell me exactly what is supposed to happen if everything is working well?

Should the Pageview events not fire on these pages? Or should they be there, but not send the parameter values?

A while back I already tried disabling all the plugins except for WooCommerce and Facebook for Woocommerce, and the issue was still there.

Hi @developer12345,

I confirm it’s normal for pageview events to fire on the cart and checkout pages as they’re indeed pages.

I took a look at the information you shared and it appears Facebook is detecting some parameters in your order received URL as sensitive data. Typically, the order key is passed in the order and it’s the first time I’m seeing it being detected as sensitive data on Facebook.

With that in mind, I took a look at your order received URL and noticed a few differences from mine. On my test site, the key is added after the order ID (Here’s a test order to check with – check the URL on the address bar, then place a test order on your site and compare the URL). However, in the screenshot you shared there are some URL parameters “removed&utm_nooverrde…” before the order key.

I believe the additional URL parameter may be responsible for the issue. Can you share some insights on the order source and the additional URL parameters on your order URL?

Hi @sukafia , thanks for your reply.

You said you noticed a few differences, but I don’t think there are any. In your test site, the key is added after the order ID. This is also the case for my website. In my screenshot, you can see the parameter and value: ?key=_removed. This is not the case on the website but I think Facebook Business adds this automatically. On the Diagnostics tab in Facebook Business it says the following: To protect the privacy of your users, we haven’t stored this data in our ad systems and you won’t be able to view or use it. I think this is the part where Facebook removes the parameter value and adds the _removed part.

So, the problem here is that we are getting unwanted errors in Facebook Business. Is this something that can be fixed? It doesn’t seem possible to exclude the PageView events on the checkout and search pages or to exclude parameters from sending to Facebook Business.

We could also ignore these errors, but I’m not sure if this will cause any problems in the future?

Thanks.

Hello,

For better assistance, please contact us at WooCommerce.com > My Account > Support. You may need to create an account before you can access that page.

Please include a link to this forum thread as well as a new copy of your site’s system status report in your response.

Best.

Hi @ihereira , thanks for your reply, but this is not a WooCommerce issue. There is nothing wrong with the WooCommerce installation. Besides, the sensitive data also gets send to Facebook on the search pages, which aren’t WooCommerce pages.

Hi,

For us to help you investigate further, please create a request by heading to WooCommerce.com > My Account > Support.

Please include a link to this forum thread in your response, we’ll be glad to help.