“wgact” source GPDR compliant?

  • Resolved doffine

    (@doffine)


    4 years, 5 months ago

    Hi, we noticed after implementing your plugin + Borlabs Consent Tool, the source “wgact” is still loaded even though no consent is given yet. We are not sure what exactly this source is and if this is GDPR compliant? Is it an essential source?

    We also noticed that the free version provides no consent mode. If I understand this correctly we can’t use your free plugin in the EU because it’s not GDPR compliant? Or is there another way to make your free plugin GDPR compliant?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Kenneth

    (@kavillarosa)

    4 years, 5 months ago

    Hi @doffine,

    Thank you for reaching out!

    You’re right. “wgact” will still be loaded by default because Explicit Consent Mode is not enabled in our plugin(which is only available in the PRO version). Even though you’re using the Borlabs Consent Tool together with our plugin, you still have to enable this.

    To do this, just go to WooCommerce Pixel Manager > Advanced > Cookie Consent Management and enable Explicit Consent Mode. See – https://share.getcloudapp.com/04uLXLAX.

    Our free version of the plugin only has the Implicit Consent Mode enabled by default. This means that cookies are tracked immediately without consent.

    If I understand this correctly we can’t use your free plugin in the EU because it’s not GDPR compliant?
    Yes, because you’ll need the Explicit Consent Mode feature to make your Cookie Banner GDPR compliant.

    I hope that helps.

    Let me know if you have other questions or concerns.

    Regards,
    Kenneth

    • This reply was modified 4 years, 5 months ago by Kenneth.
    Thread Starter doffine

    (@doffine)

    4 years, 5 months ago

    Hi Kenneth,
    thanks for answering all our questions. Great support!

    We’re using your free plugin as well as your pro plugin version (on different websites of course) and we have the Explicit Consent Mode active in the pro version but the “wgact” is still being loaded before consent is given. We followed your guide on how to use your plugin with the Borlabs Consent Tool and it seems to be working except for the “wgact” source.

    Our question now is: How can we block the “wgact” even though we already have the Explicit Consent Mode active?

    Thank you in advance!

    Plugin Author SweetCode

    (@alekv)

    4 years, 5 months ago

    Hi @doffine

    What do you mean exactly by “wgact” is still being loaded? Do you mean the plugin, or a cookie or the plugin front-end script?

    Once I know I can clarify.

    Regards
    Aleksandar

    Thread Starter doffine

    (@doffine)

    4 years, 5 months ago

    Hi Aleksandar,

    to answer your question: We see that “wgact” is being loaded when we surf to the website in Google Chrome and press F12. In the tab “sources” you can see that it’s loading an external source “wgact” and if you expand it you can see a “webpack” and “./src/js/public” with lots of .jsx files in it. We have your feature “Explicit Consent Mode” and Borlabs Cookie Tool active.

    Thanks!

    Plugin Author SweetCode

    (@alekv)

    4 years, 5 months ago

    Ah. wgact is not a tracking script. Is is a management and loader script for the tracking pixels.

    For instance, if you’ve turned on explicit consent mode, this script will detect when the visitor gives consent and then loads the tracking scripts. Without wgact that would not be possible.

    Does that answer your question?

    Thread Starter doffine

    (@doffine)

    4 years, 5 months ago

    Hi, yes that answers our question.

    Just for our further understanding: Why is it listed outside of the domain path where usually the external sources are listed?

    See Screenshot: https://imgur.com/a/Ci3NceM

    Thanks again for your support, very much appreciated!!

    Plugin Author SweetCode

    (@alekv)

    4 years, 5 months ago

    Why is it listed outside of the domain path where usually the external sources are listed?

    Good catch! But, to be honest I don’t know. I haven’t looked into that yet as it is is not a bug, just a weird way of Chrome to display it.

    • This reply was modified 4 years, 5 months ago by SweetCode.
Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘“wgact” source GPDR compliant?’ is closed to new replies.