Support » Plugin: Complianz - GDPR/CCPA Cookie Consent » Cookie not disappear

  • Resolved neoseeyou

    (@neoseeyou)


    Hello

    Thank you for your very good plugin, even if it’s difficult to configure everything properly with a store having a lot of features.

    While testing, I noticed that if I changed one of my consent settings on the cookie policy page (e.g. disallow “statistical” cookies afterwards), the cookies (like the analytic ones) still remained present and active in my browser. Is there an explanation for this or is it normal? What happens if I accept statistical cookies and then want to stop accepting them?

    Thank you!
    Regards

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hello @neoseeyou,

    The main difference is between revoking consent and removing/changing already set cookies in a visitor’s browser.

    “Complianz disables third-party scripts that set cookies prior to consent, and after a revoke. When a visitor withdraws their consent, already set cookies are no longer useful, but cannot be removed on third-party domains.”

    Please refer to our article here for the details:“Removing cookies after revoking consent”

    Kind regards,
    Jarno

    Thread Starter neoseeyou

    (@neoseeyou)

    Thank you for your quick answer! i will look at this post. I will have to test it for our affiliate programm.

    About this scenario: A visitor who has clicked on an affiliate link, chooses to accept all cookies on our site and then changes his or her mind and wants to block marketing cookies (affiliate cookies are in this category) then decides to purchase a product from our site. The affiliate should not receive any commission in this case.

    The same goes for the opposite case, if the visitor refuses the marketing cookies from the beginning and then decides to allow them, will the affiliate receive his commission?

    Thank you

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @neoseeyou,

    Hard to accurately say without knowing the exact configuration of both the referring website and the ‘main’ website, as there are a lot of variables to account for.

    I would say that when you revoke consent & add a custom filter/script that actually removes the Cookies (those pertaining to the affiliate) from a visitor’s browser, that this visit won’t be attributed to the affiliate. But then again, testing would be the only way to know for sure.

    Kind regards,
    Jarno

    • This reply was modified 3 months, 3 weeks ago by jarnovos.
    Thread Starter neoseeyou

    (@neoseeyou)

    Thanks Jarno šŸ˜‰

    Despite the script you provide in your documentation, this does not seem to have any effect on affiliateWP cookies.

    Should i have to custom your function in order to work with this plugin?

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @neoseeyou,

    Indeed, the script might need adaptations to fit your exact use case. Our example skips cookies that include ‘wp’, so it could be that the AffiliateWP cookies get skipped as a result?

    But just to reiterate, removing Cookies from your visitors’ browsers is not required in the context of the ePrivacy Directive.

    Kind regards,
    Jarno

    Thread Starter neoseeyou

    (@neoseeyou)

    Hello

    Thank you for this answer, affiliateWP cookies start with “aff” but you’re right, the script maybe need some adaptations.

    Cheers

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.