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 getclicky.com'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 wordpress.org 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="http://static.getclicky.com/123.js"][/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="http://static.getclicky.com/js"][/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

Clicky API v4 released

In addition to the new wordpress plugin, today we're also releasing version 4 of our analytics API. We've got some really great new features outlined below. Full documentation is here.

  • Segmentation data!
    Example: Summary data + top countries and web browsers for visitors from twitter.com over the last 7 days

  • Data for individual items (e.g. a specific country or search term). Note, this is different than the existing "filter" parameter, which is a wildcard (i.e., slow) match. This is an exact match string and hence very quick.
    Example: Daily hits from google.com

  • Hourly data for supported data types (visitors and actions)
    Example: hourly data for both visitors and actions over the last 7 days

  • Option to specify only the fields you want returned for type=visitors-list. This is a big one because we have a number of users who export their entire visitors-list every day. They may only want a few fields, but had to get all of them no matter what. If this applies to you, this new option will vastly speed up the response time for visitors-list queries.
    Example: Only return IP, session ID, landing page, location, and browser

  • Proper error responses. It's hard to believe that up until now, a bad request would just return completely empty. How helpful of us! Now, if there are any problems with your request, an error will be output.
    Example: Forgetting the required "type" parameter. XML PHP JSON

  • The XML parent element has been changed from "items" to the more standard "response". This parent element also has a new attribute, "status", whose value will either be "ok" or "fail". If it is "fail", there is an error with your request. The XML document will then have just one element, "error", whose value will be the error message. For PHP and JSON, which both return arrays, the array will only have one item, whose key will be "error" and whose value will be the error message.

  • We've added a ton of inline examples throughout the documentation, so instead of perhaps being confused about what a certain feature does, you can just click a link and instantly see an example.


The two big features for us are segmentation, and being able to specify a individual items. With these, and everything else, we feel the API is much stronger than v3.


We like APIs. They're neat.

We're going to be adding some more APIs in the near future that let you get information about your account, as well as the ability to write data to Clicky, instead of just reading from it. For example, registering new sites, updating site preferences, creating goals, etc.

We're releasing one today as a sneak peak. This is something that those of you with lots of sites may find quite useful. It's called "sites". (We're really creative). Pass it your username and password, and it will return to you all of the sites in your account, including their domain name, nickname, site_id, sitekey, sitekey_admin, and database server.

For example, here's a pretend account I just registered.
http://api.getclicky.com/api/account/sites?username=awesomeaccount&password=awesomepassword

And with PHP output:
http://api.getclicky.com/api/account/sites?username=awesomeaccount&password=awesomepassword&output=php


Happy Halloween weekend!

Don't drink too much! We'll see you in November.
0 comments |   Oct 30 2009 3:18am

Next Page »




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