FB cookies load despite blocking via script center

And here a screenshot of the script center: https://prnt.sc/wl9i5n

Hi @tomkelly33,

The best way to see if there are any cookies present is in the browser itself; https://snipboard.io/mgBGMn.jpg

For Chrome, you can click on the lock in front of your URL, when you visit incognito and see what cookies are present on first load.

Unfortunately, cookies scans mostly have a double agenda, and do not consider regions, specific configurations etc

To see which API’s, or external URL’s are requested, you can look in your console, right-click, inspect -> Sources.

https://snipboard.io/tHoEAP.jpg

Hope this helps,

regards Aert

Hi Aert,
Thanks that helped a lot.
The funny thing is that most cookie scanners say that the site is compliant but the one I use goes into most depth and usually finds issues anyway ??
So I found out that the external Facebook and Google analytics loading probably comes from the embedded URLs on the privacy policy page here: https://immobilien-liebe.com/datenschutzerklaerung/
Can I block/deactivate all those hyperlinks via Complianz script center?

I investigated further and found that for some reason the scanner believes that Facebook.com is a subpage of the website and thus finds all those false positives. As if FB’s start page was hyperlinked in the main navigation menu, very strange. By now I think this is rather a bug of the scanner than of Complianz. Would you agree? You can test the scanner here: https://wwwschutz.de/demo/wwwschutz-ki-check-public-p4/start.php?url=https://immobilien-liebe.com/

Just to confirm I used another scanner (consentmanager.net) and it also finds FB not getting blocked, see here: https://prnt.sc/wltr83
So how can I block those 2 cookies using Complianz or are those false positives as well?

Hi @tomkelly33,

The embedded URL’s won’t cause any tracking, they will need specific parameters and requests to work.

I think the most logical explanation is the following, and please check your own browser instead of scanners that have a pricing option.

In your page source, there’s a Facebook Pixel script, if the scan recognizes the script it might trigger a false positive because it doesn’t recognize it’s controlled by Complianz; the first part

<script class="cmplz-script" type="text/plain"> Is how we block the scripts.

I’m 99% sure most scanners do not check if the script is controlled, only if the script is present.

<script class="cmplz-script" type="text/plain">!function(f,b,e,v,n,t,s)
{if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};
if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';
n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];
s.parentNode.insertBefore(t,s)}(window,document,'script',
'https://connect.facebook.net/en_US/fbevents.js');
 fbq('init', '***'); 
fbq('track', 'PageView');</script>

Ok, Aert, thanks for your help!
The first scanner company got back to me and had to admit that it was a bug on their part. So all seems well and perfectly blocked.
Cheers