on-site analytics bug is fixed. clear your browser cache and let us know how it works!

There's also a bug with the on-site analytics widget not loading. This will be fixed today!

There was an issue with our automatic history.pushState() tracking. Deploying a fix now!

If you are using proxy tracking with caching, you'll need to clear that cache manually if you want your site's tracking code updated asap. Otherwise, regardless of using proxy tracking or not, you shouldn't need to do anything!

Discovered when updating our Shopify tracking code to the new API (a few weeks late, sorry). We'll announce this Shopify update soon, should be within 24 hours!

We started working on this last week and we're trying some pretty aggressive measures, so your traffic may fluctuate a bit more than you're used to for a bit.

We're going to make mistakes too... A customer just informed us no iCloud relay traffic was logging.

Oops 🥹

Last, we moved to clicky.com in 2012, but still there are calls to the API via getclicky.com, more than we expected once we looked. So there's an exception to bot blocking for API calls, since they're supposed to be 100% automated. Let us know if any issues

We have some new AI features coming soon that we teased about in our last blog post, but once that's ready, then our bot detection will also improve a good amount.

blog.clicky.com/ai-utms-and-...

We're well past peak traffic logging time today, but it's currently blocking about 800 requests per minute.

No filter is perfect, there will be false positives, but please let us know how it's working and if you see any major changes in your traffic.

Sending you an email...

I'm not sure what that one is, but oh, we should probably be stripping trailing slashes, I'll fix that soon.

We're creating a new category for AI visitor and bot traffic, so you can view reports on them all together instead of by single domain only.

The bots all/mostly use Headless Chrome, which does javascript, so it shouldn't be an issue.