POST … net::ERR_BLOCKED_BY_CLIENT

  • Resolved Peter

    (@pdux)


    3 weeks ago

    Hello 🙂

    First I want to thank you for your amazing work, I just discovered your plugin and already love the simplicity, no BS and the fact how lightweight it is !

    However I experience this issue, just in vivaldi browser, even tho I have disabled internal ad/tracking blocking completely, even without any plugins, even in private window :/

    Console error: POST https://xxxx.xx/koko-analytics-collect.php net::ERR_BLOCKED_BY_CLIENT

    Now, I know this has nothing to do with your plugin I assume, however, I was wondering whether there is anything that can be done to avoid this happening, some workaround, that other plugins seem to be doing.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Danny van Kooten

    (@dvankooten)

    3 weeks ago

    Hello @pdux,

    Thank you for the kind words!

    The error message “blocked by client” indicates that the HTTP request was blocked by your client, which is Vivaldi Browser in this case. So something in its configuration is still causing it to block this request. It may be worthwhile to check out this article in their knowledge base to see if you can add an exception for your site: https://help.vivaldi.com/desktop/privacy/tracking-and-ad-blocking/

    Best,
    Danny

    Thread Starter Peter

    (@pdux)

    3 weeks ago

    The thing is, as I said, I disabled all blocking in Vivaldi, like, completely.
    I also edited my post, ‘Now, I know this has nothing to do with your plugin I assume, however, I was wondering whether there is anything that can be done to avoid this happening, some workaround, that other plugins seem to be doing.’

    Another Edit: I found the problem, its their feature ‘Block Hyperlink Audit Tracking’, so I wonder whether there is something you could do to avoid being blocked by it.

    Found some reference: https://forum.vivaldi.net/topic/79924/what-is-hyperlink-audit-tracking

    • This reply was modified 3 weeks ago by Peter.
    Plugin Author Danny van Kooten

    (@dvankooten)

    3 weeks ago

    Hi @pdux,

    We could start playing a cat and mouse game in trying to combat privacy-preserving features like this (because you could argue they shouldn’t apply to Koko Analytics, and I would agree) but it would be a never-ending game which would definitely come at a cost in terms of either code complexity, performance or reliability. Or all combined.

    For now we believe it’s best to simply focus on the part of the visitor base that is not using ad-blocking or has explicitly whitelisted your site.

    I was wondering whether there is anything that can be done to avoid this happening, some workaround, that other plugins seem to be doing.’

    Can you name an example, please?

    If other plugins are getting around this it may be because they’re either a) not yet on one of the default filter lists like EasyList Privacy (which Koko Analytics is on) or b) because they’re not using navigator.sendBeacon().

    Now we are using the navigator.sendBeacon function explicitly because it comes with several cool features:

    • the request is fired off with a lower priority then other stuff on your page, so there is virtually no performance impact for your visitors in terms of LCP etc.
    • the request completes even if the user navigates away from the page quickly, thus increasing the accuracy of your stats.

      I hope that explains a bit the rationale behind our choices.
    Thread Starter Peter

    (@pdux)

    2 weeks, 5 days ago

    Thank you for your explanation

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