Viewing 7 replies - 1 through 7 (of 7 total)
  • Same to you.
    I have this error.
    Please let me know any solutions?

    Plugin Author alekv

    (@alekv)

    This is probably nothing we can fix.
    Our plugin simply inserts the Google conversion script. And the described problem is probably triggered by that script.

    But, in order to get a better understanding of that error, and maybe find a solution, could you send me the URLs of where this happens to support@wolfundbaer.ch ?

    Dear @alekv
    Here is the url of that error.
    https://yangon.style/
    Hope to you can find any solution.

    There should be a way to add the cookie with the ‘SECURE’ flag. Please check it.

    Plugin Author alekv

    (@alekv)

    @kksandar1

    I can’t replicate that error: https://take.ms/Dn3er

    Could you send me a screenshot to support@wolfundbaer.ch?

    @kksandar1 @dimath99

    You can read here for more details about the SameSite cookie.

    You can disable them through chrome://flags Cookie Deprecation messages disabled.

    * The new SameSite rules will become the default behavior on Stable in Chrome 80.

    • This reply was modified 2 months, 1 week ago by kepaduan.
    • This reply was modified 2 months, 1 week ago by kepaduan.
    Plugin Author alekv

    (@alekv)

    Hi @kepaduan. Thanks for the info. It helped me narrow down it down a bit more to what causes the issue.

    As soon as I turned on to block third party cookies in my Chrome browser, I received the same warning message: https://take.ms/ZqjUL

    1) Currently, this warning only affects people who block third party cookies. But, the warning shows us this will become a problem for everyone with Chrome 80, so I understand we need a solution.

    I dug further and found out this is not affecting only the doubleclick coookie, but Facebook and possibly other cookies too: https://take.ms/AJQ0d

    2) The way our plugin works we won’t be able to fix the issue at hand. What our plugin does is to insert the Google gtag script through a Google server which is not under our control. This gives Google the ability to update the script anytime they need. On the other side we can’t change the script and the cooke directive. We only can use the script functions to transmit the order value (and a bit more) to Google. SameSite cookie instructions are not one of those functions.

    3) I believe Google (and every other tracking pixel) has to come up with a solution for the issue we face here. I believe for Google it will be as simple as updating the gtag script on their side. But there is no way for me to find out if and when they are going to do it. It is next to impossible to get in contact with one of their engineers who are working on this.

    Regards
    Aleksandar

    • This reply was modified 2 months, 1 week ago by alekv.
    • This reply was modified 2 months, 1 week ago by alekv.
Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.