Sneak peek of the new Clicky

Competition in our space is heating up, so we're working furiously to make Clicky stand out. One way to do that is with colors. Remember Paint by Numbers? Well we have taken that concept and color-coded all your favorite stats to the colors of the rainbow. And we thought... what's prettier than a rainbow? Maybe two rainbows? Exactly.

So as you can see, your stats have never been prettier, or easier to read. Our guess is that you will never want to leave your computer again.

To say that we are

SUPER EXCITED

would be the understatement of the decade. This bad boy is going to eat our competition for breakfast. Coming soon!!!


37 comments |   Mar 31 2010 5:29pm

Cookies and pinging support coming soon to our tracking code

We're working on another update to our tracking code that's going to add two much needed features: cookies, and pinging support. We have to make some backend changes also to support this, so we expect it to be about 2 weeks before it's ready. Here's what these features will do for us:

Mmm... cookie

Cookies will let us track unique visitors more accurately. Currently we just do this based on IP address, which works well most of the time. But if you have a bunch of people all behind the same router all accessing the same site at the same time, Clicky currently sees this as one visitor. This is rarely a problem for most of you, but some of you have sites that are accessed mainly by intranets, so it's more of an issue. Cookies will also let us finally track new vs returning visitors.

Cookies will be enabled by default. Most of you couldn't care less, but we do have some government sites using our service and we have been contacted more than once to ask about cookies, because it's illegal to have a government site that sets third party cookies without a signoff from the Secretary of Defense - no joke. So if you want to disable cookies in your tracking, implement this code as soon as possible. We're going to email everyone who has a .gov site in their account and point them to this post so we can be sure that everyone sees it.

Pinging

Pinging support will let us provide much more accurate "time on site" figures for your visitors. Right now we just rely on a time out period to say "ok, this person is gone". With pinging, we'll actually know when they're gone. Spy will be much more accurate in terms of how many visitors are actually on your site literally right now. This will also let us track how long someone is on your page for the last page view of their session. In particular, people who only have 1 action will no longer all be shown as "10 seconds" - we'll actually know how long they were online.

We're also going to adjust our "bounce rate" calculation so not everyone with just one page view will be counted as a bounce. While a lot of people who only have one page view are not engaged with your site, this isn't always the case. If you have a long article linked from Digg for example, 50% of the people may actually read the whole thing and be on your site for 5-10 minutes. Right now, all of these people would be shown as bounces, but once this feature is implemented we'll probably classify anyone who is on your site for more than 30 seconds as an engaged user, and they won't be a bounce.

Woopra recently poked fun at us on their blog for not having pinging support, but we agree with them - this feature is needed, and we will have it very soon. It's been a planned feature for a very long time, so we're glad it's finally in the works.
18 comments |   Mar 29 2010 1:16pm

Asynchronous tracking code, take 2

Kindly ignore yesterday's post about asynchronous tracking code. After further research it was determined that we didn't entirely know the full details of how this works with other services like Google Analytics. The code we released was simply waiting for "onload" to fire and then creating the script element that would trigger tracking. While this sort of achieves the same effect (it doesn't interfere with your site's loading), it definitely decreases accuracy, which is why we warned about that.

Well, forget all that, k? We just released an updated version that is truly asynchronous, and it should be more accurate, not less. Why? What we didn't know yesterday was that if you inject a script element into the DOM, all modern browsers by default will download that script asynchronously, which means in parallel with anything else that is already downloading to a visitor's browser. I'm embarrassed I didn't know about this trick, but it's true.

Taking this a step further, we modified the actual tracking code that you link to from your site so that the beacon it sends back to log data is also based on an injected script element, which means it now is asynchronous as well. Previously, we were using an image, which does not get this benefit.

We've been testing this new stuff most of the day for the tracking of getclicky.com, and it's working very nicely.

So, if you do absolutely nothing, you will still automatically get the benefit of the asynchronous logging of data. You may still see "waiting for in.getclicky.com..." in your browser's status bar, but it is not interfering with the downloading of other items from your web site.

But, if you want full asynchronicity, then go grab a fresh copy of the code from your tracking code page. This new code that you paste onto your site will also inject the tracking code script into your site's HTML, which will give you the full benefit of this functionality.

On yesterday's post, someone asked why we still recommended pasting it into the bottom of your site, rather than the head like Google Analytics suggests. The way the code from yesterday was designed, there was no benefit to placing it higher. But today, things are different. However, from what we have read, Google's recommendation is incorrect. They recommend you place the async code inside your site's "head" tag, but this code then manipulates the "head" object directly before the browser has fully parsed it. Everything I have read says you should not do that, as it can cause serious browser malfunction. If you want to place this code higher up, we recommend doing so at the very top of your body element, rather than the bottom. But we really don't think it will make much of a difference either way.

Ok, go enjoy!
15 comments |   Mar 25 2010 5:30pm

Asynchronous tracking code

Update: Kindly ignore this post. Please read this one instead.

By popular demand, we are releasing asynchronous tracking code. This means tracking your site with Clicky will have literally zero impact on the loading speed of your site, because the code won't be downloaded and executed by the end user until your page has fully loaded. Although our tracking code is on a CDN and should load very quickly already, there has been demand for this, so we are offering it.

Grab a copy of it in your site preferences area.

We are not making this the default tracking code because there are a few gotchas:
- Stats will probably be slightly less accurate (this problem affects every analytics service that offers async support - but we want to be up front about it)
- clicky.log() events that your page fires in the first 500-1000ms probably won't be logged

These are explained in further detail on the tracking code page, so please read the whole thing before deploying this code!
7 comments |   Mar 23 2010 12:37pm

Content Distribution Network Map

Our custom built CDN is running very smoothly and, thanks to VPS.net, quite affordably as well. We thought you might like to see a map of where our CDN servers are currently located, and where we plan to expand to in the future.


getclicky.com content distribution network



For Tokyo, we're awaiting VPS.net's deployment into Japan, which is supposedly coming relatively soon. For Melbourne and Sao Paulo (sorry, lame blog software doesn't let us input squiggly a's), we're waiting for Dyn (our new DNS provider) to add their own servers in these areas so we can send targeted traffic to them. We're expecting all of this to happen within the next 6 months.

Until then, the majority of our users are in the US, Europe, SE Asia, and Australia, so with the exception of Australia, you are all being serviced very well - and the ping times from Australia to Malaysia aren't that bad.

Also, our CDN isn't currently compatible with our white label service, but that's about to change, so stay tuned.
14 comments |   Mar 22 2010 2:25pm

Next Page »




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