We’ve made a number of enhancements over the last few weeks that have gone unannounced, because none of them were particularly worthy of their own blog post. But now that we got a collection of items, we’re going to write about them.
Change the default type for any dashboard module – When you customize your dashboard, most modules will now have an option called “default type”. The options listed are the exact same things as the “tabs” you see for that module, when viewing your actual dashboard. Previously, the default type was always whatever was “first” in that list. But now, if you want the default to be something else (e.g. change “Links” to default to “newest unique” instead of just overall top incoming links), you can do that!- If your page titles change, we’ll update them too – Previously, we only logged the page title for any unique URL for your site the very first time we logged that page. If you updated your page title structures (as an amazingly insane number of you do, apparently – we get emails about this every single week), Clicky would still show the old one. Alas, no more! If the title changes for any given unique URL on your site, we will update it too. The update won’t always be immediate, though, but it should be within a week (assuming that the page has been visited and logged by Clicky since you last made the change).
Hourly graphs for today stop at the current hour – Say it’s 10am and you’re checking your hourly visitors graph. Used to be, every hour after 10am would be a zero – which it technically is, but we’d draw it that way too, so it made it look like your traffic just fell off a cliff. No more! If it’s 10am, we’ll only draw the graph (for today) up until 10am, which has a nice psychological impact.- More translations – We’ve added a bunch of new terms to translate. 100% of our stats reporting interface is now available for translation. If you want to help, click here!
- Larger date ranges – All reports were limited to one year. We’ve increased this limit to 2 years. Segmentation (filtering) has always been limited to 31 days though because it’s a fairly intensive process. But the update we released a few months ago dramatically increased the efficiency of the way visitors are stored. Because of this, we can now allow you to segment a larger range. The new limit is 90 days.
- Disable pinging in our tracking code – We don’t know why you’d ever want to do this, but we got requests for it, so we added it. By default, our tracking code periodically pings our tracking servers while a visitor is sitting on a single page, so we can get a more accurate figure for how much time they actually spent on your site. If for some reason you want to disable this (and we won’t complain – it means less stress on our tracking servers!), you now have the option.
- Complex IP range queries – In a single request, you can now request a list of visitors that match a specific range of IPs, or a specific IP, or both, or multiple of both. For example, you could use this to request all visitors from 65.0.0.0-75.255.255.255, plus 66.1.2.3., plus 2.3.4.0-2.3.4.255 – all in one request. This will be mainly of interest to those of who utilize our API, but regardless, to those of you who need something like this, we think you’ll like it. You can find documentation for it here.
- Time offset for visitors and actions in the API – You can now request a specific time fragment for type=visitors-list and type=actions-list in the API. This means if you have data up through say 12:30pm extracted, and it’s now 1pm, you no longer have to “guess” how many items you need to extract so you can get all of the missing data from 12:30-1pm. Now you can just say time_offset=1800 (30 minutes) and you’ll get only the data you need. You’ll need to (probably) request limit=all as well, otherwise the default limit of 10 applies. We like this option a lot because it makes your life easier, and it puts significantly less stress on our API. So if you have an app that extracts visitors or actions lists, please update it to use this option.
