killedmufasa

Hi again! Thanks for the amazing support so far, thank you! Sorry about the confusion with the cmplz_choice cookie, looks like I indeed misunderstood its function. Perhaps you could consider updating the docs to clarify its function?

What you can do is to check if cmplz_statistics or cmplz_marketing is either ‘allow’ or ‘deny’. If it’s empty, no choice has been made yet.

That seems like a very neat solution, thx! Although, I gotta say cmplzGetBannerStatus() sounds much easier to work with. Speaking of, will it work with the shortcode too?

Other than that, no further help needed. Is it okay/handy if I keep the thread marked as ‘unresolved’ until v6 releases?

Cheers!

Hi again! Thanks a lot for making the cookie available to non-premium users and so quickly! I can confirm the cookie is now always set (or at least with my settings).

However, it does behave differently than I had anticipated. According to my testing on both the site I’m working on and complianz.io (using isolated containers), the cookie cmplz_choice is always set to set. As an EU citizen, I would have expected for the cookie to default to something like no_choice (see: https://github.com/Really-Simple-Plugins/complianz-gdpr/blob/cmplz_choice-without-ab-testing/assets/js/complianz.js).

Your docs describe the cookie as such: “tells us if the user has made a choice or not”. But even when I haven’t made any choices yet, it’s set to set. Am I misunderstanding what this cookie does? Otherwise, what’s the point of the cookie if it is always set to the same value?

Thanks!