Cookie Scan while Complianz is already active

Hi @matthiaswagner,

There is actually built-in functionality that accepts cookies within such iFrames, so that they get reported in the scan results.

Perhaps you have a JavaScript error somewhere that prevents the plugin from performing this action, and results in the need to manually click Accept and re-scan for cookies? You can open your browser’s developer tools during the Scan to see if any related errors appear, which could be the case here.

In any case, you might be interested to know that we intend to overhaul the Cookie Scan functionality in a future release of the plugin; so that it runs in a ‘headless browser’ and won’t require such iFrames any longer.

If you’d be willing to join as a tester for this functionality, let me know!

Kind regards,
Jarno

hy jarno,
thank you for your quick reply. we will keep an eye on this.
beta testing is currently not possible since limited ressources ??

matt

hy again!

we are still struggling with the cookie scan. it looks like the urls that are scanned are picked somehow random? in our case it often happens that urls to elementor templates or other stuff that are not complete frontend-urls are used.

i guess it would be good if those urls are picked from pages and posts to represent real web-urls?

i do not understand why, but in some of our sites now even the complianz-cookies are not found. we tried clearing and rescanning for cookies very often and also fresh new browsers :/

can you already tell when the new functionality with “headless browser” will be released? do you have any further hints for us?

it is annoying that some cookies are not found that are present in every page after opt-in.

thank you, matt

i have to add a few lines ??
i already found out how to limit the scanner to specific post types:

function my_complianz_custom_posttypes($post_types){
	//unset( $post_types['not_this_posttype'] );
	//return $post_types;
    return array(
        'page',
        'post'
    );
}
add_filter('cmplz_cookiescan_post_types', 'my_complianz_custom_posttypes');

but i still can say for sure that the scanner will display different results on some of our sites depending on if the banner has been accepted in the browser before scanning or not.
i am really looking forward to this new version of the scanner ??

Hi @matthiaswagner,

Note that some cookies are only set on specific interactions, an example could be after having clicked a specific link or element. Those interactions may not directly occur when running the cookie scan, so these cookies will be added to the results list at a later point in time. If the cookie is set in your browser it will also be detected by the scan.

Kind regards, Jarno

hy jarno,
thanks for your quick reply. in this case we are really only talking about cookies that will be set on page load.

since we are aware of this, we use only “fresh” browsers for the setup of the cookie table and accept everything before. but since this is not how it is supposed to work, we are interestind in when the new technology will be released?

matt

Hello @matthiaswagner,

I thought you mentioned the Complianz cookies as well, and not all of these are directly set on page load. I’d expect something similar for those cookies that don’t immediately appear, or perhaps an ad-blocking extension that could be related.

The plugin version that includes the alternative cookie scan method is currently still in our testing queue and planned for a future release, but as it’s a relatively high impact change; this really has to be tested thoroughly.

Kind regards, Jarno