Clicky turns 3

Clicky launched on November 28, 2006. I can't believe it's been three years, but the calendars don't lie. Clicky is now tracking over 155,000 web sites, powered by over 30 servers chugging along in the background. We never expected it to get this big. We greatly appreciate everyone who has supported us throughout the years and told your friends and colleagues about our service - Clicky has spread purely by word of mouth and that's the best kind of marketing anyone can ask for. Thank you for everything.
21 comments |   Nov 28 2009 2:16pm

New global marketshare reports

We've just released our new global marketshare interface, and it adds a ton of new features. Previously, we only reported on global browser and OS family marketshare. Here's what's new:
  • All data available both globally, and by country
  • Breakdown of browsers and OS by version
  • Compare top overall versions (e.g. Firefox 3.5 vs MSIE 7.0), or the top versions for one specific family (e.g. just Firefox or just Windows)
  • Search engine marketshare
  • Desktop vs mobile data for browsers, OS, and search engines.
  • Mobile phone marketshare
  • Video game console marketshare
  • More accurate - data is now calculated from all traffic coming into Clicky, rather than a small sample of it

And the best part, like Clicky, it's updated in real time. You don't have to wait until December to see November's marketshare - it's there as it happens.

We just started tracking most of this data last week, so most of the reports only have about a week of history right now. Because of this, there is not currently a date range picker, but we'll be adding one once we have a few months of data.

So... go check it out!

2 comments |   Nov 23 2009 12:47pm

New segmentation features: landing/exit pages, number of actions

We're launching some really great new segmentation features today:
  • Filter by landing page
  • Filter by exit page
  • Filter by number of actions (exactly 1, greater than 10, etc)
  • View top pages, landing pages, and exit pages for any segment of visitors
  • This is of course all available in the analytics API too

Let's run through an example for's traffic. Note that some of these screenshots are edited to save space.

First, let's analyze our home page. Before this new update, all we could do was filter by visitors who had seen home page at any point during their session, like this:

But now we can filter down to only visitors who actually began their visit on our homepage. These are who we really want to look at. This is more likely to be "new" visitors, as they wouldn't be coming from bookmarks to pages within our site or anything like that:

Based on the average actions and time per visit for this second group, it's obvious these people aren't as engaged as the first group. Perfect, that's who we want. Ok, let's look at the top exit pages for these visitors, which will show us where we lost the most visitors:

But is this the data we really want? This includes people who came to our homepage, perhaps logged in and viewed 1,000 reports, then logged out and left. We don't want these people included here. So, let's add a "number of actions" filter and set it "less than 5". This will now mainly be people who are not engaged with our web site at all.

As you can see, the average time and actions is now way less than it was before. Now let's look at the top exit pages. It's about the same, actually. The numbers have gone down on all of them, but the actual top exit pages, and their order, is about the same. But that's fine - we can still look at specific data for this segment of visitors, such as top goals completed, or goals started but incompleted, to get some more data from them. Or even view the individual visitor sessions that interest us.

I won't go any further with this example, but as you can see, the paths of exploration are endless from this point. I hope it gives an idea of the powerful filtering you can do with these new features.

Here's one other quick example: Top landing and exit pages for everyone who arrived via search.

The pricing page is still a big deal for exits though. Gonna have to work on that one :)
6 comments |   Nov 04 2009 12:40am

Updates to Wordpress plugin

The two biggest feature requests have been added to the 1.0.2 release of our plugin:

  • Field to enter in text that precedes the auto-tweet, e.g., "New blog post: "

  • New preference to always tweet new posts. Enabling this option should allow new posts that are created within third party interfaces (e.g., the iPhone) to be auto-shortened and auto-tweeted as well.

What are you waiting for? Download the new version now and tell us what you think!

Note: we are in the process of adding this to so that in the future, updates can be fully automatic from your WP admin page.
20 comments |   Nov 03 2009 12:19am

New tracking code format; please update your site if possible

We've recently changed the format of the tracking code you paste onto your site to take advantage of cross-site caching. Here is an example of what it used to look like (Javascript portion only):

[script src=""][/script]

In this example, "123" would be the site ID for this site in our database. This is all fine and dandy, but the problem is that the URL is unique for each site that has our tracking code on it, even though the actual javascript code that is being downloaded is the exact same. So if someone browses to 10 different sites in a day that all have Clicky on them, they would be downloading 10 copies of the same code, instead of 1.

As of a few weeks ago, we changed the format to this:

[script src=""][/script]
[script]clicky.init( 123 );[/script]

As you can see, the URL of the tracking code is now the exact same for every site that someone would visit with Clicky on it. We just added a seperate function call to set the site ID within the script after it's downloaded. Since any user's browser would cache this script, it doesn't have to redownload it. This means your site will load faster for anyone who has visited another site with Clicky on it in the last 7 days.

So, the point. If possible, please replace the existing tracking code on your site with a fresh copy (go to site prefs, then tracking code, to get a copy). As already mentioned, this will help speed up your site for the average visitor, as well as reducing bandwidth usage on our end.

Of course, the old format still works, and will indefinitely. We don't want to force you to do this, but if you have a few extra minutes, the web will be a better place. Thanks.

UPDATE: Yes, the new WP plugin has the new tracking code format. This only applies to people who manually paste the code on their site anyways, since using a plugin puts you at the mercy of the plugin developer.
5 comments |   Nov 02 2009 2:49pm

Next Page »

Copyright © 2018, Roxr Software Ltd     Blog home   |   Clicky home   |   RSS