Hi @jestemzmiasta,
You can directly enable the CookieShredder feature (included since 6.1) under Wizard > Consent > Services > “Do you want to enable Consent per Service/CookieShredder…”, the most up-to-date version of the filter in the article you attached.
The plugin would then remove (first-party) cookies that do not meet the consent level of the user when consent is revoked. The session cookie “cmplz_cookie_data” stores which cookies are ready for removal. Full explanation here: https://complianz.io/introducing-the-cookieshredder/
Kind regards,
Jarno
Hi @jestemzmiasta,
Did this work for you? After enabling the option, some caching needs to clear and we can check if it works if you share your URL.
Let me know,
regards Aert
Thank you for your response. I have already found and activated CookieShredder option earlier, but it did not change the issue of the koko analytics cookies remaining in the browser after removing the consent. I’m working on these issues on the offline site on localhost and I don’t have how to link to it.
Can I ask for an explanation of the phrase “some caching needs to clear” – i’m not using caching plugins. Did you meant that?
I noticed one more problem. The problem of assigning to a category. For now it works as long as I give category = “marketing”. If I try to use a different category like preferences for example, it doesn’t work at all. The page is looping and trying to load constantly.
Hi @jestemzmiasta,
As for Koko Analytics, how does the cookie appear on your end? Does it have any content or is it possibly a visual occurrence, so that they still appear but are in fact empty, and disappear upon a refresh of the page? We’ll look into it on our end as well.
If you’d wish to avoid Koko from setting cookies in the meantime, you could navigate to Dashboard > Analytics and set “Use cookie to determine unique visitors…” to No to achieve that.
As for the Preferences behavior, could you elaborate on the steps I’d need to take to reproduce this?
Kind regards,
Jarno
I only need to give a small correction to “I noticed one more problem. The problem of assigning to a category“. This problem concerns other uses (not Koko), e.g. OSM maps and I meant to hide map before someone agrees to send data to OSM. Everything works great here (the map appears and disappears with consents), but as I wrote, it must be the marketing category and I don’t know why. It doesn’t work for others, like preferences or statistics.
As for Koko cookies… Of course, I had correctly set this option “Use cookie to determine unique visitors …” to No “. Anyway, cookies appear after giving consent. Thats working fine. The problem is with their removal.
Therefore, after agreeing to the statistics and manual refreshing of the page, the _koko_analytics_pages_viewed cookie appears with some numerical attribute added to it. After removing the consent, you can see the change from cmplz_statistycs to deny, but the cookie from koko is still there. And refreshing doesn’t change anything.
The behavior I see is that after refreshing a page without consent, Koko will place a cookie, but after about 800 ms the cookie is overwritten with an immediately expiring one.
If I then check the console/application/cookies overview, the cookie is indeed gone.
This the expected behavior, as the cookie shredder on interval basis clears cookies for which there is no consent.
Hi @jestemzmiasta,
We haven’t heard from you in a while, is your question answered? We are happy to help you further.
Kind regards, Kim van Dijk
Thank you for your reply and sorry for the delay. Unfortunately, it doesn’t work the same for me. Denying consent does not change the status of the _koko_analytics_pages_viewed cookie. It has a full expiration time (max-age) of about 6 hours. The changes are only for cmplz_statistics to deny. Nothing else changes 🙁
I’ve even added a script to my functions
/* reload after consent… */
which helped me a lot in other cases, such as still revealed map after choosing to revoke consent to display it. The map is not always hiding (under the map is visible placeholder but map is still working untill reload the page). But nothing changed in case of koko.
P.S>
I can provide the address of the problematic page because I already have it online, but I can do it by e-mail, I prefer not to publish it on the forum.
Hi @jestemzmiasta,
Of course, you can send us a message via support(at)complianz.io, and we will have a closer look.
Kind regards,
Jarno
We quickly determined the cause by e-mail. Problem is solved. And for everyone who has the same, I am giving a solution.
First of all, after logging into the backend, you need to enable all cookies -> click the accept button on the cookie banner. Then all cookies will be cached, including the one from koko analytics in your browser. And go through the whole wizard again. Then the Complianz plugin will detect the cookie and assign it to the correct category – statistics.
Everything works and the cookie disappears when consent is removed.
Thank you very much for your help and commitment!
