Clicky Web Analytics

Added tracking code installation instructions for Vistaprint (all http://webs.com  customers were forced over there recently) and Webflow. https://clicky.com/help/apps-plugins …

Portland normally just barely breaks 100 one or two days per year at worst. I don't know what kind of havoc this will cause, but if anything goes offline in the next few days, this is probably why. The highest temp I can recall in 20 years of living here is 104.

Cookies are useful, damnit. I don't want them to go away. Not even related to Clicky but just in general, as a web developer and an end user - cookies are great. People need to chill.

The privacy concerns with cookies are so overblown because of the media. The worst offenders are ironically media web sites that typically have 20+ third party javascript includes. I only use ad-blockers so these kinds of sites load faster, not because of privacy.https://twitter.com/sarafischer/status/1408058508017291264 …

With this new design, we're no longer tracking or displaying OS and search engine breakdowns. But those were absolutely dominated by Windows and Google respectively, so they weren't interesting anyways. Web browser data is the good stuff.

Spy uses the same design for the part that shows actions so it also got the same updated look. And with so much more efficient use of space, it now shows the last 100 actions instead of the last 40.

Edge is the ONLY browser I'm aware of that completely changes its user agent on mobile devices. Pretty weird stuff. Anyways we'll add support for this later today so you should start seeing it again, sometimes... its user base is small but it's a nice browser!

Been using the Edge browser a lot recently and noticed there were literally zero "Edge mobile" visits being logged to Clicky, but I know it used to work. Turns out the user agent on iOS is "EdgiOS" and on Android it's "EdgA"... So, it was just falling back to Chrome.

ESET update: https://clicky.com/forums/?id=62382#62386 …

ESET said they have disabled the filter temporarily while they look into reworking it. So hopefully the errors will permanently stop very soon from now.

We deployed this change about 30 minutes ago and confirmed it works. Unfortunately visitors will have the old code cached for up to 7 days in their browser, so unless/until @eset fixes it, it won't totally go away until next Wednesday, but should be 99% gone by tomorrow.

You can still USE history.pushState in your code. But HEAVEN FORBID you check that the object exists first. We're tweaking our code now to use a try/catch block instead and will be pushing that out soon.

So it turns it's it's a generic javascript pattern match, and ANY JAVASCRIPT FILE that references "history.pushState" inside an if() block will trigger this filter. E.g. "if( history.pushState ) { doStuff(); }".

Everyone please help expedite by submitting additional reports for "https://static.getclicky.com/js " and "https://hello.staticstuff.net/js " to the page below: https://webfilter.eset.com/en-us/remove