Let me know if you think this should be something to handle in the package itself, and if so, if you have suggestions as to how. To be honest this was built before cookie regulation was such a hot-topic, and I probably should consider it a bit more.

Was thinking perhaps if I added a check for a (configurable) cookie or a (configurable) session value existing with a non-null value, then if found, that would prevent writing any other cookies. Sounds sensible?

And after that it would be up to the implementor to set one of those two things if their site visitor has declined non-essential cookies, and be aware that if they for example wanted to show some content based on a cookie based criteria (e.g. pages viewed, number of visits), these just wouldn't show up.

Andy

Hi Andy,

I think it could be a good solution with the cookie/session value. Then I as an implementer can set this based on the approved cookie categories the user has set.

I my case I have a contact module and based on what region the user has selected I show one of five different contact modules using the cookie criteria.

I case the user has declined cookies, I would like to show a default contact module instead of no contact module. Would it be possible to add a checkmark on either a Personalisation group or a criteria, where the editor can set the group/criteria as default in case the user has not accepted cookies? When a group/criteria is marked as default it will always return true if the session is disabled by the new cookie/session value. I think the would be really usefull at least in my case right here.

Also would it be all criterias that would be disabled or just some of them?

I was thinking more that, if the user declines cookies, it's up to the website implementor to track that somehow - in a cookie (ironically) or in a session variable.

Then if they user has declined cookies the package should no longer be writing the cookies that it currently does to track them for certain criteria (namely the "pages viewed" and "number of visits" criteria). So what I'd add to the package would be a check for either of these indicators that the user has declined cookies, and if it's found, no longer write/update these ones.

So basically just making sure that "if the user has declined cookies, we don't carry on writing them".

In order to meet your use case, seems like you could just create a personalisation group that has a definition on the presence of the "declined" cookie or session variable, and if it's found, show your content.

Andy

Yes you're right, I could just make a personalisation group with a cookie criteria to show a module when users has declined cookies.

I think this would be a great solution to the plugin in order for the implementers to be able make the site cookie compliant.

Thanks Andy, I have tested and it's working.

is working on a reply...