Hello @mluppert,
With the PixelYourSite integration active, these scripts should indeed be blocked by default. The strange thing is that I’ve just seen this working on the site of another user, so I would expect it to work for you as well.
Could you try manually adding pysOptions as the URL to block under Complianz > Integrations > Script Center > “Block a script, iframe or plugin”?
You should end up with a configuration like below:
If that doesn’t seem to work yet, could you also try ruling out a potential conflict with another active plugin on the site? An easy way to check would be by activating the Health Check & Troubleshooting plugin, navigating to Plugins > Installed Plugins and clicking “Troubleshoot” under Complianz.
The above will open a testing session with only Complianz activated, and you can check if the behavior still occurs in that case. If it doesn’t, that will tell you that another active plugin is related.
Let me know if that works for you, or if further assistance would be required with this.
Kind regards,
Jarno
Hi Jarno,
thank you so much for the detailed answer.
I tried all of that, however, the error persists. It also does when activating “Troubleshoot” for Complianz. Which is weird, because I thought it deactivates all plugins (also Pixelyoursite) which should result in removed FBP Cookies, right?
Any other ideas?
Cheers
Maximo
Hello @mluppert,
That should work under normal circumstances, but I noticed that the <body> element on your site does not include <body data-cmplz=”1″> as I would expect. When this part is present, it indicates that Complianz’s cookie blocker has parsed the page; but that doesn’t seem to be the case here.
Indeed, if the PixelYourSite plugin was disabled due to the activated Troubleshooting mode, but the pixel was still being placed by PixelYourSite during that time, it shouldn’t have been able to place the pixel code any longer. That would lead me to suspect that there might be caching functionality involved, which would need to be cleared before the changes are reflected.
Could you check if the behavior persists upon clearing/purging the cache in any caching tools and CDN’s?
Kind regards,
Jarno
Hi Jarno,
thanks again for your answer and the help. I have disabled the Server Cache and I have also visited the site using a parameter to disable the Plugin Cache as well: https://www.gartenlust.eu/?nowprocket
Still I do see all of the FBPixel cookies without opt in. Any other ideas?
Cheers and thanks.
Maximo
Is there maybe a different Facebook Pixel Plugin we might try?
Hi @mluppert,
I don’t suspect that the use of the PixelYourSite plugin is what’s causing the issue in this case, because of what I described earlier:
I noticed that the <body> element on your site does not include <body data-cmplz=”1″> as I would expect. When this part is present, it indicates that Complianz’s cookie blocker has parsed the page; but that doesn’t seem to be the case here.
As I haven’t been able to replicate this behavior on my own environments thus far:
The best course of action would be to narrow down the cause of the issue by disabling plugins one-by-one (and temporarily switching the theme back to a default theme, such as one of the Twenty Twenty- themes), until the issue no longer occurs. At that point you’ll know exactly which one of them was causing it, and we can work from there.
Kind regards,
Jarno
Hi @mluppert,
We haven’t heard from you in a while, is the issue resolved? We are happy to help you further.
Kind regards, Kim van Dijk
