O:9:"MagpieRSS":19:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:40:{i:0;a:9:{s:5:"title";s:35:"New Apps  Plugins page. About time!";s:4:"link";s:88:"http://feedproxy.google.com/~r/getclicky/~3/q63Zm4slGrM/new-apps-plugins-page-about-time";s:8:"comments";s:62:"http://getclicky.com/blog/252/new-apps-plugins-page-about-time";s:4:"guid";s:62:"http://getclicky.com/blog/252/new-apps-plugins-page-about-time";s:11:"description";s:2234:"Oh man did our old integration help page need an overhaul. Other than adding links to some new plugins as they were brought into our knowledge, it hadn't been updated at all since 2007! And boy was it <i>ugly</i>. Plus, there was no mention of any of the apps that people have written for Clicky, such as <a href=http://clickytouch.com>ClickyTouch</a> or <a href=https://chrome.google.com/extensions/detail/nhdlcoplfdhmdbeleincmcnmgdajohig>ClickyChrome</a>, anywhere on our site. (Other than blog posts announcing them, which soon disappear into the great ether.)<br />
<br />
Unacceptable! I just spent the last four hours redoing the entire page, making it very quick and easy to find and install all of the applications and plugins that our awesome customers have developed over the years. Not a single piece of software on this page was written by us. It's all you and we love you for it! I also added a link to it in our main sidebar navigation that you see on all pages other than when viewing reports, because we want as many people as possible to know about all of this great software.<br />
<br />
<a href=http://getclicky.com/help/apps-plugins>Check out the new Apps  Plugins page here</a>. And if you know of an app or plugin that's not listed there, or one you may have written yourself, let us know about it! We will be more than happy to add it to this page.<br />
<br />
<br />
<br />
<a href=http://getclicky.com/help/apps-plugins><img src=http://static.getclicky.com/media/screenshots/201102-apps-plugins.gif></a><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=q63Zm4slGrM:bFWWRkoNoos:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=q63Zm4slGrM:bFWWRkoNoos:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=q63Zm4slGrM:bFWWRkoNoos:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=q63Zm4slGrM:bFWWRkoNoos:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=q63Zm4slGrM:bFWWRkoNoos:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/q63Zm4slGrM" height="1" width="1"/>";s:7:"pubdate";s:31:"Tue, 01 Mar 2011 23:20:18 -0800";s:5:"bonus";s:10:"1299050418";s:10:"feedburner";a:1:{s:8:"origlink";s:62:"http://getclicky.com/blog/252/new-apps-plugins-page-about-time";}s:7:"summary";s:2234:"Oh man did our old integration help page need an overhaul. Other than adding links to some new plugins as they were brought into our knowledge, it hadn't been updated at all since 2007! And boy was it <i>ugly</i>. Plus, there was no mention of any of the apps that people have written for Clicky, such as <a href=http://clickytouch.com>ClickyTouch</a> or <a href=https://chrome.google.com/extensions/detail/nhdlcoplfdhmdbeleincmcnmgdajohig>ClickyChrome</a>, anywhere on our site. (Other than blog posts announcing them, which soon disappear into the great ether.)<br />
<br />
Unacceptable! I just spent the last four hours redoing the entire page, making it very quick and easy to find and install all of the applications and plugins that our awesome customers have developed over the years. Not a single piece of software on this page was written by us. It's all you and we love you for it! I also added a link to it in our main sidebar navigation that you see on all pages other than when viewing reports, because we want as many people as possible to know about all of this great software.<br />
<br />
<a href=http://getclicky.com/help/apps-plugins>Check out the new Apps  Plugins page here</a>. And if you know of an app or plugin that's not listed there, or one you may have written yourself, let us know about it! We will be more than happy to add it to this page.<br />
<br />
<br />
<br />
<a href=http://getclicky.com/help/apps-plugins><img src=http://static.getclicky.com/media/screenshots/201102-apps-plugins.gif></a><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=q63Zm4slGrM:bFWWRkoNoos:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=q63Zm4slGrM:bFWWRkoNoos:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=q63Zm4slGrM:bFWWRkoNoos:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=q63Zm4slGrM:bFWWRkoNoos:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=q63Zm4slGrM:bFWWRkoNoos:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/q63Zm4slGrM" height="1" width="1"/>";}i:1;a:9:{s:5:"title";s:86:"New preferences to disable Ajax, and force the navigation to always side or always top";s:4:"link";s:141:"http://feedproxy.google.com/~r/getclicky/~3/jWtkpqsEo4I/new-preferences-to-disable-ajax-and-force-the-navigation-to-always-side-or-always-top";s:8:"comments";s:115:"http://getclicky.com/blog/251/new-preferences-to-disable-ajax-and-force-the-navigation-to-always-side-or-always-top";s:4:"guid";s:115:"http://getclicky.com/blog/251/new-preferences-to-disable-ajax-and-force-the-navigation-to-always-side-or-always-top";s:11:"description";s:2802:"We added two new much-requested features today: the ability to disable the Ajax navigation or our site, and the ability to force the navigation to always be in a sidebar or always be on top. These are account wide preferences, and you can set them by clicking the <a href=http://getclicky.com/user/edit>account link</a> on your user homepage.<br />
<br />
<h3>No Ajax</h3>I love Ajax but it's not for everybody. And it can be slightly buggy sometimes. So if you don't like, turn it off. Just know this: Clicky has ridiculous amount of Javascript code powering it. The great thing about Ajax is that the entire page is never reloaded, so this ginormous amount of code only ever has to be parsed by your browser one time. With Ajax turned off, every click results in an entirely new page view, which means all of that code (over 300KB of it) has to be re-parsed by your web browser. <i>For every page view.</i> The site feels about half as fast to me without Ajax, but luckily I realize that each one of my customers is a unique and beautiful snowflake and hence they have their own preferences.<br />
<br />
<h3>Forced navigation</h3>By default, our navigation is dynamically placed on either the top of your browser window, or in a sidebar, depending on how big the window is. But some of you always want it in one place or the other. And you get understandably confused when your shiny amazing computer at home hooked up to a 30 monitor shows Clicky in its full glory as it was meant to be, but your 386 at work with 5 pixels of total screen resolution that your boss got for a steal on eBay shows the navigation in a different place. Now you can fix it by setting this preference.<br />
<br />
<h3>UPDATE: No auto-refresh</h3>We had a user request the option to disable the auto-refreshing of reports. This happens when you're away for at least 5 minutes, as soon as we detect mouse activity we refresh the report. This new preference has been added to your account preferences page.<br />
<br />
The power is yours!<br />
<br />
<img src=http://static.getclicky.com/media/pix/captain-planet.jpg><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=jWtkpqsEo4I:lDE5fDEA3Pk:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=jWtkpqsEo4I:lDE5fDEA3Pk:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=jWtkpqsEo4I:lDE5fDEA3Pk:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=jWtkpqsEo4I:lDE5fDEA3Pk:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=jWtkpqsEo4I:lDE5fDEA3Pk:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/jWtkpqsEo4I" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 28 Feb 2011 17:13:15 -0800";s:5:"bonus";s:10:"1298941995";s:10:"feedburner";a:1:{s:8:"origlink";s:115:"http://getclicky.com/blog/251/new-preferences-to-disable-ajax-and-force-the-navigation-to-always-side-or-always-top";}s:7:"summary";s:2802:"We added two new much-requested features today: the ability to disable the Ajax navigation or our site, and the ability to force the navigation to always be in a sidebar or always be on top. These are account wide preferences, and you can set them by clicking the <a href=http://getclicky.com/user/edit>account link</a> on your user homepage.<br />
<br />
<h3>No Ajax</h3>I love Ajax but it's not for everybody. And it can be slightly buggy sometimes. So if you don't like, turn it off. Just know this: Clicky has ridiculous amount of Javascript code powering it. The great thing about Ajax is that the entire page is never reloaded, so this ginormous amount of code only ever has to be parsed by your browser one time. With Ajax turned off, every click results in an entirely new page view, which means all of that code (over 300KB of it) has to be re-parsed by your web browser. <i>For every page view.</i> The site feels about half as fast to me without Ajax, but luckily I realize that each one of my customers is a unique and beautiful snowflake and hence they have their own preferences.<br />
<br />
<h3>Forced navigation</h3>By default, our navigation is dynamically placed on either the top of your browser window, or in a sidebar, depending on how big the window is. But some of you always want it in one place or the other. And you get understandably confused when your shiny amazing computer at home hooked up to a 30 monitor shows Clicky in its full glory as it was meant to be, but your 386 at work with 5 pixels of total screen resolution that your boss got for a steal on eBay shows the navigation in a different place. Now you can fix it by setting this preference.<br />
<br />
<h3>UPDATE: No auto-refresh</h3>We had a user request the option to disable the auto-refreshing of reports. This happens when you're away for at least 5 minutes, as soon as we detect mouse activity we refresh the report. This new preference has been added to your account preferences page.<br />
<br />
The power is yours!<br />
<br />
<img src=http://static.getclicky.com/media/pix/captain-planet.jpg><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=jWtkpqsEo4I:lDE5fDEA3Pk:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=jWtkpqsEo4I:lDE5fDEA3Pk:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=jWtkpqsEo4I:lDE5fDEA3Pk:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=jWtkpqsEo4I:lDE5fDEA3Pk:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=jWtkpqsEo4I:lDE5fDEA3Pk:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/jWtkpqsEo4I" height="1" width="1"/>";}i:2;a:9:{s:5:"title";s:33:"Chat with your visitors from Spy!";s:4:"link";s:88:"http://feedproxy.google.com/~r/getclicky/~3/MDeI-xVNTtY/chat-with-your-visitors-from-spy";s:8:"comments";s:62:"http://getclicky.com/blog/250/chat-with-your-visitors-from-spy";s:4:"guid";s:62:"http://getclicky.com/blog/250/chat-with-your-visitors-from-spy";s:11:"description";s:3662:"We get a lot of requests to implement a visitor chat feature. We also have a lot of users who have <a href=http://olark.com>Olark</a> installed on their web site, which is a visitor chat service. Rather than write our own chat service, which is not really something we wanted to do, we decided to implement Olark chat right into Spy.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-olark.png><br />
<br />
<br />
We wanted to make the implementation as easy as possible, so good news: if you already have Olark installed on your site, you don't need to do a gosh darn thing. Our code detects their code and vice versa, and anything that needs to happen between our services happens automatically. Nice eh?<br />
<br />
Ideally, a new browser window or tab would open when you click the chat link, but Olark doesn't have a web chat feature on the operator end (operator = you). They say they may add that in the future, and if they do we will switch to that. For now, they support operating chat via Jabber and Google Talk (standalone, or within Gmail). When you click the chat link for a visitor in Spy, you will get a new IM immediately, telling you that you have initiated a chat from Clicky Spy. Just start typing in that box to start chatting with the visitor.<br />
<br />
Olark works on a freemium model, but the free service isn't lacking any features. The only limit on the free account is how many chats you can do per month. The free plan allows up to 15 chats per month, which is completely reasonable. Unless you want to spend all day chatting with your visitors, we doubt many people will go over this limit. <a href=http://olark.com>Sign up for an Olark account here</a>.<br />
<br />
You may notice some visitors won't have a chat link, at least initially. Here are a few reasons why that might happen:<br />
<ul><li>Since our entire site is Ajax-based now, you might need to refresh the entire page to make your browser load a new copy of our Spy Javascript, without which there will be no chat links.<br />
<li>We just updated the tracking code today with the new Olark integration, so it will be up to one week before all of your visitors are guaranteed to have the latest tracking code loaded in their browsers.<br />
<li>You can only chat with online visitors. If you have a lowish traffic site, the last 40 actions displayed might not all be from visitors who are online right now. Chatting with visitors who are no longer online makes no sense, so those visitors will not have a chat link next to them.<br />
<li>If you are self-hosting the tracking code (<i>which is no longer supported!</i>), you will need to grab a fresh copy.<br />
<li>The visitor may be blocking Olark's code in their browser. This is highly unlikely, but possible.<br />
<li>There might be some weird bug in our code. If a week has gone by and for some reason a lot of your visitors still don't have a chat link, send us an email.</ul><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=MDeI-xVNTtY:DTEvpY_jE5k:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=MDeI-xVNTtY:DTEvpY_jE5k:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=MDeI-xVNTtY:DTEvpY_jE5k:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=MDeI-xVNTtY:DTEvpY_jE5k:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=MDeI-xVNTtY:DTEvpY_jE5k:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/MDeI-xVNTtY" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 21 Feb 2011 20:13:59 -0800";s:5:"bonus";s:10:"1298348039";s:10:"feedburner";a:1:{s:8:"origlink";s:62:"http://getclicky.com/blog/250/chat-with-your-visitors-from-spy";}s:7:"summary";s:3662:"We get a lot of requests to implement a visitor chat feature. We also have a lot of users who have <a href=http://olark.com>Olark</a> installed on their web site, which is a visitor chat service. Rather than write our own chat service, which is not really something we wanted to do, we decided to implement Olark chat right into Spy.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-olark.png><br />
<br />
<br />
We wanted to make the implementation as easy as possible, so good news: if you already have Olark installed on your site, you don't need to do a gosh darn thing. Our code detects their code and vice versa, and anything that needs to happen between our services happens automatically. Nice eh?<br />
<br />
Ideally, a new browser window or tab would open when you click the chat link, but Olark doesn't have a web chat feature on the operator end (operator = you). They say they may add that in the future, and if they do we will switch to that. For now, they support operating chat via Jabber and Google Talk (standalone, or within Gmail). When you click the chat link for a visitor in Spy, you will get a new IM immediately, telling you that you have initiated a chat from Clicky Spy. Just start typing in that box to start chatting with the visitor.<br />
<br />
Olark works on a freemium model, but the free service isn't lacking any features. The only limit on the free account is how many chats you can do per month. The free plan allows up to 15 chats per month, which is completely reasonable. Unless you want to spend all day chatting with your visitors, we doubt many people will go over this limit. <a href=http://olark.com>Sign up for an Olark account here</a>.<br />
<br />
You may notice some visitors won't have a chat link, at least initially. Here are a few reasons why that might happen:<br />
<ul><li>Since our entire site is Ajax-based now, you might need to refresh the entire page to make your browser load a new copy of our Spy Javascript, without which there will be no chat links.<br />
<li>We just updated the tracking code today with the new Olark integration, so it will be up to one week before all of your visitors are guaranteed to have the latest tracking code loaded in their browsers.<br />
<li>You can only chat with online visitors. If you have a lowish traffic site, the last 40 actions displayed might not all be from visitors who are online right now. Chatting with visitors who are no longer online makes no sense, so those visitors will not have a chat link next to them.<br />
<li>If you are self-hosting the tracking code (<i>which is no longer supported!</i>), you will need to grab a fresh copy.<br />
<li>The visitor may be blocking Olark's code in their browser. This is highly unlikely, but possible.<br />
<li>There might be some weird bug in our code. If a week has gone by and for some reason a lot of your visitors still don't have a chat link, send us an email.</ul><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=MDeI-xVNTtY:DTEvpY_jE5k:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=MDeI-xVNTtY:DTEvpY_jE5k:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=MDeI-xVNTtY:DTEvpY_jE5k:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=MDeI-xVNTtY:DTEvpY_jE5k:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=MDeI-xVNTtY:DTEvpY_jE5k:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/MDeI-xVNTtY" height="1" width="1"/>";}i:3;a:9:{s:5:"title";s:65:"Split testing, new features for goals, and better visitor history";s:4:"link";s:119:"http://feedproxy.google.com/~r/getclicky/~3/1Mn2EDEoJ8U/split-testing-new-features-for-goals-and-better-visitor-history";s:8:"comments";s:93:"http://getclicky.com/blog/249/split-testing-new-features-for-goals-and-better-visitor-history";s:4:"guid";s:93:"http://getclicky.com/blog/249/split-testing-new-features-for-goals-and-better-visitor-history";s:11:"description";s:6309:"Alrighty, yesterday I went over a few new features after they were released, but that was just so you didn't think they were broken :) If you haven't read that post yet, please <a href=http://getclicky.com/blog/248/new-features-some-of-them-might-seem-broken-and-heres-why>read it here</a>, so you understand a few limitations of the new features until some historical post processing has been completed.<br />
<br />
<h3>Split testing</h3>We now have built in support for split testing. We're planning on using this extensively on getclicky.com itself, but we wanted to get it out as soon as possible so we haven't created any tests yet. But I wanted to have a screenshot for you, so I created a fake split test on our user registration page. There was no actual difference between what the visitors saw, we were just telling Clicky tracking that there was. Here's what it looks like:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-split-tests.png><br />
<br />
As should be evident, to make your split tests valid, you need a good sample size. There was absolutely no difference between what these visitors saw, yet the conversion rates are 49% vs 37%. I'll let this run indefinitely, at least until we get two different registration pages to actually test, to see what the differences end up being. They should converge with time.<br />
<br />
More details on setting up split tests are included on the main goals setup page. When you create a split test, you can choose what specific goals you want to track conversions for (as we did here, we're just tracking our new user goal instead of all goals), or you can let it default to tracking conversions for all goals. Both options have their ups and downs so it depends on what you're doing.<br />
<br />
If you want to use a GUI interface to design your split tests, we have partnered with <a href=http://app.visualwebsiteoptimizer.com/create-account-clicky.php>Visual Website Optimizer</a> to provide that for you. More details on that are also on the goal setup page.<br />
<br />
<br />
<h3>Better visitor history</h3>Previously we were tracking the time of someone's first visit to your site, but now how many times they visited. Nor did we keep track of their first session ID. That's all fixed now! When viewing any visitor's details, you'll see how many total times they have visited your site, and the time of their first visit is now a link directly to that session, so you can see what they did on your site and how they got there (search etc) the first time they showed up.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-visitor-details.png><br />
<br />
<br />
<br />
<h3>Dynamic goals</h3>Goals no longer need to be pre-defined. They still can be of course, but you now have the option to define them on the fly within Javascript. Dynamic goals have no limits, so that's the a huge benefit. Downside is you can't customize them (e.g. choose an icon) or use them with funnels.<br />
<br />
<br />
<h3>New goal report</h3>We've updated the main goal report to include a few new pieces of information. Tracking conversions is great, but wouldn't it also be nice to know how long it takes the average visitor to convert? That's exactly what we've added! Here's a snippet of our goal report, showing two goals that are very important to us - how many new people are registering, and how many people are upgrading. We offer a 21 day trial when new people register, but on average people are upgrading after only 14 days. That's fantastic! And for new users, it looks like the average person registers on their second visit after a 4 day lull from their first visit. Interesting! Of course, this is only about 12 hours of data, so it doesn't tell the whole story. A bigger sample size will give us a more accurate picture of how you use Clicky.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-goals.png><br />
<br />
<br />
<br />
<h3>Better goal integration in all reports</h3>When viewing any report, previously we had an extra column for conversions and conversion rate for each segment. However, the way we were calculating this wasn't taking into account which specific goals that segment was completing. It was just keeping an overall tally, and when you clicked the conversion number, it would filter your visitors down to those who had completed any goal for whatever segment you were viewing.<br />
<br />
Now we'll show way more up front. As you can see int he screenshot below, we've added inline revenue to the reports, and when you click on the conversion number, it pops up a menu showing you all the individual goals that segment has completed, ordered most to least. You can click on any of those goals to immediately filter your visitors down to just that segment+goal, or click the all visitors link at the bottom to view visitors from that segment who have completed ANY goal.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-goals-menu.png><br />
<br />
<br />
<h3>Cookie domain</h3>You can now specify the domain for the tracking cookie we set, instead of just .yoursite.com by default. It's a bit complicated and you should really only do this if you know what you're doing, but we've had requests for it so here it is. See docs <a href=http://getclicky.com/help/customization#cookie_domain>here</a><br />
<br />
<br />
That's all the major stuff. There's a few other little goodies here and there. e.g. all split testing data is available via the API, and has been added to the iPhone web app too. Hope you enjoy!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=1Mn2EDEoJ8U:scywAN8Xam8:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=1Mn2EDEoJ8U:scywAN8Xam8:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=1Mn2EDEoJ8U:scywAN8Xam8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=1Mn2EDEoJ8U:scywAN8Xam8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=1Mn2EDEoJ8U:scywAN8Xam8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/1Mn2EDEoJ8U" height="1" width="1"/>";s:7:"pubdate";s:31:"Fri, 11 Feb 2011 14:35:09 -0800";s:5:"bonus";s:10:"1297463709";s:10:"feedburner";a:1:{s:8:"origlink";s:93:"http://getclicky.com/blog/249/split-testing-new-features-for-goals-and-better-visitor-history";}s:7:"summary";s:6309:"Alrighty, yesterday I went over a few new features after they were released, but that was just so you didn't think they were broken :) If you haven't read that post yet, please <a href=http://getclicky.com/blog/248/new-features-some-of-them-might-seem-broken-and-heres-why>read it here</a>, so you understand a few limitations of the new features until some historical post processing has been completed.<br />
<br />
<h3>Split testing</h3>We now have built in support for split testing. We're planning on using this extensively on getclicky.com itself, but we wanted to get it out as soon as possible so we haven't created any tests yet. But I wanted to have a screenshot for you, so I created a fake split test on our user registration page. There was no actual difference between what the visitors saw, we were just telling Clicky tracking that there was. Here's what it looks like:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-split-tests.png><br />
<br />
As should be evident, to make your split tests valid, you need a good sample size. There was absolutely no difference between what these visitors saw, yet the conversion rates are 49% vs 37%. I'll let this run indefinitely, at least until we get two different registration pages to actually test, to see what the differences end up being. They should converge with time.<br />
<br />
More details on setting up split tests are included on the main goals setup page. When you create a split test, you can choose what specific goals you want to track conversions for (as we did here, we're just tracking our new user goal instead of all goals), or you can let it default to tracking conversions for all goals. Both options have their ups and downs so it depends on what you're doing.<br />
<br />
If you want to use a GUI interface to design your split tests, we have partnered with <a href=http://app.visualwebsiteoptimizer.com/create-account-clicky.php>Visual Website Optimizer</a> to provide that for you. More details on that are also on the goal setup page.<br />
<br />
<br />
<h3>Better visitor history</h3>Previously we were tracking the time of someone's first visit to your site, but now how many times they visited. Nor did we keep track of their first session ID. That's all fixed now! When viewing any visitor's details, you'll see how many total times they have visited your site, and the time of their first visit is now a link directly to that session, so you can see what they did on your site and how they got there (search etc) the first time they showed up.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-visitor-details.png><br />
<br />
<br />
<br />
<h3>Dynamic goals</h3>Goals no longer need to be pre-defined. They still can be of course, but you now have the option to define them on the fly within Javascript. Dynamic goals have no limits, so that's the a huge benefit. Downside is you can't customize them (e.g. choose an icon) or use them with funnels.<br />
<br />
<br />
<h3>New goal report</h3>We've updated the main goal report to include a few new pieces of information. Tracking conversions is great, but wouldn't it also be nice to know how long it takes the average visitor to convert? That's exactly what we've added! Here's a snippet of our goal report, showing two goals that are very important to us - how many new people are registering, and how many people are upgrading. We offer a 21 day trial when new people register, but on average people are upgrading after only 14 days. That's fantastic! And for new users, it looks like the average person registers on their second visit after a 4 day lull from their first visit. Interesting! Of course, this is only about 12 hours of data, so it doesn't tell the whole story. A bigger sample size will give us a more accurate picture of how you use Clicky.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-goals.png><br />
<br />
<br />
<br />
<h3>Better goal integration in all reports</h3>When viewing any report, previously we had an extra column for conversions and conversion rate for each segment. However, the way we were calculating this wasn't taking into account which specific goals that segment was completing. It was just keeping an overall tally, and when you clicked the conversion number, it would filter your visitors down to those who had completed any goal for whatever segment you were viewing.<br />
<br />
Now we'll show way more up front. As you can see int he screenshot below, we've added inline revenue to the reports, and when you click on the conversion number, it pops up a menu showing you all the individual goals that segment has completed, ordered most to least. You can click on any of those goals to immediately filter your visitors down to just that segment+goal, or click the all visitors link at the bottom to view visitors from that segment who have completed ANY goal.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201102-goals-menu.png><br />
<br />
<br />
<h3>Cookie domain</h3>You can now specify the domain for the tracking cookie we set, instead of just .yoursite.com by default. It's a bit complicated and you should really only do this if you know what you're doing, but we've had requests for it so here it is. See docs <a href=http://getclicky.com/help/customization#cookie_domain>here</a><br />
<br />
<br />
That's all the major stuff. There's a few other little goodies here and there. e.g. all split testing data is available via the API, and has been added to the iPhone web app too. Hope you enjoy!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=1Mn2EDEoJ8U:scywAN8Xam8:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=1Mn2EDEoJ8U:scywAN8Xam8:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=1Mn2EDEoJ8U:scywAN8Xam8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=1Mn2EDEoJ8U:scywAN8Xam8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=1Mn2EDEoJ8U:scywAN8Xam8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/1Mn2EDEoJ8U" height="1" width="1"/>";}i:4;a:9:{s:5:"title";s:61:"New features. Some of them might seem broken, and here's why!";s:4:"link";s:113:"http://feedproxy.google.com/~r/getclicky/~3/Yj4PCtuJhWU/new-features-some-of-them-might-seem-broken-and-heres-why";s:8:"comments";s:87:"http://getclicky.com/blog/248/new-features-some-of-them-might-seem-broken-and-heres-why";s:4:"guid";s:87:"http://getclicky.com/blog/248/new-features-some-of-them-might-seem-broken-and-heres-why";s:11:"description";s:5849:"Our new release is out. It's been in the works for almost 30 days. There is metric happy ton of new stuff in here, especially if you use goals. But... it's been a LONG 48 hours preparing for some big database changes behind the scenes, so the last thing I want to do right now is write the nice, detailed blog post this release deserves. I'll do that after some sleep! Plus, that will give the database servers a chance to process some of the new data we're tracking, so I can show you screenshots of the new features with real data from Clicky's traffic.<br />
<br />
If you have no idea what's new, please see <a href=http://getclicky.com/blog/246/new-features-coming-soon>this post</a> from a few weeks ago, where we announced what was coming soon. There's a lot more to this release than in that post, but it covers most of the major points.<br />
<br />
<b>There are a few features I want to discuss right now</b>, because if I don't, you're going to think they're broken. That's because they rely on a core feature that we just added for unique visitors, where we now track how many times each unique person has visited your site, and the session ID of their first visit.<br />
<br />
Previous to today, we were not storing this information in an optimized way. Part of this update changes that, and hence we can use this information in a couple of interesting ways (with more to come in the future). <b>So, now we have the <i>ability</i> to store it, but that doesn't mean it's magically there already.</b> There are scripts running in the background that are parsing through data all the way back to April 16 2010, which is the date we started tracking true unique visitors. Based on the speed these scripts are running, we estimate it will take most database servers between 1 and 2 weeks to complete. So until that at least 2 weeks have passed, if you see some strange numbers - this is why.<br />
<br />
Here are the ways we are using this data right now:<br />
<br />
<h3>Visitor details: Link to first visit, and total visits</h3><br />
<img class=ml20 src=http://static.getclicky.com/media/screenshots/201102-first-visit.png><br />
<br />
When viewing visitor details, previously we only showed the date and time of their first visit. But now, we'll also give you a link directly to that first session. This allows you to quickly see what this visitor did the first time they visited your site. Quite interesting, if I do say so myself! But, until we have gone through the last 10 months of data and discovered their true first visit, the link probably won't be right. It will just be a link to their oldest session <i>as we have thus far determined</i>. You may notice we're also displaying the total numbers of time this person has visited. This also won't be accurate until this 10 month chunk of data has been fully processed.<br />
<br />
<br />
<h3>Goals: Time to goal, and visits to goal</h3><img class=ml20 src=http://static.getclicky.com/media/screenshots/201102-goals-time-visits.png width=600><br />
<br />
When a visitor completes a goal, we now check out how many total visits they've had and how long ago they first visited as of that point in time, and store that calculation in the database. When viewing your goal report, we'll show you the average of these two values for all visitors who have completed that goal for whatever date range you are viewing. This gives you a great way to gauge how quickly your visitors convert on average. (Also, we'll only use a visitor's data in this calculation the first time they complete a goal, so the numbers don't get skewed by people who complete the same goal multiple times. However, this aspect of your historical data is <i>not</i> being post-processed. So if you have goals that can be completed more than once, until most of your repeat customers have completed the goal at least one more time, these numbers may be wacky).<br />
<br />
The screenshot above is one of the goals we track, new user registration, as of about 30 minutes past midnight on this wonderful Friday morning. We have 13 new users, with the average user taking 2 visits and 1 day, 12 hours from the time of their first visit to when they finally registered. (I think there's a huge outlier here, when I viewed it about 5 minutes before snapping this screenshot, the average time was 3m 30s. I'm also noticing a bug now - the visits number is supposed to be rounded to the nearest tenth of a number, not to a whole number - I'll fix that tomorrow!)<br />
<br />
Since we were already tracking the time of their first visit, the time to goal value should be mostly correct (excluding your repeat customers for now), but the visits to goal will not be, until we have gone through this 10 month period of data for all of your visitors.<br />
<br />
-----<br />
<br />
This post was much longer than I expected, and I only covered 2 out of maybe 10 major new items. I will write a nice post tomorrow detailing everything that's new. I just wanted to clarify a few things tonight so you don't think these particular new features are broken - they just won't be accurate until a few weeks have passed.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=Yj4PCtuJhWU:p2diRc3bL_8:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Yj4PCtuJhWU:p2diRc3bL_8:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Yj4PCtuJhWU:p2diRc3bL_8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Yj4PCtuJhWU:p2diRc3bL_8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Yj4PCtuJhWU:p2diRc3bL_8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/Yj4PCtuJhWU" height="1" width="1"/>";s:7:"pubdate";s:31:"Fri, 11 Feb 2011 00:50:22 -0800";s:5:"bonus";s:10:"1297414222";s:10:"feedburner";a:1:{s:8:"origlink";s:87:"http://getclicky.com/blog/248/new-features-some-of-them-might-seem-broken-and-heres-why";}s:7:"summary";s:5849:"Our new release is out. It's been in the works for almost 30 days. There is metric happy ton of new stuff in here, especially if you use goals. But... it's been a LONG 48 hours preparing for some big database changes behind the scenes, so the last thing I want to do right now is write the nice, detailed blog post this release deserves. I'll do that after some sleep! Plus, that will give the database servers a chance to process some of the new data we're tracking, so I can show you screenshots of the new features with real data from Clicky's traffic.<br />
<br />
If you have no idea what's new, please see <a href=http://getclicky.com/blog/246/new-features-coming-soon>this post</a> from a few weeks ago, where we announced what was coming soon. There's a lot more to this release than in that post, but it covers most of the major points.<br />
<br />
<b>There are a few features I want to discuss right now</b>, because if I don't, you're going to think they're broken. That's because they rely on a core feature that we just added for unique visitors, where we now track how many times each unique person has visited your site, and the session ID of their first visit.<br />
<br />
Previous to today, we were not storing this information in an optimized way. Part of this update changes that, and hence we can use this information in a couple of interesting ways (with more to come in the future). <b>So, now we have the <i>ability</i> to store it, but that doesn't mean it's magically there already.</b> There are scripts running in the background that are parsing through data all the way back to April 16 2010, which is the date we started tracking true unique visitors. Based on the speed these scripts are running, we estimate it will take most database servers between 1 and 2 weeks to complete. So until that at least 2 weeks have passed, if you see some strange numbers - this is why.<br />
<br />
Here are the ways we are using this data right now:<br />
<br />
<h3>Visitor details: Link to first visit, and total visits</h3><br />
<img class=ml20 src=http://static.getclicky.com/media/screenshots/201102-first-visit.png><br />
<br />
When viewing visitor details, previously we only showed the date and time of their first visit. But now, we'll also give you a link directly to that first session. This allows you to quickly see what this visitor did the first time they visited your site. Quite interesting, if I do say so myself! But, until we have gone through the last 10 months of data and discovered their true first visit, the link probably won't be right. It will just be a link to their oldest session <i>as we have thus far determined</i>. You may notice we're also displaying the total numbers of time this person has visited. This also won't be accurate until this 10 month chunk of data has been fully processed.<br />
<br />
<br />
<h3>Goals: Time to goal, and visits to goal</h3><img class=ml20 src=http://static.getclicky.com/media/screenshots/201102-goals-time-visits.png width=600><br />
<br />
When a visitor completes a goal, we now check out how many total visits they've had and how long ago they first visited as of that point in time, and store that calculation in the database. When viewing your goal report, we'll show you the average of these two values for all visitors who have completed that goal for whatever date range you are viewing. This gives you a great way to gauge how quickly your visitors convert on average. (Also, we'll only use a visitor's data in this calculation the first time they complete a goal, so the numbers don't get skewed by people who complete the same goal multiple times. However, this aspect of your historical data is <i>not</i> being post-processed. So if you have goals that can be completed more than once, until most of your repeat customers have completed the goal at least one more time, these numbers may be wacky).<br />
<br />
The screenshot above is one of the goals we track, new user registration, as of about 30 minutes past midnight on this wonderful Friday morning. We have 13 new users, with the average user taking 2 visits and 1 day, 12 hours from the time of their first visit to when they finally registered. (I think there's a huge outlier here, when I viewed it about 5 minutes before snapping this screenshot, the average time was 3m 30s. I'm also noticing a bug now - the visits number is supposed to be rounded to the nearest tenth of a number, not to a whole number - I'll fix that tomorrow!)<br />
<br />
Since we were already tracking the time of their first visit, the time to goal value should be mostly correct (excluding your repeat customers for now), but the visits to goal will not be, until we have gone through this 10 month period of data for all of your visitors.<br />
<br />
-----<br />
<br />
This post was much longer than I expected, and I only covered 2 out of maybe 10 major new items. I will write a nice post tomorrow detailing everything that's new. I just wanted to clarify a few things tonight so you don't think these particular new features are broken - they just won't be accurate until a few weeks have passed.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=Yj4PCtuJhWU:p2diRc3bL_8:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Yj4PCtuJhWU:p2diRc3bL_8:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Yj4PCtuJhWU:p2diRc3bL_8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Yj4PCtuJhWU:p2diRc3bL_8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Yj4PCtuJhWU:p2diRc3bL_8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/Yj4PCtuJhWU" height="1" width="1"/>";}i:5;a:9:{s:5:"title";s:32:"Quick downtime Saturday ~6pm PST";s:4:"link";s:87:"http://feedproxy.google.com/~r/getclicky/~3/-yejb84zk8s/quick-downtime-saturday-6pm-pst";s:8:"comments";s:61:"http://getclicky.com/blog/247/quick-downtime-saturday-6pm-pst";s:4:"guid";s:61:"http://getclicky.com/blog/247/quick-downtime-saturday-6pm-pst";s:11:"description";s:1855:"Our network host is requiring all customers to move their servers into a new server room they built last year. We've been putting this off for as long as possible, but the moment of truth has arrived.<br />
<br />
We will try our hardest so there's no time when our network is actually 100% offline, because that affects your web sites. The plan is to move one of the paired load balancers and one of the tracking servers into the new room, then take the other stuff offline and let the already-moved LB and tracking server take over tracking temporarily. When the other servers are moved and come back online, everything will magically pair back together. This way there won't be more than a 5-10 second blip, and no tracking data will be lost.<br />
<br />
The site will be in maintenance mode during the move, which we expect to take about an hour. When the database servers come back online, they will be behind real time by about an hour, so they will take a little bit to catch back up.<br />
<br />
We've had our servers in the same set of racks in the same physical room for more than 4 years, so we don't expect to have to do this ever again.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=-yejb84zk8s:aS49ZxCRSNA:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=-yejb84zk8s:aS49ZxCRSNA:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=-yejb84zk8s:aS49ZxCRSNA:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=-yejb84zk8s:aS49ZxCRSNA:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=-yejb84zk8s:aS49ZxCRSNA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/-yejb84zk8s" height="1" width="1"/>";s:7:"pubdate";s:31:"Fri, 04 Feb 2011 19:26:38 -0800";s:5:"bonus";s:10:"1296876398";s:10:"feedburner";a:1:{s:8:"origlink";s:61:"http://getclicky.com/blog/247/quick-downtime-saturday-6pm-pst";}s:7:"summary";s:1855:"Our network host is requiring all customers to move their servers into a new server room they built last year. We've been putting this off for as long as possible, but the moment of truth has arrived.<br />
<br />
We will try our hardest so there's no time when our network is actually 100% offline, because that affects your web sites. The plan is to move one of the paired load balancers and one of the tracking servers into the new room, then take the other stuff offline and let the already-moved LB and tracking server take over tracking temporarily. When the other servers are moved and come back online, everything will magically pair back together. This way there won't be more than a 5-10 second blip, and no tracking data will be lost.<br />
<br />
The site will be in maintenance mode during the move, which we expect to take about an hour. When the database servers come back online, they will be behind real time by about an hour, so they will take a little bit to catch back up.<br />
<br />
We've had our servers in the same set of racks in the same physical room for more than 4 years, so we don't expect to have to do this ever again.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=-yejb84zk8s:aS49ZxCRSNA:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=-yejb84zk8s:aS49ZxCRSNA:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=-yejb84zk8s:aS49ZxCRSNA:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=-yejb84zk8s:aS49ZxCRSNA:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=-yejb84zk8s:aS49ZxCRSNA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/-yejb84zk8s" height="1" width="1"/>";}i:6;a:9:{s:5:"title";s:24:"New features coming soon";s:4:"link";s:80:"http://feedproxy.google.com/~r/getclicky/~3/9Ngmdibksdo/new-features-coming-soon";s:8:"comments";s:54:"http://getclicky.com/blog/246/new-features-coming-soon";s:4:"guid";s:54:"http://getclicky.com/blog/246/new-features-coming-soon";s:11:"description";s:3524:"It's been pretty quiet around these parts recently, so in case anyone was wondering if we were asleep at the wheel, the answer is NO! We took a few weeks off for the holidays but have been hard at work on lots of new goodies for the last two weeks. I just wanted to outlay what you can look forward to in our new release, which should be out by the end of this month.<br />
<br />
<ul><li><b>Split testing</b> - split tests will be defined 100% dynamically using our <a href=http://getclicky.com/help/customization>clicky_custom</a> javascript object, which means there will be no limits on how many tests or versions of each test you can have, and no annoying forms to fill out. You'll also be able to define the specific goal you want to track for this split test, so that we only calculate the best version of your test based on one goal which is likely desired the majority of the time. Otherwise, we'll be tracking <i>all goals</i> that occur after this person visits one of your split pages.<br />
<br />
<li><b>Dynamic goals</b> - For campaigns, we support both static and dynamic campaigns, so you don't have to define them first if you don't want to. We'll be adding the same thing to goals. One reason is to allow you to have more goals - there won't be any limits with dynamic goals. Secondly, we think it's easier to not have to predefine everything. This makes sense especially when combined with our new split testing feature. You will be able to define both your split tests and the goal you want to track for that test on the fly (if you want).<br />
<br />
<li><b>Total number of visits per unique visitor</b> - this seems obvious but we're not currently tracking it directly. That's going to change so we can quickly query this value for any of your visitors. This will be particularly useful for goals, so you can see how many visits it takes the average person to complete any of your web site's goals (we'll be adding this as a new column in the main goal report). We'll also be reporting the average <i>time</i> too, which will be based on the time of each unique visitor's <a href=http://getclicky.com/blog/227/when-did-visitor-xyz-first-visit-my-site>first visit</a> to your site.<br />
<br />
<li><b>Customizable cookie domain</b> - If you don't know what this means without further explanation, it probably won't be something you want or need. But, we have had a number of users ask to be able to set this to something other than the default .yoursite.com, so you'll have that option now.</ul><br />
<br />
As we develop new features, other ideas or tweaks for those features usually come to us constantly. So, chances are there will probably be some extra stuff other than what's outlined above. We'll dive into much greater detail about each new feature in a new blog post when it's released.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=9Ngmdibksdo:o6dt9u22EwU:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=9Ngmdibksdo:o6dt9u22EwU:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=9Ngmdibksdo:o6dt9u22EwU:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=9Ngmdibksdo:o6dt9u22EwU:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=9Ngmdibksdo:o6dt9u22EwU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/9Ngmdibksdo" height="1" width="1"/>";s:7:"pubdate";s:31:"Wed, 19 Jan 2011 15:47:49 -0800";s:5:"bonus";s:10:"1295480869";s:10:"feedburner";a:1:{s:8:"origlink";s:54:"http://getclicky.com/blog/246/new-features-coming-soon";}s:7:"summary";s:3524:"It's been pretty quiet around these parts recently, so in case anyone was wondering if we were asleep at the wheel, the answer is NO! We took a few weeks off for the holidays but have been hard at work on lots of new goodies for the last two weeks. I just wanted to outlay what you can look forward to in our new release, which should be out by the end of this month.<br />
<br />
<ul><li><b>Split testing</b> - split tests will be defined 100% dynamically using our <a href=http://getclicky.com/help/customization>clicky_custom</a> javascript object, which means there will be no limits on how many tests or versions of each test you can have, and no annoying forms to fill out. You'll also be able to define the specific goal you want to track for this split test, so that we only calculate the best version of your test based on one goal which is likely desired the majority of the time. Otherwise, we'll be tracking <i>all goals</i> that occur after this person visits one of your split pages.<br />
<br />
<li><b>Dynamic goals</b> - For campaigns, we support both static and dynamic campaigns, so you don't have to define them first if you don't want to. We'll be adding the same thing to goals. One reason is to allow you to have more goals - there won't be any limits with dynamic goals. Secondly, we think it's easier to not have to predefine everything. This makes sense especially when combined with our new split testing feature. You will be able to define both your split tests and the goal you want to track for that test on the fly (if you want).<br />
<br />
<li><b>Total number of visits per unique visitor</b> - this seems obvious but we're not currently tracking it directly. That's going to change so we can quickly query this value for any of your visitors. This will be particularly useful for goals, so you can see how many visits it takes the average person to complete any of your web site's goals (we'll be adding this as a new column in the main goal report). We'll also be reporting the average <i>time</i> too, which will be based on the time of each unique visitor's <a href=http://getclicky.com/blog/227/when-did-visitor-xyz-first-visit-my-site>first visit</a> to your site.<br />
<br />
<li><b>Customizable cookie domain</b> - If you don't know what this means without further explanation, it probably won't be something you want or need. But, we have had a number of users ask to be able to set this to something other than the default .yoursite.com, so you'll have that option now.</ul><br />
<br />
As we develop new features, other ideas or tweaks for those features usually come to us constantly. So, chances are there will probably be some extra stuff other than what's outlined above. We'll dive into much greater detail about each new feature in a new blog post when it's released.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=9Ngmdibksdo:o6dt9u22EwU:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=9Ngmdibksdo:o6dt9u22EwU:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=9Ngmdibksdo:o6dt9u22EwU:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=9Ngmdibksdo:o6dt9u22EwU:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=9Ngmdibksdo:o6dt9u22EwU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/9Ngmdibksdo" height="1" width="1"/>";}i:7;a:9:{s:5:"title";s:36:"'Media searches' and other new stuff";s:4:"link";s:90:"http://feedproxy.google.com/~r/getclicky/~3/A9J4khyqPZo/media-searches-and-other-new-stuff";s:8:"comments";s:64:"http://getclicky.com/blog/245/media-searches-and-other-new-stuff";s:4:"guid";s:64:"http://getclicky.com/blog/245/media-searches-and-other-new-stuff";s:11:"description";s:2981:"One of our most requested features has been to segment out image searches from normal searches. We have just added this, so you should start seeing a new entry in your traffic sources report:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201012-media-searches.gif><br />
<br />
<br />
This feature has been requested countless times, as far back as <a href=http://getclicky.com/forums/?id=269>June 2008</a>. We're calling it media searches instead of image searches, since we want to be as general as possible and may add support for video searches or other types of media in the future. Image searches from Google, Yahoo, and Bing are supported at the moment. We've also renamed Direct / Bookmark to just Direct, and RSS readers to Syndication.<br />
<br />
Other new features and bug fixes from today:<br />
<ul><li>Windows phone 7 detection (will show up as just Windows phone though)<br />
<li>The new Google Web Preview bot is now blocked by default <a href=http://getclicky.com/forums/?id=6892>as requested</a><br />
<li>AOL recently moved to q as the default search parameter in their search engine, so their searches were just showing up as links in Clicky. We've updated our code to support this new parameter. It still supports the old ones too (query and encquery) in case those are still used anywhere.<br />
<li>In October, <a href=http://getclicky.com/blog/237/google-ad-clicks-and-ajax-searches>we added support</a> for google.com/aclk referrers, which is what we see when someone clicks on a paid search on Google. However, there's been a bug where these were referrers were showing up in your main links report, which normally only shows non-search referrers. We've fixed this bug, which was probably quite annoying for those of you running paid searches on Google.</ul><br />
<br />
That's all for today! You should start seeing us go back to our regular feature release schedule, where we release new stuff almost every week. The last few months have been insanely hectic from the <a href=http://getclicky.com/blog/235/the-new-clicky>massive redesign</a> and tons of traveling and a big partnership integration we'll be announcing soon. We are excited to get back into the groove of writing lots of code because that's what we live for.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=A9J4khyqPZo:vEtadNTp6gQ:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=A9J4khyqPZo:vEtadNTp6gQ:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=A9J4khyqPZo:vEtadNTp6gQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=A9J4khyqPZo:vEtadNTp6gQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=A9J4khyqPZo:vEtadNTp6gQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/A9J4khyqPZo" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 06 Dec 2010 17:29:05 -0800";s:5:"bonus";s:10:"1291685345";s:10:"feedburner";a:1:{s:8:"origlink";s:64:"http://getclicky.com/blog/245/media-searches-and-other-new-stuff";}s:7:"summary";s:2981:"One of our most requested features has been to segment out image searches from normal searches. We have just added this, so you should start seeing a new entry in your traffic sources report:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201012-media-searches.gif><br />
<br />
<br />
This feature has been requested countless times, as far back as <a href=http://getclicky.com/forums/?id=269>June 2008</a>. We're calling it media searches instead of image searches, since we want to be as general as possible and may add support for video searches or other types of media in the future. Image searches from Google, Yahoo, and Bing are supported at the moment. We've also renamed Direct / Bookmark to just Direct, and RSS readers to Syndication.<br />
<br />
Other new features and bug fixes from today:<br />
<ul><li>Windows phone 7 detection (will show up as just Windows phone though)<br />
<li>The new Google Web Preview bot is now blocked by default <a href=http://getclicky.com/forums/?id=6892>as requested</a><br />
<li>AOL recently moved to q as the default search parameter in their search engine, so their searches were just showing up as links in Clicky. We've updated our code to support this new parameter. It still supports the old ones too (query and encquery) in case those are still used anywhere.<br />
<li>In October, <a href=http://getclicky.com/blog/237/google-ad-clicks-and-ajax-searches>we added support</a> for google.com/aclk referrers, which is what we see when someone clicks on a paid search on Google. However, there's been a bug where these were referrers were showing up in your main links report, which normally only shows non-search referrers. We've fixed this bug, which was probably quite annoying for those of you running paid searches on Google.</ul><br />
<br />
That's all for today! You should start seeing us go back to our regular feature release schedule, where we release new stuff almost every week. The last few months have been insanely hectic from the <a href=http://getclicky.com/blog/235/the-new-clicky>massive redesign</a> and tons of traveling and a big partnership integration we'll be announcing soon. We are excited to get back into the groove of writing lots of code because that's what we live for.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=A9J4khyqPZo:vEtadNTp6gQ:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=A9J4khyqPZo:vEtadNTp6gQ:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=A9J4khyqPZo:vEtadNTp6gQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=A9J4khyqPZo:vEtadNTp6gQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=A9J4khyqPZo:vEtadNTp6gQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/A9J4khyqPZo" height="1" width="1"/>";}i:8;a:9:{s:5:"title";s:34:"ClickyTouch for iPad available now";s:4:"link";s:90:"http://feedproxy.google.com/~r/getclicky/~3/Jca79azW2kk/clickytouch-for-ipad-available-now";s:8:"comments";s:64:"http://getclicky.com/blog/244/clickytouch-for-ipad-available-now";s:4:"guid";s:64:"http://getclicky.com/blog/244/clickytouch-for-ipad-available-now";s:11:"description";s:2166:"Steve has updated ClickyTouch to version 1.2, which is now a universal bundle (single application) that takes full advantage of the iPad's larger screen real estate when installed on an iPad. New features include a sidebar menu that's always visible (on the iPad), an inline browser for viewing referrers, the ability to choose a date other than today, and a few new reports.<br />
<br />
If you already have an old version of ClickyTouch installed, simply update it in the app store to get the new features. If you don't have it yet, you can <a href=http://itunes.apple.com/app/clickytouch/id400455996?mt=8>download it here</a>. <br />
<br />
Please note this is a third party application, not commissioned by Clicky, so Steve is asking a very reasonable $2.99 USD to purchase the app. However, Steve is offering a free copy to 5 people who leave a comment on this post. Simply leave a comment and include your Clicky username or site ID, and we will pick our 5 favorite comments over the next few days and send you your promo code. Note that promo codes only work in the US app store right now, which is most unfortunate, but this is a limitation on Apple's end, not ours!<br />
<br />
See <a href=http://clickytouch.com>ClickyTouch.com</a> and our <a href=http://getclicky.com/blog/240/clickytouch-for-iphone>previous post</a> for more details on the app.<br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201012-clickytouch-ipad.jpg><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=Jca79azW2kk:IveKUD7y26o:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Jca79azW2kk:IveKUD7y26o:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Jca79azW2kk:IveKUD7y26o:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Jca79azW2kk:IveKUD7y26o:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Jca79azW2kk:IveKUD7y26o:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/Jca79azW2kk" height="1" width="1"/>";s:7:"pubdate";s:31:"Wed, 01 Dec 2010 22:51:29 -0800";s:5:"bonus";s:10:"1291272689";s:10:"feedburner";a:1:{s:8:"origlink";s:64:"http://getclicky.com/blog/244/clickytouch-for-ipad-available-now";}s:7:"summary";s:2166:"Steve has updated ClickyTouch to version 1.2, which is now a universal bundle (single application) that takes full advantage of the iPad's larger screen real estate when installed on an iPad. New features include a sidebar menu that's always visible (on the iPad), an inline browser for viewing referrers, the ability to choose a date other than today, and a few new reports.<br />
<br />
If you already have an old version of ClickyTouch installed, simply update it in the app store to get the new features. If you don't have it yet, you can <a href=http://itunes.apple.com/app/clickytouch/id400455996?mt=8>download it here</a>. <br />
<br />
Please note this is a third party application, not commissioned by Clicky, so Steve is asking a very reasonable $2.99 USD to purchase the app. However, Steve is offering a free copy to 5 people who leave a comment on this post. Simply leave a comment and include your Clicky username or site ID, and we will pick our 5 favorite comments over the next few days and send you your promo code. Note that promo codes only work in the US app store right now, which is most unfortunate, but this is a limitation on Apple's end, not ours!<br />
<br />
See <a href=http://clickytouch.com>ClickyTouch.com</a> and our <a href=http://getclicky.com/blog/240/clickytouch-for-iphone>previous post</a> for more details on the app.<br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201012-clickytouch-ipad.jpg><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=Jca79azW2kk:IveKUD7y26o:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Jca79azW2kk:IveKUD7y26o:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Jca79azW2kk:IveKUD7y26o:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Jca79azW2kk:IveKUD7y26o:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Jca79azW2kk:IveKUD7y26o:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/Jca79azW2kk" height="1" width="1"/>";}i:9;a:9:{s:5:"title";s:19:"Changes to tracking";s:4:"link";s:75:"http://feedproxy.google.com/~r/getclicky/~3/mkDyrM5bNqM/changes-to-tracking";s:8:"comments";s:49:"http://getclicky.com/blog/243/changes-to-tracking";s:4:"guid";s:49:"http://getclicky.com/blog/243/changes-to-tracking";s:11:"description";s:5576:"<a href=http://getclicky.com/blog/242/downtime-today-and-tracking-changes>Monday was a doozy</a>. But good things have come out of it.<br />
<br />
When we <a href=http://getclicky.com/blog/211/heres-what-new>added pinging</a> to our tracking code back in April, a few of you raised concerns that the new way we calculate time-on-site values may be misleading, since lots of people use tabbed browsing and open pages in the background, not to view them until minutes or hours or sometimes days later. This has its consequences on our end too: a user who opens a page in the background and isn't actually viewing the page, they are still sending us pings for 10 minutes (by default). This basically means for someone not actually <i>using</i> your site, they could still send ~15 overall hits to our tracking servers during that time. Big waste of resources on our end.<br />
<br />
What happened on Monday was unrelated to pinging, but the pinging does add a lot of network activity to our servers. It accounts for just over 50% of our overall network requests. So when our load balancers crashed on Monday due to overwhelming network activity (theory is that it was related to Cyber Monday craziness), disabling pinging in our tracking code helped us calm the storm quickly. Pinging has been disabled since approximately 12pm PST on Monday, which is why your bounce rate and your time-on-site values since then have been off kilter.<br />
<br />
We really want to alleviate the load these unnecessary pings put on us, and we want to make your analytics more meaningful too. So we took some suggestions you gave us back in April and integrated them into our new tracking code, which was just deployed about 20 minutes ago.<br />
<br />
<h4>What changed</h4>Now when a visitor opens a page in a background tab or window, the page view is not logged and the pinging does not start until that page is actually being viewed by the person. If they open it in the foreground, tracking will work as it always has. This change only affects people opening background tabs. We think this will provide much more meaningful data to you, because now we'll only be logging the visit once they start using your web site.<br />
<br />
The only downside to this is that if you are comparing Clicky's visitor log to that of another service you may also using on your site, some of the arrival times for your visitors won't match up. For example, IP address 1.2.3.4 may show up in Clicky as arriving at your site at 1:30pm, whereas your other service may show them as arriving at 1:25 instead. When you see something like this, the reason will be because that visitor initially opened your page in a background tab at 1:25pm, but didn't start viewing/using the page until 1:30pm.<br />
<br />
Pretend that when this person started using your site at 1:30pm, they looked around at a few pages and left at 1:35. Would you rather we report that they were there for 10 minutes from 1:25 to 1:35 (the old way), when they were <i>really</i> only there and using your site for the last 5 minutes of that visit (the new way)? The new way more accurately reflects this visitor's actual session on your site, and hence is a better way to look at things in our opinion.<br />
<br />
This is what analytics is all about - analyzing your data to make it more meaningful. Like how <a href=http://getclicky.com/blog/214/why-clickys-new-bounce-rate-is-the-best-in-the-biz>our bounce rate is different</a> than other services, but it's <i>better</i> because it's different. This is another one of those things. We celebrate our differences as the purple cow of analytics, and hope that you do too.<br />
<br />
<b>Update:</b> No action is required on your part. The tracking code that your site links to, hosted on our servers, has been updated, so everyone gets it automatically.<br />
<br />
Also, after this being live for most of today, the difference on our end is quite noticeable. The load on our load balancers has dropped by almost 15%, and the load on the tracking servers behind them has dropped more than 30%. Yay!<br />
<br />
<b>Update 2:</b> Although it worked fine in testing, there is some strange bug with Safari that was causing this browser not to be tracked 100% of the time. Based on our numbers it looks like about 1/3 of Safari visitors weren't getting tracked. We have updated the code so that this new method does not apply to Safari anymore. Since Opera doesn't support document.hasFocus() and Chrome's implementation is wonky (it always returns true), this means that basically only Firefox 3+ and IE7+ support the new method. This is more than 2/3 of internet visitors though.<br />
<br />
<b>Update 3 (Dec. 8):</b> We have reverted to the old version of our tracking code. While most users/sites experienced no problems, a few experienced drastic differences in visitors logged.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=mkDyrM5bNqM:a5ILX7FlrHI:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=mkDyrM5bNqM:a5ILX7FlrHI:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=mkDyrM5bNqM:a5ILX7FlrHI:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=mkDyrM5bNqM:a5ILX7FlrHI:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=mkDyrM5bNqM:a5ILX7FlrHI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/mkDyrM5bNqM" height="1" width="1"/>";s:7:"pubdate";s:31:"Tue, 30 Nov 2010 23:41:29 -0800";s:5:"bonus";s:10:"1291189289";s:10:"feedburner";a:1:{s:8:"origlink";s:49:"http://getclicky.com/blog/243/changes-to-tracking";}s:7:"summary";s:5576:"<a href=http://getclicky.com/blog/242/downtime-today-and-tracking-changes>Monday was a doozy</a>. But good things have come out of it.<br />
<br />
When we <a href=http://getclicky.com/blog/211/heres-what-new>added pinging</a> to our tracking code back in April, a few of you raised concerns that the new way we calculate time-on-site values may be misleading, since lots of people use tabbed browsing and open pages in the background, not to view them until minutes or hours or sometimes days later. This has its consequences on our end too: a user who opens a page in the background and isn't actually viewing the page, they are still sending us pings for 10 minutes (by default). This basically means for someone not actually <i>using</i> your site, they could still send ~15 overall hits to our tracking servers during that time. Big waste of resources on our end.<br />
<br />
What happened on Monday was unrelated to pinging, but the pinging does add a lot of network activity to our servers. It accounts for just over 50% of our overall network requests. So when our load balancers crashed on Monday due to overwhelming network activity (theory is that it was related to Cyber Monday craziness), disabling pinging in our tracking code helped us calm the storm quickly. Pinging has been disabled since approximately 12pm PST on Monday, which is why your bounce rate and your time-on-site values since then have been off kilter.<br />
<br />
We really want to alleviate the load these unnecessary pings put on us, and we want to make your analytics more meaningful too. So we took some suggestions you gave us back in April and integrated them into our new tracking code, which was just deployed about 20 minutes ago.<br />
<br />
<h4>What changed</h4>Now when a visitor opens a page in a background tab or window, the page view is not logged and the pinging does not start until that page is actually being viewed by the person. If they open it in the foreground, tracking will work as it always has. This change only affects people opening background tabs. We think this will provide much more meaningful data to you, because now we'll only be logging the visit once they start using your web site.<br />
<br />
The only downside to this is that if you are comparing Clicky's visitor log to that of another service you may also using on your site, some of the arrival times for your visitors won't match up. For example, IP address 1.2.3.4 may show up in Clicky as arriving at your site at 1:30pm, whereas your other service may show them as arriving at 1:25 instead. When you see something like this, the reason will be because that visitor initially opened your page in a background tab at 1:25pm, but didn't start viewing/using the page until 1:30pm.<br />
<br />
Pretend that when this person started using your site at 1:30pm, they looked around at a few pages and left at 1:35. Would you rather we report that they were there for 10 minutes from 1:25 to 1:35 (the old way), when they were <i>really</i> only there and using your site for the last 5 minutes of that visit (the new way)? The new way more accurately reflects this visitor's actual session on your site, and hence is a better way to look at things in our opinion.<br />
<br />
This is what analytics is all about - analyzing your data to make it more meaningful. Like how <a href=http://getclicky.com/blog/214/why-clickys-new-bounce-rate-is-the-best-in-the-biz>our bounce rate is different</a> than other services, but it's <i>better</i> because it's different. This is another one of those things. We celebrate our differences as the purple cow of analytics, and hope that you do too.<br />
<br />
<b>Update:</b> No action is required on your part. The tracking code that your site links to, hosted on our servers, has been updated, so everyone gets it automatically.<br />
<br />
Also, after this being live for most of today, the difference on our end is quite noticeable. The load on our load balancers has dropped by almost 15%, and the load on the tracking servers behind them has dropped more than 30%. Yay!<br />
<br />
<b>Update 2:</b> Although it worked fine in testing, there is some strange bug with Safari that was causing this browser not to be tracked 100% of the time. Based on our numbers it looks like about 1/3 of Safari visitors weren't getting tracked. We have updated the code so that this new method does not apply to Safari anymore. Since Opera doesn't support document.hasFocus() and Chrome's implementation is wonky (it always returns true), this means that basically only Firefox 3+ and IE7+ support the new method. This is more than 2/3 of internet visitors though.<br />
<br />
<b>Update 3 (Dec. 8):</b> We have reverted to the old version of our tracking code. While most users/sites experienced no problems, a few experienced drastic differences in visitors logged.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=mkDyrM5bNqM:a5ILX7FlrHI:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=mkDyrM5bNqM:a5ILX7FlrHI:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=mkDyrM5bNqM:a5ILX7FlrHI:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=mkDyrM5bNqM:a5ILX7FlrHI:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=mkDyrM5bNqM:a5ILX7FlrHI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/mkDyrM5bNqM" height="1" width="1"/>";}i:10;a:9:{s:5:"title";s:35:"Downtime today and tracking changes";s:4:"link";s:91:"http://feedproxy.google.com/~r/getclicky/~3/d6zaTlslO0A/downtime-today-and-tracking-changes";s:8:"comments";s:65:"http://getclicky.com/blog/242/downtime-today-and-tracking-changes";s:4:"guid";s:65:"http://getclicky.com/blog/242/downtime-today-and-tracking-changes";s:11:"description";s:7440:"Around 12pm PST, Clicky was 100% offline for about 30 minutes. This means there is a bit of missing data from everyone's stats today.<br />
<br />
So what happened? Network activity was much higher than normal, enough to overload our load balancers and cause them to crash. Before that happened, we did notice the site seeming to get slower and slower over a few hours leading up to the crash, and load on our tracking servers (behind the load balancers) was almost twice what it normally is. We initially thought we may have been under attack because the network traffic was so much higher than normal, but this does not appear to be the case.<br />
<br />
Someone on Twitter suggested it may be related to increased activity due to so called Cyber Monday, a shopping holiday <a href=http://www.msnbc.msn.com/id/40423028/ns/business-us_business/>invented</a> by the retail industry in 2005 to get you to spend more money. This seems plausible, however I would expect most of the extra browsing on the internet in general today to be on major site's like Amazon - sites that are way too big for us to track so we probably wouldn't be affected by it, in other words.<br />
<br />
A similar thing <a href=http://getclicky.com/blog/213/what-happened>happened</a> back in April when we first added pinging support to our tracking code. Pinging is what lets us determine much more accurately than most services your bounce rate and time-on-site values, because our tracking code continually talks to our servers while a visitor sits on one page. Back then, we rolled out this feature over the weekend, but then when Monday rolled around, the extra spike in traffic from these pings was so high that the same thing happened - load balancers went boom. We were pinging too agressively, it seemed. Some quick detective work showed that the pings were accounting for 80% of the traffic we were now logging - a 400% increase, in other words, basically overnight. This was quite a bit higher than we had anticipated, so we made some changes to the code to basically cut in half how many pings our code sends - they now only account for about about 50% of our total incoming hits.<br />
<br />
The point is, making this changed saved our skin then, and today it has done the same thing. After we crashed, we quickly updated the tracking code to disable pinging and threw it on the CDN. Within minutes, the load balancers were happily chugging along again. This does mean for the time being, your bounce rate and time-on-site values will be back to non-awesome mode, but if it's a choice between that and Clicky offline, we choose the former.<br />
<br />
This change is only temporary though. We're evaluating how to make it more efficient. One complaint people had when we first released the new pinging is that lots of people open tabs in the background and leave them there for a long time before actually viewing the page. So not only does this make your time-on-site values perhaps higher than they should be, it also leads to increased load on our end to track all these excess pings.<br />
<br />
So right now, for our own stats, we're testing a new version of the tracking code that only starts tracking a page view and hence starts pinging when one of the following events occurs:<br />
<ul><li>Mouse movement<br />
<li>Key press<br />
<li>Page scroll<br />
<li>Page coming into focus (when a tab is loaded in the background then displayed later, this will fire)</ul><br />
<br />
We think monitoring for these events before logging a page view and starting the pinging will lead to much more accurate traffic data, and quite a bit less load on our end. There may be some odd cases where none of the aforementioned events occur on a valid page view, but we'd guess they account for less than 1% of your traffic. Of course, if anyone has feedback or ideas on other events we should be listening for, we're all ears.<br />
<br />
Ideally we'd always log a page view immediately when it is loaded in focus but Javascript does not provide a way to check the current focus status - only to detect events when the focus changes. This is an extremely frustrating limitation but we must live with it.<br />
<br />
<h3 id=update>Update</h3>It turns out there is a new method with HTML5, document.hasFocus(), which is a way to determine on demand whether the current document is in focus. It is not yet supported in Opera, and Chrome always returns true even when it shouldn't (<a href=http://code.google.com/p/chromium/issues/detail?id=64846>bug filed</a>), but Firefox 3+, IE7+, and Safari 5 (at least, haven't tested in Safari 4) all support it properly. The test tracking code we are running on our blog and on getclicky.com has been updated to use this new method instead of relying on other events (mouse movement etc).<br />
<br />
Relying on events led to about a 5% drop in visitors being tracked, so we knew this wouldn't work. Somehow, we discovered the hasFocus() method, which has VERY little discussion online. Most people must not know about it yet. But anyways, this is what our new test code does:<br />
<br />
<ul><li>If the browser supports document.hasFocus()...<br />
<ul><li>If the current document has focus at the time the tracking code is executed, a page view is logged immediately and pinging starts. (Since Chrome has a bug where this method always returns true even when it shouldn't, Chrome users will always be logged immediately. All other modern browsers, except Opera, will work properly).<br />
<li>If the current document does NOT have focus, we setup an event listener to wait for the onfocus event to fire, at which point the page view is logged and pinging starts. This will apply to anyone who opens a page on your site in a background tab or window - we won't log their visit until they actually start viewing your page. This will help alleviate the extra load of pings on our end, and will result in more accurate usage data of your web site since we won't log a visitor until they are actually viewing your web site.<br />
</ul><br />
<li>If the browser does NOT support document.hasFocus()...  (currently only Opera, and old, outdated browsers)<br />
<ul><li>Page view is logged immediately<br />
<li>Pinging starts immediately<br />
<li>(This is the way it used to work by default anyways)</ul><br />
</ul><br />
We think this way of doing things will work great, and if all goes well from our testing, we will deploy it to our CDN and it will become the new default tracking code.<br />
<br />
By the way, pinging is still disabled in our public tracking code. Once this new code is tested and deployed, pinging still start again, and your bounce / time-on-site values will return to their normal state.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=d6zaTlslO0A:ASfZrMOg--E:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=d6zaTlslO0A:ASfZrMOg--E:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=d6zaTlslO0A:ASfZrMOg--E:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=d6zaTlslO0A:ASfZrMOg--E:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=d6zaTlslO0A:ASfZrMOg--E:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/d6zaTlslO0A" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 29 Nov 2010 18:10:43 -0800";s:5:"bonus";s:10:"1291083043";s:10:"feedburner";a:1:{s:8:"origlink";s:65:"http://getclicky.com/blog/242/downtime-today-and-tracking-changes";}s:7:"summary";s:7440:"Around 12pm PST, Clicky was 100% offline for about 30 minutes. This means there is a bit of missing data from everyone's stats today.<br />
<br />
So what happened? Network activity was much higher than normal, enough to overload our load balancers and cause them to crash. Before that happened, we did notice the site seeming to get slower and slower over a few hours leading up to the crash, and load on our tracking servers (behind the load balancers) was almost twice what it normally is. We initially thought we may have been under attack because the network traffic was so much higher than normal, but this does not appear to be the case.<br />
<br />
Someone on Twitter suggested it may be related to increased activity due to so called Cyber Monday, a shopping holiday <a href=http://www.msnbc.msn.com/id/40423028/ns/business-us_business/>invented</a> by the retail industry in 2005 to get you to spend more money. This seems plausible, however I would expect most of the extra browsing on the internet in general today to be on major site's like Amazon - sites that are way too big for us to track so we probably wouldn't be affected by it, in other words.<br />
<br />
A similar thing <a href=http://getclicky.com/blog/213/what-happened>happened</a> back in April when we first added pinging support to our tracking code. Pinging is what lets us determine much more accurately than most services your bounce rate and time-on-site values, because our tracking code continually talks to our servers while a visitor sits on one page. Back then, we rolled out this feature over the weekend, but then when Monday rolled around, the extra spike in traffic from these pings was so high that the same thing happened - load balancers went boom. We were pinging too agressively, it seemed. Some quick detective work showed that the pings were accounting for 80% of the traffic we were now logging - a 400% increase, in other words, basically overnight. This was quite a bit higher than we had anticipated, so we made some changes to the code to basically cut in half how many pings our code sends - they now only account for about about 50% of our total incoming hits.<br />
<br />
The point is, making this changed saved our skin then, and today it has done the same thing. After we crashed, we quickly updated the tracking code to disable pinging and threw it on the CDN. Within minutes, the load balancers were happily chugging along again. This does mean for the time being, your bounce rate and time-on-site values will be back to non-awesome mode, but if it's a choice between that and Clicky offline, we choose the former.<br />
<br />
This change is only temporary though. We're evaluating how to make it more efficient. One complaint people had when we first released the new pinging is that lots of people open tabs in the background and leave them there for a long time before actually viewing the page. So not only does this make your time-on-site values perhaps higher than they should be, it also leads to increased load on our end to track all these excess pings.<br />
<br />
So right now, for our own stats, we're testing a new version of the tracking code that only starts tracking a page view and hence starts pinging when one of the following events occurs:<br />
<ul><li>Mouse movement<br />
<li>Key press<br />
<li>Page scroll<br />
<li>Page coming into focus (when a tab is loaded in the background then displayed later, this will fire)</ul><br />
<br />
We think monitoring for these events before logging a page view and starting the pinging will lead to much more accurate traffic data, and quite a bit less load on our end. There may be some odd cases where none of the aforementioned events occur on a valid page view, but we'd guess they account for less than 1% of your traffic. Of course, if anyone has feedback or ideas on other events we should be listening for, we're all ears.<br />
<br />
Ideally we'd always log a page view immediately when it is loaded in focus but Javascript does not provide a way to check the current focus status - only to detect events when the focus changes. This is an extremely frustrating limitation but we must live with it.<br />
<br />
<h3 id=update>Update</h3>It turns out there is a new method with HTML5, document.hasFocus(), which is a way to determine on demand whether the current document is in focus. It is not yet supported in Opera, and Chrome always returns true even when it shouldn't (<a href=http://code.google.com/p/chromium/issues/detail?id=64846>bug filed</a>), but Firefox 3+, IE7+, and Safari 5 (at least, haven't tested in Safari 4) all support it properly. The test tracking code we are running on our blog and on getclicky.com has been updated to use this new method instead of relying on other events (mouse movement etc).<br />
<br />
Relying on events led to about a 5% drop in visitors being tracked, so we knew this wouldn't work. Somehow, we discovered the hasFocus() method, which has VERY little discussion online. Most people must not know about it yet. But anyways, this is what our new test code does:<br />
<br />
<ul><li>If the browser supports document.hasFocus()...<br />
<ul><li>If the current document has focus at the time the tracking code is executed, a page view is logged immediately and pinging starts. (Since Chrome has a bug where this method always returns true even when it shouldn't, Chrome users will always be logged immediately. All other modern browsers, except Opera, will work properly).<br />
<li>If the current document does NOT have focus, we setup an event listener to wait for the onfocus event to fire, at which point the page view is logged and pinging starts. This will apply to anyone who opens a page on your site in a background tab or window - we won't log their visit until they actually start viewing your page. This will help alleviate the extra load of pings on our end, and will result in more accurate usage data of your web site since we won't log a visitor until they are actually viewing your web site.<br />
</ul><br />
<li>If the browser does NOT support document.hasFocus()...  (currently only Opera, and old, outdated browsers)<br />
<ul><li>Page view is logged immediately<br />
<li>Pinging starts immediately<br />
<li>(This is the way it used to work by default anyways)</ul><br />
</ul><br />
We think this way of doing things will work great, and if all goes well from our testing, we will deploy it to our CDN and it will become the new default tracking code.<br />
<br />
By the way, pinging is still disabled in our public tracking code. Once this new code is tested and deployed, pinging still start again, and your bounce / time-on-site values will return to their normal state.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=d6zaTlslO0A:ASfZrMOg--E:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=d6zaTlslO0A:ASfZrMOg--E:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=d6zaTlslO0A:ASfZrMOg--E:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=d6zaTlslO0A:ASfZrMOg--E:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=d6zaTlslO0A:ASfZrMOg--E:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/d6zaTlslO0A" height="1" width="1"/>";}i:11;a:9:{s:5:"title";s:22:"ClickyTouch for iPhone";s:4:"link";s:78:"http://feedproxy.google.com/~r/getclicky/~3/KL9yih8tJAg/clickytouch-for-iphone";s:8:"comments";s:52:"http://getclicky.com/blog/240/clickytouch-for-iphone";s:4:"guid";s:52:"http://getclicky.com/blog/240/clickytouch-for-iphone";s:11:"description";s:2611:"<a href=http://www.reynoldsftw.com/>Steve Reynolds</a> has spent the last few weeks developing a native iPhone application called <a href=http://clickytouch.com/>ClickyTouch</a>. It looks pretty dang slick and you can <a class=red href=http://itunes.apple.com/app/clickytouch/id400455996?mt=8>download it right here</a>. Steve's description of the app:<br />
<br />
<i>Keep up to date throughout every view of your stats, with self refreshing data such as active users on your site, your bounce rate, average session time and overall comparison percentage versus this time yesterday. In as many cases as possible, data refreshes whilst you look at it! No refresh buttons here!<br />
<br />
View the following data in a simple, beautiful summary screen:<br />
<br />
Live Active Visitors, Bounce Rates, Time Average, Overall Visitors, Actions, Searches, Bookmarks, Links, Social Media, Goals and Campaigns</i><br />
<br />
<br />
We use Android phones at Clicky so we haven't gotten a chance to play with it ourselves, but the beta testers we've seen talking about it on Twitter have all been quite enthusiastic. Let us know what you think.<br />
<br />
<b>Update:</b> This is a third party app, not commissioned by Clicky. Hence, Steve is asking a reasonable fee of $2.99 USD for the app. However, all users are able to use it, whether they have a premium account with Clicky or not. Also, the app does ask for your username and password to automatically download and keep up-to-date the sites in your account. One user mentioned they don't want to share that information with a third party app, however we assure you that Steve is completely legit and is not the type of person who would do something evil with that information. He has been a very long time user of Clicky and just wants to spread the love!<br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201011-clickytouch.png><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=KL9yih8tJAg:7_YbKsCa_l0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=KL9yih8tJAg:7_YbKsCa_l0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=KL9yih8tJAg:7_YbKsCa_l0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=KL9yih8tJAg:7_YbKsCa_l0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=KL9yih8tJAg:7_YbKsCa_l0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/KL9yih8tJAg" height="1" width="1"/>";s:7:"pubdate";s:31:"Fri, 05 Nov 2010 09:13:15 -0800";s:5:"bonus";s:10:"1288973595";s:10:"feedburner";a:1:{s:8:"origlink";s:52:"http://getclicky.com/blog/240/clickytouch-for-iphone";}s:7:"summary";s:2611:"<a href=http://www.reynoldsftw.com/>Steve Reynolds</a> has spent the last few weeks developing a native iPhone application called <a href=http://clickytouch.com/>ClickyTouch</a>. It looks pretty dang slick and you can <a class=red href=http://itunes.apple.com/app/clickytouch/id400455996?mt=8>download it right here</a>. Steve's description of the app:<br />
<br />
<i>Keep up to date throughout every view of your stats, with self refreshing data such as active users on your site, your bounce rate, average session time and overall comparison percentage versus this time yesterday. In as many cases as possible, data refreshes whilst you look at it! No refresh buttons here!<br />
<br />
View the following data in a simple, beautiful summary screen:<br />
<br />
Live Active Visitors, Bounce Rates, Time Average, Overall Visitors, Actions, Searches, Bookmarks, Links, Social Media, Goals and Campaigns</i><br />
<br />
<br />
We use Android phones at Clicky so we haven't gotten a chance to play with it ourselves, but the beta testers we've seen talking about it on Twitter have all been quite enthusiastic. Let us know what you think.<br />
<br />
<b>Update:</b> This is a third party app, not commissioned by Clicky. Hence, Steve is asking a reasonable fee of $2.99 USD for the app. However, all users are able to use it, whether they have a premium account with Clicky or not. Also, the app does ask for your username and password to automatically download and keep up-to-date the sites in your account. One user mentioned they don't want to share that information with a third party app, however we assure you that Steve is completely legit and is not the type of person who would do something evil with that information. He has been a very long time user of Clicky and just wants to spread the love!<br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201011-clickytouch.png><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=KL9yih8tJAg:7_YbKsCa_l0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=KL9yih8tJAg:7_YbKsCa_l0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=KL9yih8tJAg:7_YbKsCa_l0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=KL9yih8tJAg:7_YbKsCa_l0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=KL9yih8tJAg:7_YbKsCa_l0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/KL9yih8tJAg" height="1" width="1"/>";}i:12;a:9:{s:5:"title";s:25:"Updates to the new Clicky";s:4:"link";s:81:"http://feedproxy.google.com/~r/getclicky/~3/JdRXcezhf98/updates-to-the-new-clicky";s:8:"comments";s:55:"http://getclicky.com/blog/239/updates-to-the-new-clicky";s:4:"guid";s:55:"http://getclicky.com/blog/239/updates-to-the-new-clicky";s:11:"description";s:2429:"<ul><li>Small site mode is back. If your browser window is less than ~1100px wide, then the sidebar flips back to the top, kind of like the old Clicky, but a bit more space efficient because there are more tabs.<br />
<li>Those of you with more than about 20 sites, the site selection menu now tiles to the right so you can see more than the first 20. This has been a huge request that we didn't consider originally because we don't track that many sites ourselves.<br />
<li>The clock is back! In the top right corner. It's part of the stats header element though, which is not shown in small site mode to save space.<br />
<li>Small site Spy users - visitors online value is now shown again. That was a silly oversight.<br />
<li>Wordpress plugin - when viewing stats from your WP admin area, the layout was messed up because of the sidebar which we were hiding. Now that small site mode is back, however, it should work correctly again.<br />
<li>There were a few minor bugs with Ajax forms that have been fixed, and lots of other minor bug fixes.</ul><br />
<br />
Before bringing small site mode back (we disabled it right after official new Clicky release because of serious bugginess), we <a href=http://getclicky.com/blog/238/drop-what-youre-doing-and-help-us-test>asked you</a> to help us test the new code on beta.getclicky.com. No one reported any bugs with it so it should be good now!<br />
<br />
Note that you may need to force refresh your browser window to get these changes.<br />
<br />
We are planning one more fix later today - making the navigation tabs auto-update to the proper state when you click back or click a link that brings you to another page that should have another tab highlighted instead.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=JdRXcezhf98:CbuVTgdyGW0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=JdRXcezhf98:CbuVTgdyGW0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=JdRXcezhf98:CbuVTgdyGW0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=JdRXcezhf98:CbuVTgdyGW0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=JdRXcezhf98:CbuVTgdyGW0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/JdRXcezhf98" height="1" width="1"/>";s:7:"pubdate";s:31:"Thu, 28 Oct 2010 13:38:38 -0800";s:5:"bonus";s:10:"1288298318";s:10:"feedburner";a:1:{s:8:"origlink";s:55:"http://getclicky.com/blog/239/updates-to-the-new-clicky";}s:7:"summary";s:2429:"<ul><li>Small site mode is back. If your browser window is less than ~1100px wide, then the sidebar flips back to the top, kind of like the old Clicky, but a bit more space efficient because there are more tabs.<br />
<li>Those of you with more than about 20 sites, the site selection menu now tiles to the right so you can see more than the first 20. This has been a huge request that we didn't consider originally because we don't track that many sites ourselves.<br />
<li>The clock is back! In the top right corner. It's part of the stats header element though, which is not shown in small site mode to save space.<br />
<li>Small site Spy users - visitors online value is now shown again. That was a silly oversight.<br />
<li>Wordpress plugin - when viewing stats from your WP admin area, the layout was messed up because of the sidebar which we were hiding. Now that small site mode is back, however, it should work correctly again.<br />
<li>There were a few minor bugs with Ajax forms that have been fixed, and lots of other minor bug fixes.</ul><br />
<br />
Before bringing small site mode back (we disabled it right after official new Clicky release because of serious bugginess), we <a href=http://getclicky.com/blog/238/drop-what-youre-doing-and-help-us-test>asked you</a> to help us test the new code on beta.getclicky.com. No one reported any bugs with it so it should be good now!<br />
<br />
Note that you may need to force refresh your browser window to get these changes.<br />
<br />
We are planning one more fix later today - making the navigation tabs auto-update to the proper state when you click back or click a link that brings you to another page that should have another tab highlighted instead.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=JdRXcezhf98:CbuVTgdyGW0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=JdRXcezhf98:CbuVTgdyGW0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=JdRXcezhf98:CbuVTgdyGW0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=JdRXcezhf98:CbuVTgdyGW0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=JdRXcezhf98:CbuVTgdyGW0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/JdRXcezhf98" height="1" width="1"/>";}i:13;a:9:{s:5:"title";s:40:"Drop what you're doing and help us test!";s:4:"link";s:94:"http://feedproxy.google.com/~r/getclicky/~3/Tg-uMuTHU0A/drop-what-youre-doing-and-help-us-test";s:8:"comments";s:68:"http://getclicky.com/blog/238/drop-what-youre-doing-and-help-us-test";s:4:"guid";s:68:"http://getclicky.com/blog/238/drop-what-youre-doing-and-help-us-test";s:11:"description";s:2454:"When we originally released <a href=http://getclicky.com/blog/235/the-new-clicky>the new Clicky</a> a few weeks ago, we had programmed in support for detecting small screens (1024 or less) and moving the sidebar to the top instead, so that you don't have to scroll sideways. However, there was apparently a serious bug with it and some of you were getting this forced small screen mode even if your browser window was large and in charge.<br />
<br />
Well, we think we finally fixed it. However, since we never saw the bug in action ourselves, we need you to help us test this change before making it live. To help test, please visit <a href=http://beta.getclicky.com>beta.getclicky.com</a> and tell us if you see it (by leaving a comment here). Don't just test once though - after you login and view a few reports, completely close your browser and re-open it and see if it continues to happen. Maybe try making your browser window small so small site mode goes into action, then close that tab, make your screen full size again, then re-open beta.getclicky.com. We think that may have been part of the problem, the screen size wasn't being checked properly if next time you viewed the site it was small instead of large or vice versa.<br />
<br />
Thanks for your help and in particular if you were one of the ones experiencing this problem with the initial release, your feedback is appreciated!<br />
<br />
<b>UPDATE:</b> To clarify, we know that it always works if your browser window is actually small. What we're looking for here is to make sure that the code does not mistakenly put you into small site mode when your browser is at least 1100px wide.<br />
<br />
<b class=red>UPDATE:</b> Test is over! All seems well. Thanks for your help!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=Tg-uMuTHU0A:02lQL5Yh420:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Tg-uMuTHU0A:02lQL5Yh420:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Tg-uMuTHU0A:02lQL5Yh420:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Tg-uMuTHU0A:02lQL5Yh420:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Tg-uMuTHU0A:02lQL5Yh420:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/Tg-uMuTHU0A" height="1" width="1"/>";s:7:"pubdate";s:31:"Wed, 27 Oct 2010 16:02:45 -0800";s:5:"bonus";s:10:"1288220565";s:10:"feedburner";a:1:{s:8:"origlink";s:68:"http://getclicky.com/blog/238/drop-what-youre-doing-and-help-us-test";}s:7:"summary";s:2454:"When we originally released <a href=http://getclicky.com/blog/235/the-new-clicky>the new Clicky</a> a few weeks ago, we had programmed in support for detecting small screens (1024 or less) and moving the sidebar to the top instead, so that you don't have to scroll sideways. However, there was apparently a serious bug with it and some of you were getting this forced small screen mode even if your browser window was large and in charge.<br />
<br />
Well, we think we finally fixed it. However, since we never saw the bug in action ourselves, we need you to help us test this change before making it live. To help test, please visit <a href=http://beta.getclicky.com>beta.getclicky.com</a> and tell us if you see it (by leaving a comment here). Don't just test once though - after you login and view a few reports, completely close your browser and re-open it and see if it continues to happen. Maybe try making your browser window small so small site mode goes into action, then close that tab, make your screen full size again, then re-open beta.getclicky.com. We think that may have been part of the problem, the screen size wasn't being checked properly if next time you viewed the site it was small instead of large or vice versa.<br />
<br />
Thanks for your help and in particular if you were one of the ones experiencing this problem with the initial release, your feedback is appreciated!<br />
<br />
<b>UPDATE:</b> To clarify, we know that it always works if your browser window is actually small. What we're looking for here is to make sure that the code does not mistakenly put you into small site mode when your browser is at least 1100px wide.<br />
<br />
<b class=red>UPDATE:</b> Test is over! All seems well. Thanks for your help!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=Tg-uMuTHU0A:02lQL5Yh420:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Tg-uMuTHU0A:02lQL5Yh420:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Tg-uMuTHU0A:02lQL5Yh420:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Tg-uMuTHU0A:02lQL5Yh420:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Tg-uMuTHU0A:02lQL5Yh420:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/Tg-uMuTHU0A" height="1" width="1"/>";}i:14;a:9:{s:5:"title";s:34:"Google ad clicks and ajax searches";s:4:"link";s:90:"http://feedproxy.google.com/~r/getclicky/~3/J53UTI9GDlM/google-ad-clicks-and-ajax-searches";s:8:"comments";s:64:"http://getclicky.com/blog/237/google-ad-clicks-and-ajax-searches";s:4:"guid";s:64:"http://getclicky.com/blog/237/google-ad-clicks-and-ajax-searches";s:11:"description";s:2579:"Out of nowhere, everyone has  been clambering for us to add support for <i>google.com/aclk</i> referrers. Something must have changed on Google's end recently because these didn't used to be that common but they are now. Many people have told us that the original search is included in the referrer string and sent us examples. So we finally just added support for this. However, based on our limited testing, when clicking on ads on google.com we don't see the q variable (that contains the search) in the string. So, we're guessing it's only there sometimes. What would cause it to be there or not is beyond us. Anyways, if the q variable is there, the search will now be displayed, and either way, the visitor will always be classified as advertising now.<br />
<br />
Also, a few months ago, we wrote a post about <a href=http://getclicky.com/blog/225/an-update-on-google-and-ajax>Google and Ajax searches</a>. We said when we saw these referrers we were just going to ignore them, because otherwise they showed up as normal links from google.com and that was causing confusion - but you all hated that idea, so we disabled it. We've just updated it now so that it will no longer show up in your links report, and the visitor will be classified as a search in traffic sources. And the referrer will be manually changed to google.com/search with no query in your visitors report. We wanted to add some link to click on to explain why the search was blank but decided against that.<br />
<br />
And finally, we're frantically working to fix some outstanding bugs with the new Clicky that we were unable to fix last week because of travel plans, including the small site bug. We'll keep you updated.<br />
<br />
<b>Update:</b> Some of you may see some [unknown] searches from Google. This was a bug when we first uploaded the new code but was fixed within about 20 minutes.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=J53UTI9GDlM:lPc2U_mAa4I:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=J53UTI9GDlM:lPc2U_mAa4I:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=J53UTI9GDlM:lPc2U_mAa4I:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=J53UTI9GDlM:lPc2U_mAa4I:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=J53UTI9GDlM:lPc2U_mAa4I:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/J53UTI9GDlM" height="1" width="1"/>";s:7:"pubdate";s:31:"Wed, 27 Oct 2010 12:39:22 -0800";s:5:"bonus";s:10:"1288208362";s:10:"feedburner";a:1:{s:8:"origlink";s:64:"http://getclicky.com/blog/237/google-ad-clicks-and-ajax-searches";}s:7:"summary";s:2579:"Out of nowhere, everyone has  been clambering for us to add support for <i>google.com/aclk</i> referrers. Something must have changed on Google's end recently because these didn't used to be that common but they are now. Many people have told us that the original search is included in the referrer string and sent us examples. So we finally just added support for this. However, based on our limited testing, when clicking on ads on google.com we don't see the q variable (that contains the search) in the string. So, we're guessing it's only there sometimes. What would cause it to be there or not is beyond us. Anyways, if the q variable is there, the search will now be displayed, and either way, the visitor will always be classified as advertising now.<br />
<br />
Also, a few months ago, we wrote a post about <a href=http://getclicky.com/blog/225/an-update-on-google-and-ajax>Google and Ajax searches</a>. We said when we saw these referrers we were just going to ignore them, because otherwise they showed up as normal links from google.com and that was causing confusion - but you all hated that idea, so we disabled it. We've just updated it now so that it will no longer show up in your links report, and the visitor will be classified as a search in traffic sources. And the referrer will be manually changed to google.com/search with no query in your visitors report. We wanted to add some link to click on to explain why the search was blank but decided against that.<br />
<br />
And finally, we're frantically working to fix some outstanding bugs with the new Clicky that we were unable to fix last week because of travel plans, including the small site bug. We'll keep you updated.<br />
<br />
<b>Update:</b> Some of you may see some [unknown] searches from Google. This was a bug when we first uploaded the new code but was fixed within about 20 minutes.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=J53UTI9GDlM:lPc2U_mAa4I:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=J53UTI9GDlM:lPc2U_mAa4I:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=J53UTI9GDlM:lPc2U_mAa4I:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=J53UTI9GDlM:lPc2U_mAa4I:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=J53UTI9GDlM:lPc2U_mAa4I:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/J53UTI9GDlM" height="1" width="1"/>";}i:15;a:9:{s:5:"title";s:35:"Reasoning and motivation for change";s:4:"link";s:91:"http://feedproxy.google.com/~r/getclicky/~3/6o7H8D6DcNc/reasoning-and-motivation-for-change";s:8:"comments";s:65:"http://getclicky.com/blog/236/reasoning-and-motivation-for-change";s:4:"guid";s:65:"http://getclicky.com/blog/236/reasoning-and-motivation-for-change";s:11:"description";s:4575:"Hi. Regarding our new interface. We've been blogging and <a href=http://twitter.com/getclicky>tweeting</a> about it and had it publicly available to <i>all users</i> for over a month, because we value your feedback and we care about you. If you care about Clicky, we feel it is your responsibility to monitor these communication channels that we use on a very regular basis. We are very open and transparent about everything we do. Some would say <a href=http://getclicky.com/blog/234/advice-on-moving-to-the-cloud>too transparent</a>, although I would disagree.<br />
<br />
During the beta period, we had many thousands of people use it and the vast majority of the feedback was very positive. Just go look at the old blog posts yourself to see the comments people were leaving. The only consistent complaint we got was that it's not centered, but otherwise most people loved it. Based on that much feedback from that many people, we knew we were going in the right direction.<br />
<br />
I have a theory regarding why the beta testers were so much more positive compared to the comments that have been left <a href=http://getclicky.com/blog/235/the-new-clicky>here</a>. If you're willing to test beta software, you are open to change already. You know things will be new and different and hence you will more accepting of them, especially because the old Clicky was still available. But even with thousands of testers, I would guess that only 5-10% of our users at the very most saw the beta. The rest of you had no idea it was coming, so it was a shock. But again, we tried to be as open about this as possible and got a ton of feedback before making it live. (So please, if you're not already, <a href=http://feeds.feedburner.com/getclicky>subscribe to our blog</a> or <a href=http://twitter.com/getclicky>follow us on Twitter</a>).<br />
<br />
People are resistant to change. If it ain't broke, don't fix it. Well, Clicky wasn't broken per se, but it was starting to feel dated. Sexy competitors like Chartbeat and Woopra have popped up and while we feel that our product is much more feature complete than either of them, people rave about their interfaces all the time. We get plenty of compliments on our (old) interface too, because of its simplicity and ease of use, but the difference is that Clicky felt like a web <i>site</i>, while the others feel like web <i>apps</i>. (And in the case of Woopra, it is literally a desktop app, although they offer a web version now as well). <br />
<br />
We wanted to feel like an app too. It's the way the web is moving and we were feeling left out. Hence, the navigational changes - fixed sidebar navigation, everything loading via Ajax, page loading animations, auto-updating reports, etc.<br />
<br />
This isn't change just for the sake of change. The new Clicky has been floating around in my head for close to a year, but I wasn't sure exactly what I wanted it to do. Over the summer my vision became clear and in mid-August I decided it was time to act. Two months later, here we are. This is the longest I've ever spent on developing a new feature for Clicky. I'm very proud of it, but that makes the negative comments hurt that much more.<br />
<br />
Please give the new Clicky a chance to grow on you. I promise that it will for most of you, once the initial shock wears off. I'm a huge believer in UI and UX, and believe this is one of the major reasons for our success. I'd like to think I know what I'm doing, so please place your trust in me to deliver you the best analytics experience possible.<br />
<br />
One last thing. Please keep your criticisms constructive. If you don't like, don't just say it sucks. That doesn't help. Tell us specifically <i>why</i> you don't like it. We will adjust things based on your feedback over the coming weeks and months. We are listening to what you have to say.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=6o7H8D6DcNc:kYlPXYUbrOY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=6o7H8D6DcNc:kYlPXYUbrOY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=6o7H8D6DcNc:kYlPXYUbrOY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=6o7H8D6DcNc:kYlPXYUbrOY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=6o7H8D6DcNc:kYlPXYUbrOY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/6o7H8D6DcNc" height="1" width="1"/>";s:7:"pubdate";s:31:"Sun, 17 Oct 2010 10:05:15 -0800";s:5:"bonus";s:10:"1287335115";s:10:"feedburner";a:1:{s:8:"origlink";s:65:"http://getclicky.com/blog/236/reasoning-and-motivation-for-change";}s:7:"summary";s:4575:"Hi. Regarding our new interface. We've been blogging and <a href=http://twitter.com/getclicky>tweeting</a> about it and had it publicly available to <i>all users</i> for over a month, because we value your feedback and we care about you. If you care about Clicky, we feel it is your responsibility to monitor these communication channels that we use on a very regular basis. We are very open and transparent about everything we do. Some would say <a href=http://getclicky.com/blog/234/advice-on-moving-to-the-cloud>too transparent</a>, although I would disagree.<br />
<br />
During the beta period, we had many thousands of people use it and the vast majority of the feedback was very positive. Just go look at the old blog posts yourself to see the comments people were leaving. The only consistent complaint we got was that it's not centered, but otherwise most people loved it. Based on that much feedback from that many people, we knew we were going in the right direction.<br />
<br />
I have a theory regarding why the beta testers were so much more positive compared to the comments that have been left <a href=http://getclicky.com/blog/235/the-new-clicky>here</a>. If you're willing to test beta software, you are open to change already. You know things will be new and different and hence you will more accepting of them, especially because the old Clicky was still available. But even with thousands of testers, I would guess that only 5-10% of our users at the very most saw the beta. The rest of you had no idea it was coming, so it was a shock. But again, we tried to be as open about this as possible and got a ton of feedback before making it live. (So please, if you're not already, <a href=http://feeds.feedburner.com/getclicky>subscribe to our blog</a> or <a href=http://twitter.com/getclicky>follow us on Twitter</a>).<br />
<br />
People are resistant to change. If it ain't broke, don't fix it. Well, Clicky wasn't broken per se, but it was starting to feel dated. Sexy competitors like Chartbeat and Woopra have popped up and while we feel that our product is much more feature complete than either of them, people rave about their interfaces all the time. We get plenty of compliments on our (old) interface too, because of its simplicity and ease of use, but the difference is that Clicky felt like a web <i>site</i>, while the others feel like web <i>apps</i>. (And in the case of Woopra, it is literally a desktop app, although they offer a web version now as well). <br />
<br />
We wanted to feel like an app too. It's the way the web is moving and we were feeling left out. Hence, the navigational changes - fixed sidebar navigation, everything loading via Ajax, page loading animations, auto-updating reports, etc.<br />
<br />
This isn't change just for the sake of change. The new Clicky has been floating around in my head for close to a year, but I wasn't sure exactly what I wanted it to do. Over the summer my vision became clear and in mid-August I decided it was time to act. Two months later, here we are. This is the longest I've ever spent on developing a new feature for Clicky. I'm very proud of it, but that makes the negative comments hurt that much more.<br />
<br />
Please give the new Clicky a chance to grow on you. I promise that it will for most of you, once the initial shock wears off. I'm a huge believer in UI and UX, and believe this is one of the major reasons for our success. I'd like to think I know what I'm doing, so please place your trust in me to deliver you the best analytics experience possible.<br />
<br />
One last thing. Please keep your criticisms constructive. If you don't like, don't just say it sucks. That doesn't help. Tell us specifically <i>why</i> you don't like it. We will adjust things based on your feedback over the coming weeks and months. We are listening to what you have to say.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=6o7H8D6DcNc:kYlPXYUbrOY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=6o7H8D6DcNc:kYlPXYUbrOY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=6o7H8D6DcNc:kYlPXYUbrOY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=6o7H8D6DcNc:kYlPXYUbrOY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=6o7H8D6DcNc:kYlPXYUbrOY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/6o7H8D6DcNc" height="1" width="1"/>";}i:16;a:9:{s:5:"title";s:14:"The New Clicky";s:4:"link";s:70:"http://feedproxy.google.com/~r/getclicky/~3/gdq2kjwmtwg/the-new-clicky";s:8:"comments";s:44:"http://getclicky.com/blog/235/the-new-clicky";s:4:"guid";s:44:"http://getclicky.com/blog/235/the-new-clicky";s:11:"description";s:5925:"After nearly 2 months of development, the new Clicky is now live. Here's what it looks like:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201009-beta.gif><br />
<br />
<br />
If you haven't been following our blog, we've had a public beta of our new interface available since September 16. (Hint: this is a good reason to read our blog. We announce important things on it!). The vast majority of the feedback has been very positive, which is remarkable for such a big change.<br />
<br />
This is still the same Clicky you know and love, the main difference is the navigation. The goal here was to make it faster to get to other pages, and to load them faster too. We also wanted the entire site to feel like a true app instead of just a web site.<br />
<br />
So, we created a fixed sidebar that stays with you as you scroll up and down the page (as long as your browser window is at least ~700px tall), and literally <i>everything</i> loads via Ajax, including form submissions (unless you're using Internet Explorer, which has WAY too many problems to support this functionality). However, this new interface is a bit wider than the standard 1024 that most sites aim for. So if we detect that your browser window is less than 1100px wide, the sidebar moves back to the top of the window so it works fairly similar to the old design with the tabs on top. The tabs aren't quite as stylized as they used to be, because we have more of them now so we need to conserve space:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201010-beta-small.gif><br />
<br />
<br />
<b>Update:</b> Some users are experiencing bugs with small site mode being enabled even when their browser window is plenty big. We've temporarily disabled this until we get it figured out.<br />
<br />
To learn more about everything that's new, please read the previous posts we've made about the beta:<br />
<br />
<a href=http://getclicky.com/blog/231/help-test-the-new-clicky-beta>Sep 16: Help test the new Clicky beta</a><br />
<a href=http://getclicky.com/blog/232/beta-updates>Sep 21: Beta updates</a><br />
<a href=http://getclicky.com/blog/233/more-beta-updates-and-were-off-to-san-francisco>Sep 24: More beta updates</a><br />
<br />
If you've been following the beta this whole time, here's what has changed since the last release:<br />
<br />
<ul><li>Aforementioned 1024 support<br />
<li>We detect mouse movement now and keep track of the last time you were active, so if you were away and then come back to Clicky, whatever report you are viewing will automatically refresh so that it's up to date with live data. This only happens if you're viewing reports for today though.<br />
<li>When a page would load via Ajax, we used to replace the entire main area with a loading graphic. We found it somewhat annoying to have everything be blank essentially until the next page loaded, so instead we now overlay a semi-transparent box over the entire area so you can still see stuff (but not click anything), and the loading graphic is now fixed in the top right corner of the page (so if you scroll up and down while a page is loading, it's always visible).<br />
<li>We investigated replacing the flash graphs with a native javascript solution, spent almost a week on it in fact, but none of the libraries are quite there yet. They all have at least one super annoying limitation or bug, typically having to do with tooltips or the axis/grid. We tried highcharts, flot, and dygraphs. We also looked at other options like raphael, but none of then had the functionality we needed. I'll probably write a blog post in the future about the state of javascript graphing, but that's for another time. So for now, we're staying with flash.<br />
<li>Spy fixed for MSIE (turned out to be some weird conflict with jQuery 1.4.2, so we've gone back to 1.4.1. 1.4.3 just came out today but the problem remains. We'll have to dig deeper).<br />
<li>The biggest complaint we have received is that it's no longer centered. We played around with this quite a bit but ultimately were not satisfied with how it looked centered with a sidebar. Even with a fairly big screen (mine is 1900px wide), I still think it looks good. Just give it a chance to grow on you, ok?</ul><br />
<br />
We've had an average of 1,000 people using this every day, even without posting any updates for a couple of weeks. So we know people are loving it, but we also know that we have almost 200,000 users so a lot of you haven't seen it yet. If there's something you don't like about it, please read through the previous posts linked above. There has been a lot of discussion between us and our beta testers about why things work a certain way or the reasoning behind certain design decisions.<br />
<br />
But based on the feedback so far, we know that most of you will appreciate the changes we made.<br />
<br />
Oh, and if you're a white label customer - it will be about another month before this change is pushed to the white label. This is because there are a number of changes to our layout and CSS, and we want to give you a chance to update everything you need to before it goes live. We'll be emailing you soon with more details.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=gdq2kjwmtwg:RMwIbf8fzvY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=gdq2kjwmtwg:RMwIbf8fzvY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=gdq2kjwmtwg:RMwIbf8fzvY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=gdq2kjwmtwg:RMwIbf8fzvY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=gdq2kjwmtwg:RMwIbf8fzvY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/gdq2kjwmtwg" height="1" width="1"/>";s:7:"pubdate";s:31:"Sat, 16 Oct 2010 15:28:30 -0800";s:5:"bonus";s:10:"1287268110";s:10:"feedburner";a:1:{s:8:"origlink";s:44:"http://getclicky.com/blog/235/the-new-clicky";}s:7:"summary";s:5925:"After nearly 2 months of development, the new Clicky is now live. Here's what it looks like:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201009-beta.gif><br />
<br />
<br />
If you haven't been following our blog, we've had a public beta of our new interface available since September 16. (Hint: this is a good reason to read our blog. We announce important things on it!). The vast majority of the feedback has been very positive, which is remarkable for such a big change.<br />
<br />
This is still the same Clicky you know and love, the main difference is the navigation. The goal here was to make it faster to get to other pages, and to load them faster too. We also wanted the entire site to feel like a true app instead of just a web site.<br />
<br />
So, we created a fixed sidebar that stays with you as you scroll up and down the page (as long as your browser window is at least ~700px tall), and literally <i>everything</i> loads via Ajax, including form submissions (unless you're using Internet Explorer, which has WAY too many problems to support this functionality). However, this new interface is a bit wider than the standard 1024 that most sites aim for. So if we detect that your browser window is less than 1100px wide, the sidebar moves back to the top of the window so it works fairly similar to the old design with the tabs on top. The tabs aren't quite as stylized as they used to be, because we have more of them now so we need to conserve space:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201010-beta-small.gif><br />
<br />
<br />
<b>Update:</b> Some users are experiencing bugs with small site mode being enabled even when their browser window is plenty big. We've temporarily disabled this until we get it figured out.<br />
<br />
To learn more about everything that's new, please read the previous posts we've made about the beta:<br />
<br />
<a href=http://getclicky.com/blog/231/help-test-the-new-clicky-beta>Sep 16: Help test the new Clicky beta</a><br />
<a href=http://getclicky.com/blog/232/beta-updates>Sep 21: Beta updates</a><br />
<a href=http://getclicky.com/blog/233/more-beta-updates-and-were-off-to-san-francisco>Sep 24: More beta updates</a><br />
<br />
If you've been following the beta this whole time, here's what has changed since the last release:<br />
<br />
<ul><li>Aforementioned 1024 support<br />
<li>We detect mouse movement now and keep track of the last time you were active, so if you were away and then come back to Clicky, whatever report you are viewing will automatically refresh so that it's up to date with live data. This only happens if you're viewing reports for today though.<br />
<li>When a page would load via Ajax, we used to replace the entire main area with a loading graphic. We found it somewhat annoying to have everything be blank essentially until the next page loaded, so instead we now overlay a semi-transparent box over the entire area so you can still see stuff (but not click anything), and the loading graphic is now fixed in the top right corner of the page (so if you scroll up and down while a page is loading, it's always visible).<br />
<li>We investigated replacing the flash graphs with a native javascript solution, spent almost a week on it in fact, but none of the libraries are quite there yet. They all have at least one super annoying limitation or bug, typically having to do with tooltips or the axis/grid. We tried highcharts, flot, and dygraphs. We also looked at other options like raphael, but none of then had the functionality we needed. I'll probably write a blog post in the future about the state of javascript graphing, but that's for another time. So for now, we're staying with flash.<br />
<li>Spy fixed for MSIE (turned out to be some weird conflict with jQuery 1.4.2, so we've gone back to 1.4.1. 1.4.3 just came out today but the problem remains. We'll have to dig deeper).<br />
<li>The biggest complaint we have received is that it's no longer centered. We played around with this quite a bit but ultimately were not satisfied with how it looked centered with a sidebar. Even with a fairly big screen (mine is 1900px wide), I still think it looks good. Just give it a chance to grow on you, ok?</ul><br />
<br />
We've had an average of 1,000 people using this every day, even without posting any updates for a couple of weeks. So we know people are loving it, but we also know that we have almost 200,000 users so a lot of you haven't seen it yet. If there's something you don't like about it, please read through the previous posts linked above. There has been a lot of discussion between us and our beta testers about why things work a certain way or the reasoning behind certain design decisions.<br />
<br />
But based on the feedback so far, we know that most of you will appreciate the changes we made.<br />
<br />
Oh, and if you're a white label customer - it will be about another month before this change is pushed to the white label. This is because there are a number of changes to our layout and CSS, and we want to give you a chance to update everything you need to before it goes live. We'll be emailing you soon with more details.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=gdq2kjwmtwg:RMwIbf8fzvY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=gdq2kjwmtwg:RMwIbf8fzvY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=gdq2kjwmtwg:RMwIbf8fzvY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=gdq2kjwmtwg:RMwIbf8fzvY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=gdq2kjwmtwg:RMwIbf8fzvY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/gdq2kjwmtwg" height="1" width="1"/>";}i:17;a:9:{s:5:"title";s:30:"Advice on moving to the cloud?";s:4:"link";s:85:"http://feedproxy.google.com/~r/getclicky/~3/LTlmVAJwY5k/advice-on-moving-to-the-cloud";s:8:"comments";s:59:"http://getclicky.com/blog/234/advice-on-moving-to-the-cloud";s:4:"guid";s:59:"http://getclicky.com/blog/234/advice-on-moving-to-the-cloud";s:11:"description";s:3143:"From day 1 we've managed our own physical servers. We buy them and build them and configure Linux on them and throw them in the data center ourselves. This allows us to configure things exactly as needed, and is quite cost efficient. But man are we getting sick of it. So much time is spent dealing with servers!<br />
<br />
People have often asked us why we don't use a cloud environment, such as Amazon. There's two main reasons. First of all, bandwidth - our load balancers are pumping almost 4,000 requests per <i>second</i> through them during peak hours, and a total of about 250,000,000 requests per day (which is almost 300GB of data - per day). Last I checked, Amazon only includes 5,000,000 requests per <i>month</i>, and you have to pay overages for extra. I don't know what the overage price is but considering we'll be over our limit 30 minutes into any given month, this is a big concern.<br />
<br />
The second reason is reliability. Cloud servers are not really guaranteed from what I understand and they can pop offline at any time. This is a very big deal when it comes to large database being stored on this type of service. Some of our database servers have over 300GB of data, although the average is closer to 100GB. And we have almost 40 database servers. If our databases were in a cloud environment and one of them popped offline, it's going to need repairs done on it before coming back online, since it would not have been shut down properly. Not something I want to deal with.<br />
<br />
So... do any of you have experience running high bandwidth services in a cloud environment? Doesn't have to be Amazon. If so, how do you find the pricing? Also, any experience with running a large database in the cloud? How have you found the reliability? Any advice from people with experience with either of these scenarios is much appreciated.<br />
<br />
We're not necessarily going to do this. It's just under consideration. We just want some input first!<br />
<br />
<b>Update:</b> The overall consensus is that we're insane to consider this, so it's unlikely to happen. It was just an option we were thinking about. Thanks for your advice.<br />
<br />
One thing I was thinking about is what if someone like Google decided to move to a hosted cloud environment. Obviously they're 10000x bigger than us but still - that'd be insane right? To run a high bandwidth and huge I/O service, you need to go old school.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=LTlmVAJwY5k:Dt9PSgSx6Ac:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=LTlmVAJwY5k:Dt9PSgSx6Ac:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=LTlmVAJwY5k:Dt9PSgSx6Ac:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=LTlmVAJwY5k:Dt9PSgSx6Ac:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=LTlmVAJwY5k:Dt9PSgSx6Ac:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/LTlmVAJwY5k" height="1" width="1"/>";s:7:"pubdate";s:31:"Thu, 07 Oct 2010 21:23:47 -0800";s:5:"bonus";s:10:"1286511827";s:10:"feedburner";a:1:{s:8:"origlink";s:59:"http://getclicky.com/blog/234/advice-on-moving-to-the-cloud";}s:7:"summary";s:3143:"From day 1 we've managed our own physical servers. We buy them and build them and configure Linux on them and throw them in the data center ourselves. This allows us to configure things exactly as needed, and is quite cost efficient. But man are we getting sick of it. So much time is spent dealing with servers!<br />
<br />
People have often asked us why we don't use a cloud environment, such as Amazon. There's two main reasons. First of all, bandwidth - our load balancers are pumping almost 4,000 requests per <i>second</i> through them during peak hours, and a total of about 250,000,000 requests per day (which is almost 300GB of data - per day). Last I checked, Amazon only includes 5,000,000 requests per <i>month</i>, and you have to pay overages for extra. I don't know what the overage price is but considering we'll be over our limit 30 minutes into any given month, this is a big concern.<br />
<br />
The second reason is reliability. Cloud servers are not really guaranteed from what I understand and they can pop offline at any time. This is a very big deal when it comes to large database being stored on this type of service. Some of our database servers have over 300GB of data, although the average is closer to 100GB. And we have almost 40 database servers. If our databases were in a cloud environment and one of them popped offline, it's going to need repairs done on it before coming back online, since it would not have been shut down properly. Not something I want to deal with.<br />
<br />
So... do any of you have experience running high bandwidth services in a cloud environment? Doesn't have to be Amazon. If so, how do you find the pricing? Also, any experience with running a large database in the cloud? How have you found the reliability? Any advice from people with experience with either of these scenarios is much appreciated.<br />
<br />
We're not necessarily going to do this. It's just under consideration. We just want some input first!<br />
<br />
<b>Update:</b> The overall consensus is that we're insane to consider this, so it's unlikely to happen. It was just an option we were thinking about. Thanks for your advice.<br />
<br />
One thing I was thinking about is what if someone like Google decided to move to a hosted cloud environment. Obviously they're 10000x bigger than us but still - that'd be insane right? To run a high bandwidth and huge I/O service, you need to go old school.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=LTlmVAJwY5k:Dt9PSgSx6Ac:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=LTlmVAJwY5k:Dt9PSgSx6Ac:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=LTlmVAJwY5k:Dt9PSgSx6Ac:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=LTlmVAJwY5k:Dt9PSgSx6Ac:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=LTlmVAJwY5k:Dt9PSgSx6Ac:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/LTlmVAJwY5k" height="1" width="1"/>";}i:18;a:9:{s:5:"title";s:49:"More beta updates; and we're off to San Francisco";s:4:"link";s:103:"http://feedproxy.google.com/~r/getclicky/~3/ZIcRfV9KT8o/more-beta-updates-and-were-off-to-san-francisco";s:8:"comments";s:77:"http://getclicky.com/blog/233/more-beta-updates-and-were-off-to-san-francisco";s:4:"guid";s:77:"http://getclicky.com/blog/233/more-beta-updates-and-were-off-to-san-francisco";s:11:"description";s:3651:"On Saturday, we're taking the train down to San Francisco for <a href=http://disrupt.techcrunch.com/2010-sf/>TechCrunch Disrupt</a>. We'll be down there for an entire week. We'll try to be good about answering emails, but unless your message is urgent, your patience is appreciated.<br />
<br />
We were <i>really</i> hoping to get the <a href=http://beta.getclicky.com>beta</a> finished and turn it on for everyone before leaving, but it's not quite there yet. The only bugs left that we know of are very minor and are not holding us back, but there's just a bit more polishing to do. Also, we don't want to flip the switch and find out there's some major problem while we're on the road. We've been getting about 1,000 people a day consistently using it, which is great, but once that jumps to over 30,000, a serious problem may surface that we didn't know about. So, we're going to wait until we're back, which will be October 2. We'll probably spend a few more days working on it and then push it out to everyone.<br />
<br />
Here's everything that's new since <a href=http://getclicky.com/blog/232/beta-updates>our last beta release</a>:<br />
<ul><li>When viewing Spy, it's always updated the document title to include the number of online visitors, but no other report did that. Now that we're always displaying this data at the top of every report (which we call stats header for short), it's included in the document title as well no matter what report you're viewing.<br />
<li>Speaking of stats header, Spy will now also update all of those numbers in real time, instead of just visitors online. When viewing any other report, they update once per minute instead.<br />
<li>Command-key support for Macs to open links in new windows<br />
<li>Clicking on a username or IP address in Spy now works<br />
<li>1024 support - if your browser window is less than ~1100 pixels wide, the sidebar now auto-hides itself. Just move your mouse over it to show the full thing. This is one thing we want really feedback on. Only 7% of our users have windows 1024 or smaller, which is awesome, but we still want to provide a good experience for you. So let us know if the auto-hide thing is good for you. We think it could be better and we will improve it, but for now this is what we got. It's not really possible to move the tabs back on top, as we were originally thinking, because of the way a bunch of things work together in our new layout.<br />
<li>Fixed the popular filters form<br />
<li>Fixed bug when filtering visitors by page URL (this was pretty major - any link you clicked on after doing that was completely broken)<br />
<li>Tons of minor bug fixes</ul><br />
<br />
There is only one major bug right now, and that's that somehow Spy broke for MSIE. No idea why. And there's about 10 minor bugs left. We'll be fixing all of those once we get back, then putting a bit more spit and polish on this bad boy and pushing it out the door.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=ZIcRfV9KT8o:OvBC1Ouictc:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=ZIcRfV9KT8o:OvBC1Ouictc:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=ZIcRfV9KT8o:OvBC1Ouictc:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=ZIcRfV9KT8o:OvBC1Ouictc:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=ZIcRfV9KT8o:OvBC1Ouictc:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/ZIcRfV9KT8o" height="1" width="1"/>";s:7:"pubdate";s:31:"Fri, 24 Sep 2010 19:29:04 -0800";s:5:"bonus";s:10:"1285381744";s:10:"feedburner";a:1:{s:8:"origlink";s:77:"http://getclicky.com/blog/233/more-beta-updates-and-were-off-to-san-francisco";}s:7:"summary";s:3651:"On Saturday, we're taking the train down to San Francisco for <a href=http://disrupt.techcrunch.com/2010-sf/>TechCrunch Disrupt</a>. We'll be down there for an entire week. We'll try to be good about answering emails, but unless your message is urgent, your patience is appreciated.<br />
<br />
We were <i>really</i> hoping to get the <a href=http://beta.getclicky.com>beta</a> finished and turn it on for everyone before leaving, but it's not quite there yet. The only bugs left that we know of are very minor and are not holding us back, but there's just a bit more polishing to do. Also, we don't want to flip the switch and find out there's some major problem while we're on the road. We've been getting about 1,000 people a day consistently using it, which is great, but once that jumps to over 30,000, a serious problem may surface that we didn't know about. So, we're going to wait until we're back, which will be October 2. We'll probably spend a few more days working on it and then push it out to everyone.<br />
<br />
Here's everything that's new since <a href=http://getclicky.com/blog/232/beta-updates>our last beta release</a>:<br />
<ul><li>When viewing Spy, it's always updated the document title to include the number of online visitors, but no other report did that. Now that we're always displaying this data at the top of every report (which we call stats header for short), it's included in the document title as well no matter what report you're viewing.<br />
<li>Speaking of stats header, Spy will now also update all of those numbers in real time, instead of just visitors online. When viewing any other report, they update once per minute instead.<br />
<li>Command-key support for Macs to open links in new windows<br />
<li>Clicking on a username or IP address in Spy now works<br />
<li>1024 support - if your browser window is less than ~1100 pixels wide, the sidebar now auto-hides itself. Just move your mouse over it to show the full thing. This is one thing we want really feedback on. Only 7% of our users have windows 1024 or smaller, which is awesome, but we still want to provide a good experience for you. So let us know if the auto-hide thing is good for you. We think it could be better and we will improve it, but for now this is what we got. It's not really possible to move the tabs back on top, as we were originally thinking, because of the way a bunch of things work together in our new layout.<br />
<li>Fixed the popular filters form<br />
<li>Fixed bug when filtering visitors by page URL (this was pretty major - any link you clicked on after doing that was completely broken)<br />
<li>Tons of minor bug fixes</ul><br />
<br />
There is only one major bug right now, and that's that somehow Spy broke for MSIE. No idea why. And there's about 10 minor bugs left. We'll be fixing all of those once we get back, then putting a bit more spit and polish on this bad boy and pushing it out the door.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=ZIcRfV9KT8o:OvBC1Ouictc:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=ZIcRfV9KT8o:OvBC1Ouictc:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=ZIcRfV9KT8o:OvBC1Ouictc:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=ZIcRfV9KT8o:OvBC1Ouictc:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=ZIcRfV9KT8o:OvBC1Ouictc:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/ZIcRfV9KT8o" height="1" width="1"/>";}i:19;a:9:{s:5:"title";s:12:"Beta updates";s:4:"link";s:68:"http://feedproxy.google.com/~r/getclicky/~3/q-sR3KbupIE/beta-updates";s:8:"comments";s:42:"http://getclicky.com/blog/232/beta-updates";s:4:"guid";s:42:"http://getclicky.com/blog/232/beta-updates";s:11:"description";s:4423:"Thank you to everyone who has tested our new <a href=http://getclicky.com/blog/231/help-test-the-new-clicky-beta>beta interface</a> and sent us great feedback on it. The vast majority of the feedback has been very positive, and for such a big change, that's very promising. If you haven't tried yet, <a href=http://beta.getclicky.com/>you should</a>.<br />
<br />
We've been squashing tons of bugs and adding more functionality this week, and we just uploaded all of the changes. As usual, please test and report on any bugs (by leaving a comment on this post).<br />
<br />
One of the biggest changes since the last release is our new user homepage. We heard you loud and clear, you want it to be cleaner and you want your sites above the fold. We used to allow you to hide the forum posts on the user homepage, but always left the blog there because we want as many people reading our posts as possible to stay up to date with what we're doing. With the new layout, there's no need for either of those options anymore, because those things no longer takes up unnecessary vertical space, as you can see from the screenshot below. We took all of the most important user links (upgrade, affiliate, etc) and put them in your face at the top, and put the blog/forum posts next to them. New blog and forum posts will also be highlighted in red so you can see when there's something new to read.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201009-beta2.gif><br />
<br />
<br />
<h4>Changes since the last release</h4><ul><li>New user homepage, as mentioned above<br />
<li>Shift/control clicking a link should now open it in a new window/tab instead of still loading it via ajax<br />
<li>All links that open in a new window should now be fixed (quite a few were broken), except for links inside Spy - those are still broken but we hope to have them fixed tomorrow.<br />
<li>Many of the next page links at the bottom of reports didn't work, but they do now!<br />
<li>Spy basic has been added back in<br />
<li>When viewing mega Spy, there is no longer a dedicated Spy version of visitors online. It now updates the global value at the top of window instead.<br />
<li>We have quite a few javascript files. Most of them (the ones that rarely change) have been consolidated into one large file, which should result in much faster loading<br />
<li>Header stats now show up for MSIE or for any browser that loads a stats page directly (a bug was preventing this from happening before)<br />
<li>If you had scrolled down and tried to open the calendar, it didn't show up. Now it is fixed position so it scrolls up and down with you while it's open.<br />
<li>Tons of other minor bug fixes</ul><br />
<br />
<h4>Things coming soon</h4><ul><li>1024 support<br />
<li>Sidebar menu options only change highlighting when clicked. If you click one, then click back, the old one stays highlighted. This will be fixed.<br />
<li>When viewing Spy, it updates the document title with the visitors online, but no other reports do even though we have a dedicated box at the top of every report showing this value. We'll be updating the entire reporting interface so this is done no matter what page you are viewing.<br />
<li>Links in Spy (e.g. clicking an IP address) will be fixed very soon!<br />
<li>We've had a lot of people ask us, why don't we move to a native (javascript) graphing engine and ditch the flash one while we're redoing the whole site? Well, we do want to do this, but it's a much bigger task than it sounds. There's a ton of backend stuff that would need to be updated. So I don't think this will happen before this is officially released. But we want to do this, so it will happen soon!</ul><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=q-sR3KbupIE:JLlvc14Ia8k:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=q-sR3KbupIE:JLlvc14Ia8k:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=q-sR3KbupIE:JLlvc14Ia8k:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=q-sR3KbupIE:JLlvc14Ia8k:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=q-sR3KbupIE:JLlvc14Ia8k:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/q-sR3KbupIE" height="1" width="1"/>";s:7:"pubdate";s:31:"Tue, 21 Sep 2010 18:13:37 -0800";s:5:"bonus";s:10:"1285118017";s:10:"feedburner";a:1:{s:8:"origlink";s:42:"http://getclicky.com/blog/232/beta-updates";}s:7:"summary";s:4423:"Thank you to everyone who has tested our new <a href=http://getclicky.com/blog/231/help-test-the-new-clicky-beta>beta interface</a> and sent us great feedback on it. The vast majority of the feedback has been very positive, and for such a big change, that's very promising. If you haven't tried yet, <a href=http://beta.getclicky.com/>you should</a>.<br />
<br />
We've been squashing tons of bugs and adding more functionality this week, and we just uploaded all of the changes. As usual, please test and report on any bugs (by leaving a comment on this post).<br />
<br />
One of the biggest changes since the last release is our new user homepage. We heard you loud and clear, you want it to be cleaner and you want your sites above the fold. We used to allow you to hide the forum posts on the user homepage, but always left the blog there because we want as many people reading our posts as possible to stay up to date with what we're doing. With the new layout, there's no need for either of those options anymore, because those things no longer takes up unnecessary vertical space, as you can see from the screenshot below. We took all of the most important user links (upgrade, affiliate, etc) and put them in your face at the top, and put the blog/forum posts next to them. New blog and forum posts will also be highlighted in red so you can see when there's something new to read.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201009-beta2.gif><br />
<br />
<br />
<h4>Changes since the last release</h4><ul><li>New user homepage, as mentioned above<br />
<li>Shift/control clicking a link should now open it in a new window/tab instead of still loading it via ajax<br />
<li>All links that open in a new window should now be fixed (quite a few were broken), except for links inside Spy - those are still broken but we hope to have them fixed tomorrow.<br />
<li>Many of the next page links at the bottom of reports didn't work, but they do now!<br />
<li>Spy basic has been added back in<br />
<li>When viewing mega Spy, there is no longer a dedicated Spy version of visitors online. It now updates the global value at the top of window instead.<br />
<li>We have quite a few javascript files. Most of them (the ones that rarely change) have been consolidated into one large file, which should result in much faster loading<br />
<li>Header stats now show up for MSIE or for any browser that loads a stats page directly (a bug was preventing this from happening before)<br />
<li>If you had scrolled down and tried to open the calendar, it didn't show up. Now it is fixed position so it scrolls up and down with you while it's open.<br />
<li>Tons of other minor bug fixes</ul><br />
<br />
<h4>Things coming soon</h4><ul><li>1024 support<br />
<li>Sidebar menu options only change highlighting when clicked. If you click one, then click back, the old one stays highlighted. This will be fixed.<br />
<li>When viewing Spy, it updates the document title with the visitors online, but no other reports do even though we have a dedicated box at the top of every report showing this value. We'll be updating the entire reporting interface so this is done no matter what page you are viewing.<br />
<li>Links in Spy (e.g. clicking an IP address) will be fixed very soon!<br />
<li>We've had a lot of people ask us, why don't we move to a native (javascript) graphing engine and ditch the flash one while we're redoing the whole site? Well, we do want to do this, but it's a much bigger task than it sounds. There's a ton of backend stuff that would need to be updated. So I don't think this will happen before this is officially released. But we want to do this, so it will happen soon!</ul><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=q-sR3KbupIE:JLlvc14Ia8k:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=q-sR3KbupIE:JLlvc14Ia8k:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=q-sR3KbupIE:JLlvc14Ia8k:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=q-sR3KbupIE:JLlvc14Ia8k:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=q-sR3KbupIE:JLlvc14Ia8k:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/q-sR3KbupIE" height="1" width="1"/>";}i:20;a:9:{s:5:"title";s:29:"Help test the new Clicky beta";s:4:"link";s:85:"http://feedproxy.google.com/~r/getclicky/~3/K92crt9Mqtk/help-test-the-new-clicky-beta";s:8:"comments";s:59:"http://getclicky.com/blog/231/help-test-the-new-clicky-beta";s:4:"guid";s:59:"http://getclicky.com/blog/231/help-test-the-new-clicky-beta";s:11:"description";s:4783:"The last month we have been been doing nothing but working on a massive overhaul of our entire web site. The goal was to make it faster, easier to navigate, and feel like a true web application.<br />
<br />
Check it out at <a href=http://beta.getclicky.com/>beta.getclicky.com</a> (but please read the rest of this post too!)<br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201009-beta.gif><br />
<br />
<br />
What's new?<br />
<ul><li><i>Every page</i> loads via Ajax, including form submissions, which makes everything load lightning fast. (Except for IE - sorry, but this browser just has too many problems).<br />
<li>All navigation is now in a sidebar that changes depending on context. When you're viewing reports, it just contains your report options. (Click the Clicky logo to get back to your user homepage). Every other part of the site will show a different menu instead.<br />
<li>If your screen is at least ~800 px tall, the sidebar is in a fixed position so as you scroll up/down the screen, it's always there.<br />
<li>The sidebar helps us get important data as high up on the page as possible. For example when viewing reports, there used to be around 200 pixels of vertical space before the data you wanted was displayed. Now it's about 20 pixels.<br />
<li>When viewing reports, there are a few figures that are always at the top of every page (visitors online now, and total visitors and actions today). The visitor/action tallies have a sparkline graph next to them as well. These automatically update once per minute.<br />
<li>Lots of other stuff (I'm a bit pressed for time right now)</ul><br />
<br />
This has been tested extensively with all modern browsers - Firefox 3.6, Chrome 6.0, Opera 10.5, Safari 5, and IE7. We haven't tested with older versions of these browsers (or newer, in the case of Firefox 4 (in beta), and IE8/9). So we want to play around with this extensively and report on any bugs here, especially with browsers that we haven't tested.<br />
<br />
This is not complete by any means, but we hope to have it released within the next week or two. There's still some ideas we have brewing, and there are some known bugs:<br />
<br />
<h3>Known bugs/issues that will be fixed</h3><ul><li>This is slightly wider than 1024, which is the standard. Thankfully, only around 7% of our users have a screen that's 1024 or less pixels wide. But we will be adding support for 1024, don't worry. Either the sidebar will automatically hide, or we'll just move the tabs back to the top for these users.<br />
<li>The site may seem kind of slow on your first few page views, but that's because none of these files are on our <a href=http://getclicky.com/blog/203/content-distribution-network-map>CDN</a> yet. That will change when this is released officially!<br />
<li>When viewing Spy, the visitors online figure doesn't necessary match the global one at the top. The global one also updates slower. We'll be fixing this so when you view Spy, it will update both figures instead of just the one inside Spy.<br />
<li>The graphs at the top don't show up for MSIE yet<br />
<li>MSIE also has a few problems with some of the drop down menus that are loaded into the page via ajax<br />
<li>In some browsers, the saved filters drop down menu doesn't work right<br />
<li>The filter results... form at the top of any popular data report doesn't work<br />
<li>When you click on sidebar menu, the item you click is automaically highlighted. If you click back in your browser, that item remained highlighted.<br />
<li>The /user/ pages will probably get their own sidebar menu<br />
<li>If you're a white label user, there is some new and some changes CSS in here. We'll be giving you a 1-month window to create a new CSS file for the new interface, before the new interface goes live. Also, we'll be maintaining the iframe=1 parameter, and when we see that we will automatically adjust to 1024 width, including probably putting the tabs back on top for the reporting interface).</ul><br />
<br />
Let us know what you think!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=K92crt9Mqtk:hQtJlX91sdE:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=K92crt9Mqtk:hQtJlX91sdE:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=K92crt9Mqtk:hQtJlX91sdE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=K92crt9Mqtk:hQtJlX91sdE:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=K92crt9Mqtk:hQtJlX91sdE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/K92crt9Mqtk" height="1" width="1"/>";s:7:"pubdate";s:31:"Thu, 16 Sep 2010 13:25:00 -0800";s:5:"bonus";s:10:"1284668700";s:10:"feedburner";a:1:{s:8:"origlink";s:59:"http://getclicky.com/blog/231/help-test-the-new-clicky-beta";}s:7:"summary";s:4783:"The last month we have been been doing nothing but working on a massive overhaul of our entire web site. The goal was to make it faster, easier to navigate, and feel like a true web application.<br />
<br />
Check it out at <a href=http://beta.getclicky.com/>beta.getclicky.com</a> (but please read the rest of this post too!)<br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201009-beta.gif><br />
<br />
<br />
What's new?<br />
<ul><li><i>Every page</i> loads via Ajax, including form submissions, which makes everything load lightning fast. (Except for IE - sorry, but this browser just has too many problems).<br />
<li>All navigation is now in a sidebar that changes depending on context. When you're viewing reports, it just contains your report options. (Click the Clicky logo to get back to your user homepage). Every other part of the site will show a different menu instead.<br />
<li>If your screen is at least ~800 px tall, the sidebar is in a fixed position so as you scroll up/down the screen, it's always there.<br />
<li>The sidebar helps us get important data as high up on the page as possible. For example when viewing reports, there used to be around 200 pixels of vertical space before the data you wanted was displayed. Now it's about 20 pixels.<br />
<li>When viewing reports, there are a few figures that are always at the top of every page (visitors online now, and total visitors and actions today). The visitor/action tallies have a sparkline graph next to them as well. These automatically update once per minute.<br />
<li>Lots of other stuff (I'm a bit pressed for time right now)</ul><br />
<br />
This has been tested extensively with all modern browsers - Firefox 3.6, Chrome 6.0, Opera 10.5, Safari 5, and IE7. We haven't tested with older versions of these browsers (or newer, in the case of Firefox 4 (in beta), and IE8/9). So we want to play around with this extensively and report on any bugs here, especially with browsers that we haven't tested.<br />
<br />
This is not complete by any means, but we hope to have it released within the next week or two. There's still some ideas we have brewing, and there are some known bugs:<br />
<br />
<h3>Known bugs/issues that will be fixed</h3><ul><li>This is slightly wider than 1024, which is the standard. Thankfully, only around 7% of our users have a screen that's 1024 or less pixels wide. But we will be adding support for 1024, don't worry. Either the sidebar will automatically hide, or we'll just move the tabs back to the top for these users.<br />
<li>The site may seem kind of slow on your first few page views, but that's because none of these files are on our <a href=http://getclicky.com/blog/203/content-distribution-network-map>CDN</a> yet. That will change when this is released officially!<br />
<li>When viewing Spy, the visitors online figure doesn't necessary match the global one at the top. The global one also updates slower. We'll be fixing this so when you view Spy, it will update both figures instead of just the one inside Spy.<br />
<li>The graphs at the top don't show up for MSIE yet<br />
<li>MSIE also has a few problems with some of the drop down menus that are loaded into the page via ajax<br />
<li>In some browsers, the saved filters drop down menu doesn't work right<br />
<li>The filter results... form at the top of any popular data report doesn't work<br />
<li>When you click on sidebar menu, the item you click is automaically highlighted. If you click back in your browser, that item remained highlighted.<br />
<li>The /user/ pages will probably get their own sidebar menu<br />
<li>If you're a white label user, there is some new and some changes CSS in here. We'll be giving you a 1-month window to create a new CSS file for the new interface, before the new interface goes live. Also, we'll be maintaining the iframe=1 parameter, and when we see that we will automatically adjust to 1024 width, including probably putting the tabs back on top for the reporting interface).</ul><br />
<br />
Let us know what you think!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=K92crt9Mqtk:hQtJlX91sdE:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=K92crt9Mqtk:hQtJlX91sdE:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=K92crt9Mqtk:hQtJlX91sdE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=K92crt9Mqtk:hQtJlX91sdE:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=K92crt9Mqtk:hQtJlX91sdE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/K92crt9Mqtk" height="1" width="1"/>";}i:21;a:9:{s:5:"title";s:37:"Tracking server upgrades this weekend";s:4:"link";s:93:"http://feedproxy.google.com/~r/getclicky/~3/SmxFm0eApLY/tracking-server-upgrades-this-weekend";s:8:"comments";s:67:"http://getclicky.com/blog/230/tracking-server-upgrades-this-weekend";s:4:"guid";s:67:"http://getclicky.com/blog/230/tracking-server-upgrades-this-weekend";s:11:"description";s:2339:"The last few months we've been growing faster than we want to. That's a nice problem to have but it has its consequences. We've been getting a surge of high traffic sites using our service, so our tracking servers are really struggling right now. You may have noticed a bit of lag when our tracking code tries to log data to our home servers - that is a result of this. Of course, that data is logged <i>asynchronously</i>, which means it shouldn't interfere with anything on your site, but it's still annoying.<br />
<br />
As we've grown there have always been software tweaks we could make to boost performance, but we're out of options now, these things are as optimized as they're going to get.<br />
<br />
We apologize for this lag recently, but of course it's going to get fixed. This weekend, we'll be adding an additional 2 tracking servers into the mix (currently, there are 3). These 2 servers are much higher end than the existing ones, so it will be 150-200% capacity boost instead of just 67%. This will give us a lot of breathing room, which we could really use.<br />
<br />
<h4>What's next?</h4>The last 3 weeks we've been working on a massive overhaul to the entire web site. It started as just an overhaul to the stats interface, but we decided the entire web site could use an update. This update is <i>awesome</i> but it's also a lot of work. We hope to have a beta available late next week for you to play around with, as we expect there to be some bugs (particularly with older browsers), so we'll need as many people to test it as possible. We'll be announcing it here and on Twitter as soon as it's available!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=SmxFm0eApLY:5gCY8DJ4-aw:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=SmxFm0eApLY:5gCY8DJ4-aw:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=SmxFm0eApLY:5gCY8DJ4-aw:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=SmxFm0eApLY:5gCY8DJ4-aw:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=SmxFm0eApLY:5gCY8DJ4-aw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/SmxFm0eApLY" height="1" width="1"/>";s:7:"pubdate";s:31:"Wed, 01 Sep 2010 13:07:36 -0800";s:5:"bonus";s:10:"1283371656";s:10:"feedburner";a:1:{s:8:"origlink";s:67:"http://getclicky.com/blog/230/tracking-server-upgrades-this-weekend";}s:7:"summary";s:2339:"The last few months we've been growing faster than we want to. That's a nice problem to have but it has its consequences. We've been getting a surge of high traffic sites using our service, so our tracking servers are really struggling right now. You may have noticed a bit of lag when our tracking code tries to log data to our home servers - that is a result of this. Of course, that data is logged <i>asynchronously</i>, which means it shouldn't interfere with anything on your site, but it's still annoying.<br />
<br />
As we've grown there have always been software tweaks we could make to boost performance, but we're out of options now, these things are as optimized as they're going to get.<br />
<br />
We apologize for this lag recently, but of course it's going to get fixed. This weekend, we'll be adding an additional 2 tracking servers into the mix (currently, there are 3). These 2 servers are much higher end than the existing ones, so it will be 150-200% capacity boost instead of just 67%. This will give us a lot of breathing room, which we could really use.<br />
<br />
<h4>What's next?</h4>The last 3 weeks we've been working on a massive overhaul to the entire web site. It started as just an overhaul to the stats interface, but we decided the entire web site could use an update. This update is <i>awesome</i> but it's also a lot of work. We hope to have a beta available late next week for you to play around with, as we expect there to be some bugs (particularly with older browsers), so we'll need as many people to test it as possible. We'll be announcing it here and on Twitter as soon as it's available!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=SmxFm0eApLY:5gCY8DJ4-aw:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=SmxFm0eApLY:5gCY8DJ4-aw:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=SmxFm0eApLY:5gCY8DJ4-aw:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=SmxFm0eApLY:5gCY8DJ4-aw:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=SmxFm0eApLY:5gCY8DJ4-aw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/SmxFm0eApLY" height="1" width="1"/>";}i:22;a:9:{s:5:"title";s:33:"Why Clicky validates your traffic";s:4:"link";s:89:"http://feedproxy.google.com/~r/getclicky/~3/iBSOxJjmuOo/why-clicky-validates-your-traffic";s:8:"comments";s:63:"http://getclicky.com/blog/229/why-clicky-validates-your-traffic";s:4:"guid";s:63:"http://getclicky.com/blog/229/why-clicky-validates-your-traffic";s:11:"description";s:2651:"A couple users in our forums were just talking about how <a href=http://getclicky.com/forums/?id=6032>their Google Analytics reports are unreliable</a> because people have copied their GA tracking code (for reasons unknown) onto their web sites, and now the traffic from these other sites is being reported in GA alongside the real traffic that should only be getting logged in the first place.<br />
<br />
We had no idea GA allowed this to happen and frankly, we were surprised to hear it. If I was a <a href=http://en.wikipedia.org/wiki/Griefer>griefer</a>, and I owned a high traffic, off-color web site, I might get my lulz by regularly including the GA code from other random sites in my own web site's HTML. Hypothetically, of course :)<br />
<br />
This is one of the reasons we chose to validate your traffic against your registered domain name before logging it. And this was one of the very, <i>very</i> first things we ever did when we were designing Clicky. We're talking October 2006, before Clicky was even available to the public. This has caused headaches for some users over the years, e.g. if they mistype their domain when registering, or their domain changes but they don't update it on Clicky, then no traffic gets logged. But for the most part it's worked well for everyone, and to make it flexible we have offered (also from day 1) a mirrors option to add additional domains that are authorized to log traffic for a certain site ID.<br />
<br />
We don't know if other analytics services do any validation, but if not, maybe we should add another bullet point to <a href=http://getclicky.com/#theotherguys>ye olde matrix</a>. I imagine Google may do this for support reasons, so they get as few questions about why aren't my stats working as possible, but we still don't agree with it. We get support questions about this maybe once a week, but we have no problem helping people out with it.<br />
<br />
What do you think?<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=iBSOxJjmuOo:G_6PIOnXL_U:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=iBSOxJjmuOo:G_6PIOnXL_U:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=iBSOxJjmuOo:G_6PIOnXL_U:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=iBSOxJjmuOo:G_6PIOnXL_U:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=iBSOxJjmuOo:G_6PIOnXL_U:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/iBSOxJjmuOo" height="1" width="1"/>";s:7:"pubdate";s:31:"Wed, 11 Aug 2010 17:43:12 -0800";s:5:"bonus";s:10:"1281573792";s:10:"feedburner";a:1:{s:8:"origlink";s:63:"http://getclicky.com/blog/229/why-clicky-validates-your-traffic";}s:7:"summary";s:2651:"A couple users in our forums were just talking about how <a href=http://getclicky.com/forums/?id=6032>their Google Analytics reports are unreliable</a> because people have copied their GA tracking code (for reasons unknown) onto their web sites, and now the traffic from these other sites is being reported in GA alongside the real traffic that should only be getting logged in the first place.<br />
<br />
We had no idea GA allowed this to happen and frankly, we were surprised to hear it. If I was a <a href=http://en.wikipedia.org/wiki/Griefer>griefer</a>, and I owned a high traffic, off-color web site, I might get my lulz by regularly including the GA code from other random sites in my own web site's HTML. Hypothetically, of course :)<br />
<br />
This is one of the reasons we chose to validate your traffic against your registered domain name before logging it. And this was one of the very, <i>very</i> first things we ever did when we were designing Clicky. We're talking October 2006, before Clicky was even available to the public. This has caused headaches for some users over the years, e.g. if they mistype their domain when registering, or their domain changes but they don't update it on Clicky, then no traffic gets logged. But for the most part it's worked well for everyone, and to make it flexible we have offered (also from day 1) a mirrors option to add additional domains that are authorized to log traffic for a certain site ID.<br />
<br />
We don't know if other analytics services do any validation, but if not, maybe we should add another bullet point to <a href=http://getclicky.com/#theotherguys>ye olde matrix</a>. I imagine Google may do this for support reasons, so they get as few questions about why aren't my stats working as possible, but we still don't agree with it. We get support questions about this maybe once a week, but we have no problem helping people out with it.<br />
<br />
What do you think?<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=iBSOxJjmuOo:G_6PIOnXL_U:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=iBSOxJjmuOo:G_6PIOnXL_U:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=iBSOxJjmuOo:G_6PIOnXL_U:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=iBSOxJjmuOo:G_6PIOnXL_U:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=iBSOxJjmuOo:G_6PIOnXL_U:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/iBSOxJjmuOo" height="1" width="1"/>";}i:23;a:9:{s:5:"title";s:36:"Viddler rolls out Clicky integration";s:4:"link";s:92:"http://feedproxy.google.com/~r/getclicky/~3/pg2AUa7eHh8/viddler-rolls-out-clicky-integration";s:8:"comments";s:66:"http://getclicky.com/blog/228/viddler-rolls-out-clicky-integration";s:4:"guid";s:66:"http://getclicky.com/blog/228/viddler-rolls-out-clicky-integration";s:11:"description";s:2493:"When we <a href=http://getclicky.com/blog/224/video-analytics>announced</a> our new video analytics a few weeks ago, one of the things we mentioned is that <a href=http://viddler.com>Viddler</a> was integrating Clicky directly into their flash player - except it wasn't quite ready at the time. This is really wonderful because tracking video interactions is not quite as easy as we'd like it to be. You have to embed videos with their Javascript API enabled, which is not the default for any service, and then you have to add a bit of extra code so that their API talks to our API... etc.<br />
<br />
Viddler, on the other hand, was already using Clicky for their own site and started talking to us a few months back about making Viddler tracking fully automatic. This is actually what motivated us to make this feature in the first place. We knew all these services had APIs but we didn't really want to deal with them. Of course, we ended up writing libraries for two of the top services (Youtube and Vimeo) as well as a library for tracking HTML5 videos anyways, because that's how we roll.<br />
<br />
Well, the wait is finally over. <a href=http://blog.viddler.com/sandieman/getclicky-analytics-integration/>Viddler has just announced</a> that their integration with Clicky has gone live. Any of you who have at least a Pro account and have Viddler videos embedded on your web site, you should start seeing data automatically in your Content > Video report, without having to do a gosh darn thing.<br />
<br />
We're really excited about this because not only are we one of a small handful of analytics companies to offer video analytics, but as of now, I believe we are the <i>only</i> analytics service to have fully automatic integration with a large third party video provider.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=pg2AUa7eHh8:Z9YMT3IQUN0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=pg2AUa7eHh8:Z9YMT3IQUN0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=pg2AUa7eHh8:Z9YMT3IQUN0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=pg2AUa7eHh8:Z9YMT3IQUN0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=pg2AUa7eHh8:Z9YMT3IQUN0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/pg2AUa7eHh8" height="1" width="1"/>";s:7:"pubdate";s:31:"Tue, 10 Aug 2010 11:53:51 -0800";s:5:"bonus";s:10:"1281466431";s:10:"feedburner";a:1:{s:8:"origlink";s:66:"http://getclicky.com/blog/228/viddler-rolls-out-clicky-integration";}s:7:"summary";s:2493:"When we <a href=http://getclicky.com/blog/224/video-analytics>announced</a> our new video analytics a few weeks ago, one of the things we mentioned is that <a href=http://viddler.com>Viddler</a> was integrating Clicky directly into their flash player - except it wasn't quite ready at the time. This is really wonderful because tracking video interactions is not quite as easy as we'd like it to be. You have to embed videos with their Javascript API enabled, which is not the default for any service, and then you have to add a bit of extra code so that their API talks to our API... etc.<br />
<br />
Viddler, on the other hand, was already using Clicky for their own site and started talking to us a few months back about making Viddler tracking fully automatic. This is actually what motivated us to make this feature in the first place. We knew all these services had APIs but we didn't really want to deal with them. Of course, we ended up writing libraries for two of the top services (Youtube and Vimeo) as well as a library for tracking HTML5 videos anyways, because that's how we roll.<br />
<br />
Well, the wait is finally over. <a href=http://blog.viddler.com/sandieman/getclicky-analytics-integration/>Viddler has just announced</a> that their integration with Clicky has gone live. Any of you who have at least a Pro account and have Viddler videos embedded on your web site, you should start seeing data automatically in your Content > Video report, without having to do a gosh darn thing.<br />
<br />
We're really excited about this because not only are we one of a small handful of analytics companies to offer video analytics, but as of now, I believe we are the <i>only</i> analytics service to have fully automatic integration with a large third party video provider.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=pg2AUa7eHh8:Z9YMT3IQUN0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=pg2AUa7eHh8:Z9YMT3IQUN0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=pg2AUa7eHh8:Z9YMT3IQUN0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=pg2AUa7eHh8:Z9YMT3IQUN0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=pg2AUa7eHh8:Z9YMT3IQUN0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/pg2AUa7eHh8" height="1" width="1"/>";}i:24;a:9:{s:5:"title";s:41:"When did visitor XYZ first visit my site?";s:4:"link";s:96:"http://feedproxy.google.com/~r/getclicky/~3/WSQAS-ws7I8/when-did-visitor-xyz-first-visit-my-site";s:8:"comments";s:70:"http://getclicky.com/blog/227/when-did-visitor-xyz-first-visit-my-site";s:4:"guid";s:70:"http://getclicky.com/blog/227/when-did-visitor-xyz-first-visit-my-site";s:11:"description";s:1808:"<img src=http://static.getclicky.com/media/screenshots/201008-first-visit.gif><br />
<br />
<br />
We've only been tracking this data since mid-April, with <a href=http://getclicky.com/blog/211/heres-what-new>this release</a>. So for loyal visitors, you may a see a lot of dates around mid-April. That's a bummer, but it's also part of the reason we've been waiting to release this feature - we wanted to have at least a few months of data. We now have almost 4 months so we feel it's good to go.<br />
<br />
This feature will be particularly useful to those of you who use our goal system. We use goals to track when people upgrade to our premium service so we can see it right in our stats. (Of course, we have an admin area to see all of this data too, but it's more fun when it's in your stats). As you can see in this screenshot, taken from a visitor today (with all identifying info removed), this person first visited in... well, mid-April. The point is, we immediately know how long this person has been coming to our site before upgrading, and we can see it right in their session details. Fun!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=WSQAS-ws7I8:3i7ckDPac4M:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=WSQAS-ws7I8:3i7ckDPac4M:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=WSQAS-ws7I8:3i7ckDPac4M:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=WSQAS-ws7I8:3i7ckDPac4M:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=WSQAS-ws7I8:3i7ckDPac4M:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/WSQAS-ws7I8" height="1" width="1"/>";s:7:"pubdate";s:31:"Fri, 06 Aug 2010 14:03:41 -0800";s:5:"bonus";s:10:"1281128621";s:10:"feedburner";a:1:{s:8:"origlink";s:70:"http://getclicky.com/blog/227/when-did-visitor-xyz-first-visit-my-site";}s:7:"summary";s:1808:"<img src=http://static.getclicky.com/media/screenshots/201008-first-visit.gif><br />
<br />
<br />
We've only been tracking this data since mid-April, with <a href=http://getclicky.com/blog/211/heres-what-new>this release</a>. So for loyal visitors, you may a see a lot of dates around mid-April. That's a bummer, but it's also part of the reason we've been waiting to release this feature - we wanted to have at least a few months of data. We now have almost 4 months so we feel it's good to go.<br />
<br />
This feature will be particularly useful to those of you who use our goal system. We use goals to track when people upgrade to our premium service so we can see it right in our stats. (Of course, we have an admin area to see all of this data too, but it's more fun when it's in your stats). As you can see in this screenshot, taken from a visitor today (with all identifying info removed), this person first visited in... well, mid-April. The point is, we immediately know how long this person has been coming to our site before upgrading, and we can see it right in their session details. Fun!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=WSQAS-ws7I8:3i7ckDPac4M:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=WSQAS-ws7I8:3i7ckDPac4M:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=WSQAS-ws7I8:3i7ckDPac4M:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=WSQAS-ws7I8:3i7ckDPac4M:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=WSQAS-ws7I8:3i7ckDPac4M:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/WSQAS-ws7I8" height="1" width="1"/>";}i:25;a:9:{s:5:"title";s:20:"HTML5 video tracking";s:4:"link";s:76:"http://feedproxy.google.com/~r/getclicky/~3/eycXhwZnGJ4/html5-video-tracking";s:8:"comments";s:50:"http://getclicky.com/blog/226/html5-video-tracking";s:4:"guid";s:50:"http://getclicky.com/blog/226/html5-video-tracking";s:11:"description";s:1415:"We've just added a <a href=http://getclicky.com/help/video#html5>new library</a> for tracking <a href=http://en.wikipedia.org/wiki/HTML5_video>HTML5 videos</a>. The best part is that since HTML5 videos are native browser elements with a common API across all browsers, all you have to do track these videos with Clicky is to add one line of code to include this library on your site - and that's it. It will automatically find all HTML5 video elements on any page it's installed on, and interface with our video API to track people playing these videos.<br />
<br />
HTML5 video is still in its infancy, but it is the future of online video and we are happy to provide great support for tracking it. Have at it!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=eycXhwZnGJ4:TnXBi3FT_is:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=eycXhwZnGJ4:TnXBi3FT_is:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=eycXhwZnGJ4:TnXBi3FT_is:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=eycXhwZnGJ4:TnXBi3FT_is:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=eycXhwZnGJ4:TnXBi3FT_is:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/eycXhwZnGJ4" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 02 Aug 2010 23:40:04 -0800";s:5:"bonus";s:10:"1280817604";s:10:"feedburner";a:1:{s:8:"origlink";s:50:"http://getclicky.com/blog/226/html5-video-tracking";}s:7:"summary";s:1415:"We've just added a <a href=http://getclicky.com/help/video#html5>new library</a> for tracking <a href=http://en.wikipedia.org/wiki/HTML5_video>HTML5 videos</a>. The best part is that since HTML5 videos are native browser elements with a common API across all browsers, all you have to do track these videos with Clicky is to add one line of code to include this library on your site - and that's it. It will automatically find all HTML5 video elements on any page it's installed on, and interface with our video API to track people playing these videos.<br />
<br />
HTML5 video is still in its infancy, but it is the future of online video and we are happy to provide great support for tracking it. Have at it!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=eycXhwZnGJ4:TnXBi3FT_is:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=eycXhwZnGJ4:TnXBi3FT_is:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=eycXhwZnGJ4:TnXBi3FT_is:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=eycXhwZnGJ4:TnXBi3FT_is:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=eycXhwZnGJ4:TnXBi3FT_is:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/eycXhwZnGJ4" height="1" width="1"/>";}i:26;a:9:{s:5:"title";s:28:"An update on Google and Ajax";s:4:"link";s:84:"http://feedproxy.google.com/~r/getclicky/~3/W-7NGNlBYzg/an-update-on-google-and-ajax";s:8:"comments";s:58:"http://getclicky.com/blog/225/an-update-on-google-and-ajax";s:4:"guid";s:58:"http://getclicky.com/blog/225/an-update-on-google-and-ajax";s:11:"description";s:3565:"Who remembers <a href=http://getclicky.com/blog/150/googles-new-ajax-powered-search-results-breaks-search-keyword-tracking-for-everyone>this story</a> from February 2009? This is when Google began testing the use of Ajax in its search results to speed up page loads. It definitely makes things faster and Google said speed was the sole reason behind it. The problem is that the search query is now hidden behind the hash tag of the URL, and browsers don't send hash tags with referrer data. In other words, analytics services like Clicky can't get the search term that the visitor used to find your site.<br />
<br />
We raised a small fit about it because we think knowing what your visitors are searching for to find your site is an extremely important aspect of running a web site. I claimed that they would have some way to keep the searches integrated with Google Analytics, but Google denied that was possible. I don't really believe that - they are able to integrate AdWords data into Google Analytics just fine - but whatever.<br />
<br />
Anyways. Google stopped doing it for a while, or at least dramatically reduced the number of users who get this feature, because I didn't see any plain google.com referrers in our stats for quite a while. Recently though, I've been seeing more, and in particular, the last couple of weeks.<br />
<br />
We get a lot of emails about this, people asking us how could the referrer possibly be just google.com and nothing else. <br />
<br />
Well, this is the reason. And we're getting a bit tired of this question :) So, as of about an hour ago, when we see a referrer come in that is just google.com (or any other TLD) and there is no path and no query, we're simply going to pretend the referrer doesn't exist. The downside to this is that previously, at least you knew they came in from Google, even if you don't know what that search was. Now you won't know even that. But, you have to consider our perspective too. This is mainly about about support.<br />
<br />
The other option would be to keep the same referrer in there and just make up a fake search, e.g. Unknown, so you would see that for visitors who had an unknown search term from Google. But we're afraid there will be a lot of people who take this literally and think someone is actually searching for the term unknown and then they will think Clicky is broken.<br />
<br />
From a support perspective, we think the best thing to do is just filter these out. But please let us know how you feel about this decision, or if you have any other ideas.<br />
<br />
<b>Update:</b> We hear you. None of you like this. We'll be removing it later today and coming up with something else. We liked the idea one of you listed, of having it say unknown but then just linking that to a help page explaining what it means. We'll probably do something like that.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=W-7NGNlBYzg:3borz_79HyQ:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=W-7NGNlBYzg:3borz_79HyQ:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=W-7NGNlBYzg:3borz_79HyQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=W-7NGNlBYzg:3borz_79HyQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=W-7NGNlBYzg:3borz_79HyQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/W-7NGNlBYzg" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 02 Aug 2010 12:20:30 -0800";s:5:"bonus";s:10:"1280776830";s:10:"feedburner";a:1:{s:8:"origlink";s:58:"http://getclicky.com/blog/225/an-update-on-google-and-ajax";}s:7:"summary";s:3565:"Who remembers <a href=http://getclicky.com/blog/150/googles-new-ajax-powered-search-results-breaks-search-keyword-tracking-for-everyone>this story</a> from February 2009? This is when Google began testing the use of Ajax in its search results to speed up page loads. It definitely makes things faster and Google said speed was the sole reason behind it. The problem is that the search query is now hidden behind the hash tag of the URL, and browsers don't send hash tags with referrer data. In other words, analytics services like Clicky can't get the search term that the visitor used to find your site.<br />
<br />
We raised a small fit about it because we think knowing what your visitors are searching for to find your site is an extremely important aspect of running a web site. I claimed that they would have some way to keep the searches integrated with Google Analytics, but Google denied that was possible. I don't really believe that - they are able to integrate AdWords data into Google Analytics just fine - but whatever.<br />
<br />
Anyways. Google stopped doing it for a while, or at least dramatically reduced the number of users who get this feature, because I didn't see any plain google.com referrers in our stats for quite a while. Recently though, I've been seeing more, and in particular, the last couple of weeks.<br />
<br />
We get a lot of emails about this, people asking us how could the referrer possibly be just google.com and nothing else. <br />
<br />
Well, this is the reason. And we're getting a bit tired of this question :) So, as of about an hour ago, when we see a referrer come in that is just google.com (or any other TLD) and there is no path and no query, we're simply going to pretend the referrer doesn't exist. The downside to this is that previously, at least you knew they came in from Google, even if you don't know what that search was. Now you won't know even that. But, you have to consider our perspective too. This is mainly about about support.<br />
<br />
The other option would be to keep the same referrer in there and just make up a fake search, e.g. Unknown, so you would see that for visitors who had an unknown search term from Google. But we're afraid there will be a lot of people who take this literally and think someone is actually searching for the term unknown and then they will think Clicky is broken.<br />
<br />
From a support perspective, we think the best thing to do is just filter these out. But please let us know how you feel about this decision, or if you have any other ideas.<br />
<br />
<b>Update:</b> We hear you. None of you like this. We'll be removing it later today and coming up with something else. We liked the idea one of you listed, of having it say unknown but then just linking that to a help page explaining what it means. We'll probably do something like that.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=W-7NGNlBYzg:3borz_79HyQ:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=W-7NGNlBYzg:3borz_79HyQ:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=W-7NGNlBYzg:3borz_79HyQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=W-7NGNlBYzg:3borz_79HyQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=W-7NGNlBYzg:3borz_79HyQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/W-7NGNlBYzg" height="1" width="1"/>";}i:27;a:9:{s:5:"title";s:15:"Video analytics";s:4:"link";s:71:"http://feedproxy.google.com/~r/getclicky/~3/PqXG33tVoW4/video-analytics";s:8:"comments";s:45:"http://getclicky.com/blog/224/video-analytics";s:4:"guid";s:45:"http://getclicky.com/blog/224/video-analytics";s:11:"description";s:4173:"Video analytics has arrived! <a href=http://getclicky.com/help/video>Documentation is here</a>. Once you have set this up on your web site, here is an example report you would see under the new Content:Video tab.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201007-video-analytics.gif><br />
<br />
<br />
We've tried to make this as easy as possible for you to use, so we have two announcements to make. <br />
<br />
<h3>Viddler</h3>First, we have partnered with <a href=http://viddler.com>Viddler</a> to make video analytics <i>fully automatic</i>. Any Viddler video you have on your web site, no additional programming is required, it will just simply work. However, Viddler's implementation of this isn't quite done, so this isn't available yet. But we expect it to be ready by the end of August, and we'll certainly let you know the second that it is.<br />
<br />
<h3>Youtube</h3>Youtube is the most popular video service in the world, so we have created our own Javascript library (with the help of <a href=http://cnanney.com/>Chris Nanney</a>, the same person who created the awesome <a href=http://getclicky.com/blog/200/if-you-use-google-chrome-youll-like-this>Google Chrome extension</a>) to make tracking Youtube as easy as possible. Unfortunately, without a direct partnership, we can't make it fully automatic like we are with Viddler. But it's still very easy to implement, requiring just six lines of code for one video, and two additional lines for each additional video, on any one web page. See the docs <a href=http://getclicky.com/help/video#viddler>here</a>.<br />
<br />
<h3>UPDATE: Vimeo!</h3>A number of you requested a library for tracking Vimeo. We got this done today, it is available in the documentation. Unfortunately, it's a bit more cumbersome than tracking Youtube, because they require a lot more data to be declared when embedding a video. Also, their API doesn't have a method to get the video's ID or public URL, so you have to declare the ID for us so our code can build the URL automatically.<br />
<br />
<br />
The example report above was created from the help of many Twitter users earlier today. We <a href=http://twitter.com/getclicky/status/19851870473>tweeted</a>, asking people to go to <a href=http://getclicky.com/youtube>this page</a> and play around with the videos (we hope you enjoyed the moonwalking). You can see the actual up to date reports in our demo on the following pages:<br />
<br />
- <a href=http://getclicky.com/stats/content-video?site_id=32020>The main video report page</a><br />
- <a href=http://getclicky.com/stats/home?site_id=32020>Dashboard</a> (we created a new module just for vidoes)<br />
- <a href=http://getclicky.com/stats/visitors-actions?site_id=32020action_type=video>Action log</a> (we created a new filter to just view video actions)<br />
<br />
Video interactions will also show up in Spy, although the specific type of action (play, pause, etc) does not - yet. We may add it, but that would require editing the Javascript, and if you haven't seen the Spy javascript - <a href=http://static.getclicky.com/inc/javascript/spy.js>it's a doozy</a>. We think just showing the fact that people are playing the videos at all is pretty neat to see in Spy.<br />
<br />
Let us know what you think!<br />
<br />
Oh, and if any of you developers out there want to create a library for other video services, let us know. We'll happily link to it or host it ourselves.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=PqXG33tVoW4:2qD8zj5YGco:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=PqXG33tVoW4:2qD8zj5YGco:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=PqXG33tVoW4:2qD8zj5YGco:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=PqXG33tVoW4:2qD8zj5YGco:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=PqXG33tVoW4:2qD8zj5YGco:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/PqXG33tVoW4" height="1" width="1"/>";s:7:"pubdate";s:31:"Thu, 29 Jul 2010 16:31:35 -0800";s:5:"bonus";s:10:"1280446295";s:10:"feedburner";a:1:{s:8:"origlink";s:45:"http://getclicky.com/blog/224/video-analytics";}s:7:"summary";s:4173:"Video analytics has arrived! <a href=http://getclicky.com/help/video>Documentation is here</a>. Once you have set this up on your web site, here is an example report you would see under the new Content:Video tab.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201007-video-analytics.gif><br />
<br />
<br />
We've tried to make this as easy as possible for you to use, so we have two announcements to make. <br />
<br />
<h3>Viddler</h3>First, we have partnered with <a href=http://viddler.com>Viddler</a> to make video analytics <i>fully automatic</i>. Any Viddler video you have on your web site, no additional programming is required, it will just simply work. However, Viddler's implementation of this isn't quite done, so this isn't available yet. But we expect it to be ready by the end of August, and we'll certainly let you know the second that it is.<br />
<br />
<h3>Youtube</h3>Youtube is the most popular video service in the world, so we have created our own Javascript library (with the help of <a href=http://cnanney.com/>Chris Nanney</a>, the same person who created the awesome <a href=http://getclicky.com/blog/200/if-you-use-google-chrome-youll-like-this>Google Chrome extension</a>) to make tracking Youtube as easy as possible. Unfortunately, without a direct partnership, we can't make it fully automatic like we are with Viddler. But it's still very easy to implement, requiring just six lines of code for one video, and two additional lines for each additional video, on any one web page. See the docs <a href=http://getclicky.com/help/video#viddler>here</a>.<br />
<br />
<h3>UPDATE: Vimeo!</h3>A number of you requested a library for tracking Vimeo. We got this done today, it is available in the documentation. Unfortunately, it's a bit more cumbersome than tracking Youtube, because they require a lot more data to be declared when embedding a video. Also, their API doesn't have a method to get the video's ID or public URL, so you have to declare the ID for us so our code can build the URL automatically.<br />
<br />
<br />
The example report above was created from the help of many Twitter users earlier today. We <a href=http://twitter.com/getclicky/status/19851870473>tweeted</a>, asking people to go to <a href=http://getclicky.com/youtube>this page</a> and play around with the videos (we hope you enjoyed the moonwalking). You can see the actual up to date reports in our demo on the following pages:<br />
<br />
- <a href=http://getclicky.com/stats/content-video?site_id=32020>The main video report page</a><br />
- <a href=http://getclicky.com/stats/home?site_id=32020>Dashboard</a> (we created a new module just for vidoes)<br />
- <a href=http://getclicky.com/stats/visitors-actions?site_id=32020action_type=video>Action log</a> (we created a new filter to just view video actions)<br />
<br />
Video interactions will also show up in Spy, although the specific type of action (play, pause, etc) does not - yet. We may add it, but that would require editing the Javascript, and if you haven't seen the Spy javascript - <a href=http://static.getclicky.com/inc/javascript/spy.js>it's a doozy</a>. We think just showing the fact that people are playing the videos at all is pretty neat to see in Spy.<br />
<br />
Let us know what you think!<br />
<br />
Oh, and if any of you developers out there want to create a library for other video services, let us know. We'll happily link to it or host it ourselves.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=PqXG33tVoW4:2qD8zj5YGco:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=PqXG33tVoW4:2qD8zj5YGco:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=PqXG33tVoW4:2qD8zj5YGco:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=PqXG33tVoW4:2qD8zj5YGco:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=PqXG33tVoW4:2qD8zj5YGco:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/PqXG33tVoW4" height="1" width="1"/>";}i:28;a:9:{s:5:"title";s:29:"New feature: Save yo' filters";s:4:"link";s:83:"http://feedproxy.google.com/~r/getclicky/~3/tLVrtt7k0bc/new-feature-save-yo-filters";s:8:"comments";s:57:"http://getclicky.com/blog/222/new-feature-save-yo-filters";s:4:"guid";s:57:"http://getclicky.com/blog/222/new-feature-save-yo-filters";s:11:"description";s:1314:"Another new feature rolling out today: saved filters. We've had a lot of requests for this. Now whenever you have filters invoked, you will see an option to save them. As well, there is a menu you can click on to quickly access all of your saved filters. To delete any saved filters, there's a new section in your site prefs to manage them. Filters are global which means any saved filter will appear in the menu for all of your sites. Simple! Perfect!<br />
<br />
This new feature is available to all users.<br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201007-saved-filters.gif><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=tLVrtt7k0bc:9muQWbeVMGs:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=tLVrtt7k0bc:9muQWbeVMGs:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=tLVrtt7k0bc:9muQWbeVMGs:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=tLVrtt7k0bc:9muQWbeVMGs:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=tLVrtt7k0bc:9muQWbeVMGs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/tLVrtt7k0bc" height="1" width="1"/>";s:7:"pubdate";s:31:"Sat, 03 Jul 2010 10:35:40 -0800";s:5:"bonus";s:10:"1278178540";s:10:"feedburner";a:1:{s:8:"origlink";s:57:"http://getclicky.com/blog/222/new-feature-save-yo-filters";}s:7:"summary";s:1314:"Another new feature rolling out today: saved filters. We've had a lot of requests for this. Now whenever you have filters invoked, you will see an option to save them. As well, there is a menu you can click on to quickly access all of your saved filters. To delete any saved filters, there's a new section in your site prefs to manage them. Filters are global which means any saved filter will appear in the menu for all of your sites. Simple! Perfect!<br />
<br />
This new feature is available to all users.<br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201007-saved-filters.gif><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=tLVrtt7k0bc:9muQWbeVMGs:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=tLVrtt7k0bc:9muQWbeVMGs:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=tLVrtt7k0bc:9muQWbeVMGs:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=tLVrtt7k0bc:9muQWbeVMGs:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=tLVrtt7k0bc:9muQWbeVMGs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/tLVrtt7k0bc" height="1" width="1"/>";}i:29;a:9:{s:5:"title";s:36:"$5,000 for an Android desktop widget";s:4:"link";s:90:"http://feedproxy.google.com/~r/getclicky/~3/4xBFfFEA7ow/5000-for-an-android-desktop-widget";s:8:"comments";s:64:"http://getclicky.com/blog/221/5000-for-an-android-desktop-widget";s:4:"guid";s:64:"http://getclicky.com/blog/221/5000-for-an-android-desktop-widget";s:11:"description";s:8066:"<img class=fr ml20 mb20 src=http://static.getclicky.com/media/screenshots/android-pandora.png><b class=red>JULY 6 UPDATE: We have a good pool of developers to choose from at this time, so we are no longer accepting applicants for this project. Thank you for all of the interest!</b><br />
<br />
We're very much in love with Android and would like nothing more than to have a desktop widget to always have <a href=http://getclicky.com/demo>our stats</a> available at a quick glance. If you're not familiar with Android widgets, they're basically apps that run on your desktop alongside your icons. For example, on the right hand side is a screenshot of the Pandora widget - you can control the entire app without actually being inside the app.<br />
<br />
We really dig this functionality and are looking for something similar for Clicky so you can always have your stats right in front of you. I personally am interested in exploring Android development in the future because I believe very strongly in this operating system, but I don't know Java and it would probably take me several months of full time development to get something like this up and running - time I don't currently have.<br />
<br />
<h3>What the widget should do</h3><ul><li>When user adds the widget to their desktop:<br />
<ul><li><b>Four sizes to choose from in the widget menu</b> - 2x1, 4x1, 2x2, and 4x2. We wish the widget size was definable at run time but it's not so we'll have to pollute the widget menu with four sizes :(<br />
<li><b>If they are adding this widget for the first time</b>, you need to ask for their credentials, which you send to an API to grab their list of sites. You save these credentials locally on the phone so if the user adds more than one widget, they don't have to re-enter their credentials. (Note to users concerned with privacy - we're inventing a new version of OAuth called Simple OAuth that will protect your password and let you revoke access to services as needed, without having to change your password - more details on that later). Once the credentials have been verified, the next screen lets them select all of the following options <i><u>on one screen:</u></i><br />
<li><b>The web site</b> they want the widget to display stats for.<br />
<li><b>Refresh interval</b> (5m, 15m, 30m, 1h, 2h, 3h, 4h) (Note: when device is sleeping, the data should not be refreshed. It should only be refreshed upon wake, or while the device is in use).<br />
<li><b>Widgets 1 panel high</b> show site name at top, then visitors and actions below that for today (including trend percentages for each item). <b>If it's 2 panels high</b>, also show bounce rate and goals/revenue (if they have goals setup). Use icons rather than text to differentiate these data types, to save space (if you're not familiar with Clicky, see our <a href=http://getclicky.com/demo>demo</a> to see the icons we use).<br />
<li><b>If the widget is 4 panels wide</b> (4x1 or 4x2), they can one choose additional piece of data to display:<br />
<ul><li>Additional dates for the default data (e.g. column 2 could show yesterday or last 7 days for visitors/actions/etc)<br />
<li>Popular data types (e.g. top searches, top goals, etc),<br />
<li>Graph of hourly data for visitors or actions for today, or graph of visitors or actions for the last 30 days<br />
</ul></ul><br />
<li>Clicking the widget opens up a full screen window:<br />
<ul><li><b>Shows same data but with more detail</b> - e.g. for visitors/actions/bounce/goals, it could show a sparkline graph next to each of them showing data for the last 30 days (using a free charting API such as <a href=http://code.google.com/apis/charttools/index.html>Google Charts</a>).<br />
<li><b>Below this, show the top 30 items</b> for their top content that day, or if their widget is 4 panels wide and they have selected a popular data type (e.g. searches) to display in the extra space, then show that type by default instead. And have a menu either way that lets them choose a different type to display (e.g. change from top content to top searches). Obviously, all 30 items won't fit on one screen, so the window should be scrollable, and have a next page button at the bottom, so they can view 31-60, etc.<br />
<li><b>Date range picker</b> to view data for more than just today (only in this view though, not for the widget itself, which should always default to today)<br />
</ul><br />
<li>User can add multiple widgets to their desktop, one for each site.<br />
<br />
<li>This needs to be compatible with at least Android 2.0 through 2.2. And if it's not too difficult, 1.5 and 1.6 as well.<br />
<br />
<li>We need to be the owner of this software, and hence you will need to provide the source code to us so we can improve it ourselves in the future or have someone else do so for us if you are not available for future development. We will happily credit you as the original developer, but we need to own the product, which also means that in the Android Market, it will be listed as a product of our company, <a href=http://roxr.net>Roxr Software Ltd</a>. (And of course, this widget will be totally free for all of our users). This doesn't mean we're going to take the code from you - you can keep it for yourself to base other projects on (except for a competing analytics service - we'd have a problem with that).<br />
<br />
<li><img class=fr ml20 mb20 src=http://static.getclicky.com/media/screenshots/android-widgets.gif>We have very high standards with regards to quality and aesthetics. This needs to be a very solid app, and it needs to look so good that our users will want to eat it. To give you an idea of what we like, we really dig the finance widgets that Google offers (see screenshot to the right). We like subtle transparency and shading of the background, and the shadow/transparency on the edges, which makes the widget feels like it's in the desktop. Having a shadow underneath the widget, to make it feel like it's on instead of in the desktop, would be fine too.<br />
<br />
<li>We of course have a very thorough <a href=http://getclicky.com/help/api>stats API</a> already, that you will be using to get all of the data that will be displayed in the widget.<br />
</ul><br />
<br />
<h3>Interested?</h3>If you've got what it takes, email <a href=mailto:sean@getclicky.com>sean@getclicky.com</a> with the subject line Android widget. Or if you know someone who may be eligible, send them a link to this post.<br />
<br />
In your email, tell us what Android applications and/or widgets you have developed. You <i>must</i> have Android development experience, and you'll get super bonus points if you have created a widget. And super <i>mega</i> bonus points if you are able to start immediately and can devote at least 20 hours a week to development - we'd like to have this released within 2 months.<br />
<br />
We will pay you $1,000 up front, an additional $1,000 once a beta version is ready for us to play with, and the rest upon completion of the product. We prefer to pay with Paypal to keep things simple and fast, but we can pay by check if you prefer.<br />
<br />
Lastly, we are open to negotiation on the price. We think this will be about 100 hours of work, so it's equivalent to $50/hour or a $100K/year job. But if you think otherwise, when you email us, tell us your price.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=4xBFfFEA7ow:otbulBaxk0c:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=4xBFfFEA7ow:otbulBaxk0c:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=4xBFfFEA7ow:otbulBaxk0c:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=4xBFfFEA7ow:otbulBaxk0c:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=4xBFfFEA7ow:otbulBaxk0c:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/4xBFfFEA7ow" height="1" width="1"/>";s:7:"pubdate";s:31:"Thu, 01 Jul 2010 14:27:43 -0800";s:5:"bonus";s:10:"1278019663";s:10:"feedburner";a:1:{s:8:"origlink";s:64:"http://getclicky.com/blog/221/5000-for-an-android-desktop-widget";}s:7:"summary";s:8066:"<img class=fr ml20 mb20 src=http://static.getclicky.com/media/screenshots/android-pandora.png><b class=red>JULY 6 UPDATE: We have a good pool of developers to choose from at this time, so we are no longer accepting applicants for this project. Thank you for all of the interest!</b><br />
<br />
We're very much in love with Android and would like nothing more than to have a desktop widget to always have <a href=http://getclicky.com/demo>our stats</a> available at a quick glance. If you're not familiar with Android widgets, they're basically apps that run on your desktop alongside your icons. For example, on the right hand side is a screenshot of the Pandora widget - you can control the entire app without actually being inside the app.<br />
<br />
We really dig this functionality and are looking for something similar for Clicky so you can always have your stats right in front of you. I personally am interested in exploring Android development in the future because I believe very strongly in this operating system, but I don't know Java and it would probably take me several months of full time development to get something like this up and running - time I don't currently have.<br />
<br />
<h3>What the widget should do</h3><ul><li>When user adds the widget to their desktop:<br />
<ul><li><b>Four sizes to choose from in the widget menu</b> - 2x1, 4x1, 2x2, and 4x2. We wish the widget size was definable at run time but it's not so we'll have to pollute the widget menu with four sizes :(<br />
<li><b>If they are adding this widget for the first time</b>, you need to ask for their credentials, which you send to an API to grab their list of sites. You save these credentials locally on the phone so if the user adds more than one widget, they don't have to re-enter their credentials. (Note to users concerned with privacy - we're inventing a new version of OAuth called Simple OAuth that will protect your password and let you revoke access to services as needed, without having to change your password - more details on that later). Once the credentials have been verified, the next screen lets them select all of the following options <i><u>on one screen:</u></i><br />
<li><b>The web site</b> they want the widget to display stats for.<br />
<li><b>Refresh interval</b> (5m, 15m, 30m, 1h, 2h, 3h, 4h) (Note: when device is sleeping, the data should not be refreshed. It should only be refreshed upon wake, or while the device is in use).<br />
<li><b>Widgets 1 panel high</b> show site name at top, then visitors and actions below that for today (including trend percentages for each item). <b>If it's 2 panels high</b>, also show bounce rate and goals/revenue (if they have goals setup). Use icons rather than text to differentiate these data types, to save space (if you're not familiar with Clicky, see our <a href=http://getclicky.com/demo>demo</a> to see the icons we use).<br />
<li><b>If the widget is 4 panels wide</b> (4x1 or 4x2), they can one choose additional piece of data to display:<br />
<ul><li>Additional dates for the default data (e.g. column 2 could show yesterday or last 7 days for visitors/actions/etc)<br />
<li>Popular data types (e.g. top searches, top goals, etc),<br />
<li>Graph of hourly data for visitors or actions for today, or graph of visitors or actions for the last 30 days<br />
</ul></ul><br />
<li>Clicking the widget opens up a full screen window:<br />
<ul><li><b>Shows same data but with more detail</b> - e.g. for visitors/actions/bounce/goals, it could show a sparkline graph next to each of them showing data for the last 30 days (using a free charting API such as <a href=http://code.google.com/apis/charttools/index.html>Google Charts</a>).<br />
<li><b>Below this, show the top 30 items</b> for their top content that day, or if their widget is 4 panels wide and they have selected a popular data type (e.g. searches) to display in the extra space, then show that type by default instead. And have a menu either way that lets them choose a different type to display (e.g. change from top content to top searches). Obviously, all 30 items won't fit on one screen, so the window should be scrollable, and have a next page button at the bottom, so they can view 31-60, etc.<br />
<li><b>Date range picker</b> to view data for more than just today (only in this view though, not for the widget itself, which should always default to today)<br />
</ul><br />
<li>User can add multiple widgets to their desktop, one for each site.<br />
<br />
<li>This needs to be compatible with at least Android 2.0 through 2.2. And if it's not too difficult, 1.5 and 1.6 as well.<br />
<br />
<li>We need to be the owner of this software, and hence you will need to provide the source code to us so we can improve it ourselves in the future or have someone else do so for us if you are not available for future development. We will happily credit you as the original developer, but we need to own the product, which also means that in the Android Market, it will be listed as a product of our company, <a href=http://roxr.net>Roxr Software Ltd</a>. (And of course, this widget will be totally free for all of our users). This doesn't mean we're going to take the code from you - you can keep it for yourself to base other projects on (except for a competing analytics service - we'd have a problem with that).<br />
<br />
<li><img class=fr ml20 mb20 src=http://static.getclicky.com/media/screenshots/android-widgets.gif>We have very high standards with regards to quality and aesthetics. This needs to be a very solid app, and it needs to look so good that our users will want to eat it. To give you an idea of what we like, we really dig the finance widgets that Google offers (see screenshot to the right). We like subtle transparency and shading of the background, and the shadow/transparency on the edges, which makes the widget feels like it's in the desktop. Having a shadow underneath the widget, to make it feel like it's on instead of in the desktop, would be fine too.<br />
<br />
<li>We of course have a very thorough <a href=http://getclicky.com/help/api>stats API</a> already, that you will be using to get all of the data that will be displayed in the widget.<br />
</ul><br />
<br />
<h3>Interested?</h3>If you've got what it takes, email <a href=mailto:sean@getclicky.com>sean@getclicky.com</a> with the subject line Android widget. Or if you know someone who may be eligible, send them a link to this post.<br />
<br />
In your email, tell us what Android applications and/or widgets you have developed. You <i>must</i> have Android development experience, and you'll get super bonus points if you have created a widget. And super <i>mega</i> bonus points if you are able to start immediately and can devote at least 20 hours a week to development - we'd like to have this released within 2 months.<br />
<br />
We will pay you $1,000 up front, an additional $1,000 once a beta version is ready for us to play with, and the rest upon completion of the product. We prefer to pay with Paypal to keep things simple and fast, but we can pay by check if you prefer.<br />
<br />
Lastly, we are open to negotiation on the price. We think this will be about 100 hours of work, so it's equivalent to $50/hour or a $100K/year job. But if you think otherwise, when you email us, tell us your price.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=4xBFfFEA7ow:otbulBaxk0c:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=4xBFfFEA7ow:otbulBaxk0c:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=4xBFfFEA7ow:otbulBaxk0c:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=4xBFfFEA7ow:otbulBaxk0c:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=4xBFfFEA7ow:otbulBaxk0c:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/4xBFfFEA7ow" height="1" width="1"/>";}i:30;a:9:{s:5:"title";s:31:"New feature: Sub-user accounts!";s:4:"link";s:85:"http://feedproxy.google.com/~r/getclicky/~3/43LG_NnoqOs/new-feature-sub-user-accounts";s:8:"comments";s:59:"http://getclicky.com/blog/220/new-feature-sub-user-accounts";s:4:"guid";s:59:"http://getclicky.com/blog/220/new-feature-sub-user-accounts";s:11:"description";s:2424:"<img class=fr ml20 mb10 src=http://static.getclicky.com/media/screenshots/201006-sub-users.gif>On your <a href=http://getclicky.com/user/>user homepage</a>, you may notice a new option to Manage users. What is this? Oh, only about the most requested feature of all time.<br />
<br />
Anyone with a Pro or higher account can now create additional user accounts that can be assigned read-only or administrative access to one or more of your existing sites. This is great way to let your clients login to our service and only be able to view the stats they should have access to, without having to share your entire account with them. Sub-user admins have full control over a site, including changing preferences and setting up goals, campaigns, etc. The only thing a sub-user admin can't do is delete the site itself.<br />
<br />
There are limits though, because we don't want to cannibalize our <a href=http://getclicky.com/whitelabel/>white label</a> service. The white label service has always had this feature, but with the white label, there are no limits with how many users you can create (not to mention, you can fully rebrand the service as your own!). So we had to create some limits here.<br />
<br />
Pro accounts can create up to 3 additional users. Super Pro and Custom accounts can create up to 7 users. Most of our users are Pro, so if you need more than 3 users, please <a href=http://getclicky.com/user/upgrade>upgrade</a> to Super Pro, and if you need more than 7, please consider our <a href=http://getclicky.com/whitelabel/>white label</a> service.<br />
<br />
We've gotten countless requests for this over the years and finally decided it was about time we added it to the standard offering. Enjoy!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=43LG_NnoqOs:rzfpuI26rIY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=43LG_NnoqOs:rzfpuI26rIY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=43LG_NnoqOs:rzfpuI26rIY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=43LG_NnoqOs:rzfpuI26rIY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=43LG_NnoqOs:rzfpuI26rIY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/43LG_NnoqOs" height="1" width="1"/>";s:7:"pubdate";s:31:"Thu, 24 Jun 2010 17:56:53 -0800";s:5:"bonus";s:10:"1277427413";s:10:"feedburner";a:1:{s:8:"origlink";s:59:"http://getclicky.com/blog/220/new-feature-sub-user-accounts";}s:7:"summary";s:2424:"<img class=fr ml20 mb10 src=http://static.getclicky.com/media/screenshots/201006-sub-users.gif>On your <a href=http://getclicky.com/user/>user homepage</a>, you may notice a new option to Manage users. What is this? Oh, only about the most requested feature of all time.<br />
<br />
Anyone with a Pro or higher account can now create additional user accounts that can be assigned read-only or administrative access to one or more of your existing sites. This is great way to let your clients login to our service and only be able to view the stats they should have access to, without having to share your entire account with them. Sub-user admins have full control over a site, including changing preferences and setting up goals, campaigns, etc. The only thing a sub-user admin can't do is delete the site itself.<br />
<br />
There are limits though, because we don't want to cannibalize our <a href=http://getclicky.com/whitelabel/>white label</a> service. The white label service has always had this feature, but with the white label, there are no limits with how many users you can create (not to mention, you can fully rebrand the service as your own!). So we had to create some limits here.<br />
<br />
Pro accounts can create up to 3 additional users. Super Pro and Custom accounts can create up to 7 users. Most of our users are Pro, so if you need more than 3 users, please <a href=http://getclicky.com/user/upgrade>upgrade</a> to Super Pro, and if you need more than 7, please consider our <a href=http://getclicky.com/whitelabel/>white label</a> service.<br />
<br />
We've gotten countless requests for this over the years and finally decided it was about time we added it to the standard offering. Enjoy!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=43LG_NnoqOs:rzfpuI26rIY:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=43LG_NnoqOs:rzfpuI26rIY:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=43LG_NnoqOs:rzfpuI26rIY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=43LG_NnoqOs:rzfpuI26rIY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=43LG_NnoqOs:rzfpuI26rIY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/43LG_NnoqOs" height="1" width="1"/>";}i:31;a:9:{s:5:"title";s:31:"How we use Gmail as a help desk";s:4:"link";s:87:"http://feedproxy.google.com/~r/getclicky/~3/e8LT2gYVcZo/how-we-use-gmail-as-a-help-desk";s:8:"comments";s:61:"http://getclicky.com/blog/219/how-we-use-gmail-as-a-help-desk";s:4:"guid";s:61:"http://getclicky.com/blog/219/how-we-use-gmail-as-a-help-desk";s:11:"description";s:6051:"This is a bit off topic, but I thought some of you might find it interesting.<br />
<br />
We get a lot of emails. For the past three and a half years, my partner Noah and I have been forwarding our getclicky.com emails to our personal Gmail accounts (because we love Gmail). This works good, but the problem is that a lot of the time, a user will email the wrong person. So then we have to forward emails to each other, and sometimes back again, and it becomes a bit of a mess. It also makes it harder to know if a person has emailed us before about something, because maybe he emailed Noah last time, but me the next time.<br />
<br />
As we grow, so does our volume of email. If you saw how much email we get, you'd cry. Earlier this month we decided we needed to create a centralized help desk, so everything for both of us was in one place. We looked at Zendesk and its <a href=http://alternativeto.net/desktop/zendesk/?platform=online>alternatives</a>, and frankly, we found most of them rather appalling. They were just so ridiculously crammed with features and confusing interfaces, not to mention ridiculously priced, I just couldn't see myself using any of them.<br />
<br />
So we decided to just create a new Gmail account that we can both use, and forward all @getclicky.com emails to it. (Note: We of course use Gmail's send email as feature, so the emails we send are from xyz@getclicky.com, not clicky@gmail.com. <b>UPDATE:</b> Ok, geez, we'll move to the apps edition so no forwarding is involved! :P). So far after about a month, it's been great. With the help of a few labs features, we can do everything we need Gmail to do to be a great help desk. I was already using these features with my personal Gmail account, but now that we have a combined one and can use all of these features together, it's great.<br />
<br />
<ul><li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/gmail-helpdesk/labels.gif><b>Labels</b> - To assign emails to one of us or the other, we've just created two labels - Sean and Noah. All emails to sean@ or noah@ are automatically assigned the appropriate label, but emails to support@ are not. Regardless of whether or not an email comes in with the right label, we can quickly assign or reassign each one to the correct person without having to forward emails. And if it's reassigned to the other person later, that person has the full history of the conversation available.<br />
<br />
<li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/gmail-helpdesk/replies.gif><b>Canned replies</b> - This Labs feature lets you save canned replies, so you can quickly respond to certain emails that you tend to get a lot. Most replies you receive from us are written just for you with plenty of TLC, but there are some emails we just get too often that we have to use this feature. (Except for the labels screenshot above, these are all taken from the Gmail Labs page. I just noticed this one has RTFM as one of the examples. That made me laugh ^_^)<br />
<br />
<li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/gmail-helpdesk/superstars.gif><b>Super Stars</b> - This Labs feature lets you have more than one color of star. We use three stars - yellow, red, and blue. The standard yellow star just means we have read the email but still need to reply. A red star means the same thing, but that it's high priority. A blue star means we are awaiting a reply, and we want to follow up if we haven't heard anything within a few days. Flagging it lets us easily find it later.<br />
<br />
<li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/gmail-helpdesk/translate.gif><b>Message translation</b> - This Labs feature automatically translates emails in foreign languages into your native tongue. We have a lot of international users, so we occasionally get an email in a foreign language. Of course, we do not speak these languages, so this is very handy.<br />
<br />
<li><b>Help desk on the go</b> - We both have Android phones (Motorola Droid FTW!), and the Gmail integration with Android is super great. The Labs features don't work with it, but at the very least we can read, reply, and assign emails to each other as needed, no matter where we are.<br />
</ul><br />
<br />
The only thing you can't do is have ticket numbers, but unless you do support by telephone, this should not be a big deal at all. And ticket numbers are just way too corporate anyways. If you want to give the vibe that you're a hip startup, you won't need them.<br />
<br />
One last concern is that if you have a large support department (more than 5 people or so), this probably isn't the best solution. It would probably just be a bit too chaotic. But if your support department is that big, you are probably living the corporate life already, so why are you even reading this? :P<br />
<br />
Best of all? Gmail is totally free. :) When you see the pricing of the help desk services out there, you might flip a lid. The pricing is just pure insanity. Gmail is the best email service ever created in our humble opinion, and since it's free and can be heavily customized, it can make a great help desk for your company. And if you already use it for your help desk, let us know what features you use to make your life easier.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=e8LT2gYVcZo:0DQuXC5GDRg:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=e8LT2gYVcZo:0DQuXC5GDRg:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=e8LT2gYVcZo:0DQuXC5GDRg:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=e8LT2gYVcZo:0DQuXC5GDRg:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=e8LT2gYVcZo:0DQuXC5GDRg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/e8LT2gYVcZo" height="1" width="1"/>";s:7:"pubdate";s:31:"Wed, 23 Jun 2010 00:53:11 -0800";s:5:"bonus";s:10:"1277279591";s:10:"feedburner";a:1:{s:8:"origlink";s:61:"http://getclicky.com/blog/219/how-we-use-gmail-as-a-help-desk";}s:7:"summary";s:6051:"This is a bit off topic, but I thought some of you might find it interesting.<br />
<br />
We get a lot of emails. For the past three and a half years, my partner Noah and I have been forwarding our getclicky.com emails to our personal Gmail accounts (because we love Gmail). This works good, but the problem is that a lot of the time, a user will email the wrong person. So then we have to forward emails to each other, and sometimes back again, and it becomes a bit of a mess. It also makes it harder to know if a person has emailed us before about something, because maybe he emailed Noah last time, but me the next time.<br />
<br />
As we grow, so does our volume of email. If you saw how much email we get, you'd cry. Earlier this month we decided we needed to create a centralized help desk, so everything for both of us was in one place. We looked at Zendesk and its <a href=http://alternativeto.net/desktop/zendesk/?platform=online>alternatives</a>, and frankly, we found most of them rather appalling. They were just so ridiculously crammed with features and confusing interfaces, not to mention ridiculously priced, I just couldn't see myself using any of them.<br />
<br />
So we decided to just create a new Gmail account that we can both use, and forward all @getclicky.com emails to it. (Note: We of course use Gmail's send email as feature, so the emails we send are from xyz@getclicky.com, not clicky@gmail.com. <b>UPDATE:</b> Ok, geez, we'll move to the apps edition so no forwarding is involved! :P). So far after about a month, it's been great. With the help of a few labs features, we can do everything we need Gmail to do to be a great help desk. I was already using these features with my personal Gmail account, but now that we have a combined one and can use all of these features together, it's great.<br />
<br />
<ul><li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/gmail-helpdesk/labels.gif><b>Labels</b> - To assign emails to one of us or the other, we've just created two labels - Sean and Noah. All emails to sean@ or noah@ are automatically assigned the appropriate label, but emails to support@ are not. Regardless of whether or not an email comes in with the right label, we can quickly assign or reassign each one to the correct person without having to forward emails. And if it's reassigned to the other person later, that person has the full history of the conversation available.<br />
<br />
<li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/gmail-helpdesk/replies.gif><b>Canned replies</b> - This Labs feature lets you save canned replies, so you can quickly respond to certain emails that you tend to get a lot. Most replies you receive from us are written just for you with plenty of TLC, but there are some emails we just get too often that we have to use this feature. (Except for the labels screenshot above, these are all taken from the Gmail Labs page. I just noticed this one has RTFM as one of the examples. That made me laugh ^_^)<br />
<br />
<li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/gmail-helpdesk/superstars.gif><b>Super Stars</b> - This Labs feature lets you have more than one color of star. We use three stars - yellow, red, and blue. The standard yellow star just means we have read the email but still need to reply. A red star means the same thing, but that it's high priority. A blue star means we are awaiting a reply, and we want to follow up if we haven't heard anything within a few days. Flagging it lets us easily find it later.<br />
<br />
<li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/gmail-helpdesk/translate.gif><b>Message translation</b> - This Labs feature automatically translates emails in foreign languages into your native tongue. We have a lot of international users, so we occasionally get an email in a foreign language. Of course, we do not speak these languages, so this is very handy.<br />
<br />
<li><b>Help desk on the go</b> - We both have Android phones (Motorola Droid FTW!), and the Gmail integration with Android is super great. The Labs features don't work with it, but at the very least we can read, reply, and assign emails to each other as needed, no matter where we are.<br />
</ul><br />
<br />
The only thing you can't do is have ticket numbers, but unless you do support by telephone, this should not be a big deal at all. And ticket numbers are just way too corporate anyways. If you want to give the vibe that you're a hip startup, you won't need them.<br />
<br />
One last concern is that if you have a large support department (more than 5 people or so), this probably isn't the best solution. It would probably just be a bit too chaotic. But if your support department is that big, you are probably living the corporate life already, so why are you even reading this? :P<br />
<br />
Best of all? Gmail is totally free. :) When you see the pricing of the help desk services out there, you might flip a lid. The pricing is just pure insanity. Gmail is the best email service ever created in our humble opinion, and since it's free and can be heavily customized, it can make a great help desk for your company. And if you already use it for your help desk, let us know what features you use to make your life easier.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=e8LT2gYVcZo:0DQuXC5GDRg:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=e8LT2gYVcZo:0DQuXC5GDRg:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=e8LT2gYVcZo:0DQuXC5GDRg:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=e8LT2gYVcZo:0DQuXC5GDRg:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=e8LT2gYVcZo:0DQuXC5GDRg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/e8LT2gYVcZo" height="1" width="1"/>";}i:32;a:9:{s:5:"title";s:88:"You can now change the default data type for each dashboard module, amongst other things";s:4:"link";s:143:"http://feedproxy.google.com/~r/getclicky/~3/Q6VrN0ZfzBg/you-can-now-change-the-default-data-type-for-each-dashboard-module-amongst-other-things";s:8:"comments";s:117:"http://getclicky.com/blog/218/you-can-now-change-the-default-data-type-for-each-dashboard-module-amongst-other-things";s:4:"guid";s:117:"http://getclicky.com/blog/218/you-can-now-change-the-default-data-type-for-each-dashboard-module-amongst-other-things";s:11:"description";s:5447:"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.<br />
<br />
<ul><li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/201006-dashboard-types.gif><b>Change the default type for any dashboard module</b> - 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!<br />
<br />
<li><b>If your page titles change, we'll update them too</b> - 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).<br />
<br />
<li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/201006-dashboard-hourly.gif><b>Hourly graphs for today stop at the current hour</b> - 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.<br />
<br />
<li><b>More translations</b> - 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, <a href=http://getclicky.com/translate/>click here</a>!<br />
<br />
<li><b>Larger date ranges</b> - 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 <a href=http://getclicky.com/blog/211/heres-what-new>the update</a> 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.<br />
<br />
<li><b>Disable pinging in our tracking code</b> - 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 <a href=http://getclicky.com/help/customization#ping_disable>the option</a>.<br />
<br />
<li><b>Complex IP range queries</b> - 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 <a href=http://getclicky.com/help/api#ip_address>here</a>.<br />
<br />
<li><b>Time offset for visitors and actions in the API</b> - 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 <a href=http://getclicky.com/help/api#time_offset>this option</a>.<br />
</ul><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=Q6VrN0ZfzBg:OuEhuC-X2Po:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Q6VrN0ZfzBg:OuEhuC-X2Po:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Q6VrN0ZfzBg:OuEhuC-X2Po:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Q6VrN0ZfzBg:OuEhuC-X2Po:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Q6VrN0ZfzBg:OuEhuC-X2Po:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/Q6VrN0ZfzBg" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 14 Jun 2010 21:14:14 -0800";s:5:"bonus";s:10:"1276575254";s:10:"feedburner";a:1:{s:8:"origlink";s:117:"http://getclicky.com/blog/218/you-can-now-change-the-default-data-type-for-each-dashboard-module-amongst-other-things";}s:7:"summary";s:5447:"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.<br />
<br />
<ul><li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/201006-dashboard-types.gif><b>Change the default type for any dashboard module</b> - 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!<br />
<br />
<li><b>If your page titles change, we'll update them too</b> - 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).<br />
<br />
<li><img class=fr ml10 mb10 src=http://static.getclicky.com/media/screenshots/201006-dashboard-hourly.gif><b>Hourly graphs for today stop at the current hour</b> - 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.<br />
<br />
<li><b>More translations</b> - 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, <a href=http://getclicky.com/translate/>click here</a>!<br />
<br />
<li><b>Larger date ranges</b> - 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 <a href=http://getclicky.com/blog/211/heres-what-new>the update</a> 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.<br />
<br />
<li><b>Disable pinging in our tracking code</b> - 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 <a href=http://getclicky.com/help/customization#ping_disable>the option</a>.<br />
<br />
<li><b>Complex IP range queries</b> - 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 <a href=http://getclicky.com/help/api#ip_address>here</a>.<br />
<br />
<li><b>Time offset for visitors and actions in the API</b> - 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 <a href=http://getclicky.com/help/api#time_offset>this option</a>.<br />
</ul><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=Q6VrN0ZfzBg:OuEhuC-X2Po:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Q6VrN0ZfzBg:OuEhuC-X2Po:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Q6VrN0ZfzBg:OuEhuC-X2Po:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=Q6VrN0ZfzBg:OuEhuC-X2Po:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=Q6VrN0ZfzBg:OuEhuC-X2Po:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/Q6VrN0ZfzBg" height="1" width="1"/>";}i:33;a:9:{s:5:"title";s:18:"bit.ly integration";s:4:"link";s:73:"http://feedproxy.google.com/~r/getclicky/~3/2IVPBhn0VGI/bitly-integration";s:8:"comments";s:47:"http://getclicky.com/blog/217/bitly-integration";s:4:"guid";s:47:"http://getclicky.com/blog/217/bitly-integration";s:11:"description";s:3719:"One of the best parts of owning a small company is being able to act fast. There's no red tape or clueless management to deal with - you want something done, BAM, it's done! A perfect example is when Google Chrome was released. Within several hours of the announcement, <a href=http://getclicky.com/blog/136/google-chrome-added-to-browser-detection>we added support for it</a> to our web browser reporting. If I remember correctly, it took Google Analytics several weeks to get Chrome detection integrated, which we found amusing (ya know, since they're made by the same company and all).<br />
<br />
Anyways, I was recently reading a <a href=http://techcrunch.com/2010/06/03/bitly-pro-data/>story</a> on TechCrunch about bit.ly, and it briefly mentioned at the bottom about how WebTrends (a fellow Portland analytics firm) announced a partnership with <a href=http://bit.ly>bit.ly</a> to integrate bit.ly's analytics into their reports later this summer. I didn't know bit.ly had a stats API (because I use <a href=http://clicky.me>clicky.me</a>, of course!), so I jumped on the opportunity. Two days later, it's part of Clicky.<br />
<br />
bit.ly's existing API only provides very basic data unfortunately - the only thing you can access is the total number of clicks that your last 15 shortened URLs have had. I imagine this partnership with WebTrends will provide them with access to <i>all</i> of the analytics that bit.ly gives you for a link, when viewed on their web site (geographic data, referrers, etc - <a href=http://bit.ly/bOCM9F+>here's an example</a>), which we don't think is fair really. Their API should be open to everyone, so we're a bit disappointed there.<br />
<br />
But no matter. We think you'll still like this integration, and we've made it extremely easy to access the full bit.ly report for any of your links simply by clicking on the link. <a href=http://getclicky.com/stats/links-bitly?site_id=32020>Try it out in our demo account</a>.<br />
<br />
<h4>How to set it up</h4>This feature does require a Pro or higher account (<a href=http://getclicky.com/user/upgrade>upgrade here if necessary</a>). For any site you want to add this to, just go to your site preferences main page, click preferences again (near the top), and then click the advanced settings link and enter your bit.ly username where requested.<br />
<br />
<h4>Available reports</h4>This is available under the Links report, by clicking the new bit.ly sub-tab. It has also been added to the Short URLs dashboard module, and to our <a href=http://i.getclicky.com>iPhone web analytics</a>. We wanted to add it the API too but there's a bug with accessing third party data via the API at the moment that we still need to fix.<br />
<br />
Enjoy!<br />
<br />
<img class=fr src=http://static.getclicky.com/media/screenshots/201006-bitly-dashboard.gif> <img src=http://static.getclicky.com/media/screenshots/201006-bitly-iphone.gif><br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201006-bitly.gif><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=2IVPBhn0VGI:Bls1IBGoV0k:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=2IVPBhn0VGI:Bls1IBGoV0k:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=2IVPBhn0VGI:Bls1IBGoV0k:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=2IVPBhn0VGI:Bls1IBGoV0k:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=2IVPBhn0VGI:Bls1IBGoV0k:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/2IVPBhn0VGI" height="1" width="1"/>";s:7:"pubdate";s:31:"Tue, 08 Jun 2010 15:59:14 -0800";s:5:"bonus";s:10:"1276037954";s:10:"feedburner";a:1:{s:8:"origlink";s:47:"http://getclicky.com/blog/217/bitly-integration";}s:7:"summary";s:3719:"One of the best parts of owning a small company is being able to act fast. There's no red tape or clueless management to deal with - you want something done, BAM, it's done! A perfect example is when Google Chrome was released. Within several hours of the announcement, <a href=http://getclicky.com/blog/136/google-chrome-added-to-browser-detection>we added support for it</a> to our web browser reporting. If I remember correctly, it took Google Analytics several weeks to get Chrome detection integrated, which we found amusing (ya know, since they're made by the same company and all).<br />
<br />
Anyways, I was recently reading a <a href=http://techcrunch.com/2010/06/03/bitly-pro-data/>story</a> on TechCrunch about bit.ly, and it briefly mentioned at the bottom about how WebTrends (a fellow Portland analytics firm) announced a partnership with <a href=http://bit.ly>bit.ly</a> to integrate bit.ly's analytics into their reports later this summer. I didn't know bit.ly had a stats API (because I use <a href=http://clicky.me>clicky.me</a>, of course!), so I jumped on the opportunity. Two days later, it's part of Clicky.<br />
<br />
bit.ly's existing API only provides very basic data unfortunately - the only thing you can access is the total number of clicks that your last 15 shortened URLs have had. I imagine this partnership with WebTrends will provide them with access to <i>all</i> of the analytics that bit.ly gives you for a link, when viewed on their web site (geographic data, referrers, etc - <a href=http://bit.ly/bOCM9F+>here's an example</a>), which we don't think is fair really. Their API should be open to everyone, so we're a bit disappointed there.<br />
<br />
But no matter. We think you'll still like this integration, and we've made it extremely easy to access the full bit.ly report for any of your links simply by clicking on the link. <a href=http://getclicky.com/stats/links-bitly?site_id=32020>Try it out in our demo account</a>.<br />
<br />
<h4>How to set it up</h4>This feature does require a Pro or higher account (<a href=http://getclicky.com/user/upgrade>upgrade here if necessary</a>). For any site you want to add this to, just go to your site preferences main page, click preferences again (near the top), and then click the advanced settings link and enter your bit.ly username where requested.<br />
<br />
<h4>Available reports</h4>This is available under the Links report, by clicking the new bit.ly sub-tab. It has also been added to the Short URLs dashboard module, and to our <a href=http://i.getclicky.com>iPhone web analytics</a>. We wanted to add it the API too but there's a bug with accessing third party data via the API at the moment that we still need to fix.<br />
<br />
Enjoy!<br />
<br />
<img class=fr src=http://static.getclicky.com/media/screenshots/201006-bitly-dashboard.gif> <img src=http://static.getclicky.com/media/screenshots/201006-bitly-iphone.gif><br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201006-bitly.gif><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=2IVPBhn0VGI:Bls1IBGoV0k:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=2IVPBhn0VGI:Bls1IBGoV0k:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=2IVPBhn0VGI:Bls1IBGoV0k:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=2IVPBhn0VGI:Bls1IBGoV0k:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=2IVPBhn0VGI:Bls1IBGoV0k:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/2IVPBhn0VGI" height="1" width="1"/>";}i:34;a:9:{s:5:"title";s:31:"Say goodbye to search analytics";s:4:"link";s:87:"http://feedproxy.google.com/~r/getclicky/~3/a5ljLFTDBi0/say-goodbye-to-search-analytics";s:8:"comments";s:61:"http://getclicky.com/blog/216/say-goodbye-to-search-analytics";s:4:"guid";s:61:"http://getclicky.com/blog/216/say-goodbye-to-search-analytics";s:11:"description";s:4058:"Google just announced their new <a href=http://googleblog.blogspot.com/2010/05/search-more-securely-with-encrypted.html>secure search beta</a>, and <a href=http://duckduckgo.com/ rel=nofollow>DuckDuckGo</a> announced <a href=http://www.gabrielweinberg.com/blog/2010/05/duck-duck-go-searches-are-now-externally-anonymous.html rel=nofollow>similar measures</a>. DDG's are a bit more thorough, but the end result is the same - the search term is not passed through the referrer, and hence no analytics tool (not even a good old log analyzer) will have any idea of what a visitor searched for to reach your site.<br />
<br />
They both claim to do this in the name of privacy. Google's is a beta so it's off by default, and it doesn't explicitly say privacy <i>from webmasters</i>, but that is part of the end result. DDG, on the other hand, explicitly mentions not leaking your search terms, and this feature is enabled by default for all users - even over non-HTTPS connections. (Technical note: when you click a link on an HTTPS page, your browser does not send a referrer, which is why HTTPS search engines will result in secret searches that we can't see).<br />
<br />
Being able to search over HTTPS is probably a good thing for people in countries with vast censorship, such as China. I can understand offering this as an option that people can use. But I really hope Google never considers making this the default, because that would be very irritating for web masters - we would have no idea what people were searching for to get to our site, which is arguably the #1 reason to run analytics in the first place.<br />
<br />
My big problem is that DDG is hiding the search term from sites <i>by default</i>. That's not good for the internet at all, and I'm scared that Google may end up doing something similar (via HTTPS or not), and perhaps other search engines in the future.<br />
<br />
Part of the problem is that this gives users a false sense of security. Yes, someone snooping your connection won't be able to tell what you're searching for, but the sites you click through to will probably have a good idea, based on your landing page - not to mention they can also see their IP address and every page they have ever viewed on my site, ever. And yet somehow, not knowing this visitor's <i>specific</i> search term is protecting their privacy? Please. The only thing it does is make the life of a web master a much bigger pain in the ass than it was before.<br />
<br />
I'm taking time out of my amazing Hawaiian vacation to write this blog post because that's how much I care about this issue, and believe that it is not good for anyone. Of course, I wouldn't be surprised to learn that Google Analytics will somehow magically be able to track these secure searches. Wouldn't that be convenient for the likes of every other analytics service on the planet?<br />
<br />
This all seems <a href=http://getclicky.com/blog/150/googles-new-ajax-powered-search-results-breaks-search-keyword-tracking-for-everyone>very familiar</a>, doesn't it? Other search engines may start doing this too, but really, with 90% marketshare, Google is the only one that matters. So what can you do? Blog about it. Tweet. Complain. Let Google you know that you do not like this, and let DuckDuckGo and any other engine who does this in the future know the same.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=a5ljLFTDBi0:BPPvpF4FVbU:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=a5ljLFTDBi0:BPPvpF4FVbU:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=a5ljLFTDBi0:BPPvpF4FVbU:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=a5ljLFTDBi0:BPPvpF4FVbU:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=a5ljLFTDBi0:BPPvpF4FVbU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/a5ljLFTDBi0" height="1" width="1"/>";s:7:"pubdate";s:31:"Sat, 22 May 2010 10:25:06 -0800";s:5:"bonus";s:10:"1274549106";s:10:"feedburner";a:1:{s:8:"origlink";s:61:"http://getclicky.com/blog/216/say-goodbye-to-search-analytics";}s:7:"summary";s:4058:"Google just announced their new <a href=http://googleblog.blogspot.com/2010/05/search-more-securely-with-encrypted.html>secure search beta</a>, and <a href=http://duckduckgo.com/ rel=nofollow>DuckDuckGo</a> announced <a href=http://www.gabrielweinberg.com/blog/2010/05/duck-duck-go-searches-are-now-externally-anonymous.html rel=nofollow>similar measures</a>. DDG's are a bit more thorough, but the end result is the same - the search term is not passed through the referrer, and hence no analytics tool (not even a good old log analyzer) will have any idea of what a visitor searched for to reach your site.<br />
<br />
They both claim to do this in the name of privacy. Google's is a beta so it's off by default, and it doesn't explicitly say privacy <i>from webmasters</i>, but that is part of the end result. DDG, on the other hand, explicitly mentions not leaking your search terms, and this feature is enabled by default for all users - even over non-HTTPS connections. (Technical note: when you click a link on an HTTPS page, your browser does not send a referrer, which is why HTTPS search engines will result in secret searches that we can't see).<br />
<br />
Being able to search over HTTPS is probably a good thing for people in countries with vast censorship, such as China. I can understand offering this as an option that people can use. But I really hope Google never considers making this the default, because that would be very irritating for web masters - we would have no idea what people were searching for to get to our site, which is arguably the #1 reason to run analytics in the first place.<br />
<br />
My big problem is that DDG is hiding the search term from sites <i>by default</i>. That's not good for the internet at all, and I'm scared that Google may end up doing something similar (via HTTPS or not), and perhaps other search engines in the future.<br />
<br />
Part of the problem is that this gives users a false sense of security. Yes, someone snooping your connection won't be able to tell what you're searching for, but the sites you click through to will probably have a good idea, based on your landing page - not to mention they can also see their IP address and every page they have ever viewed on my site, ever. And yet somehow, not knowing this visitor's <i>specific</i> search term is protecting their privacy? Please. The only thing it does is make the life of a web master a much bigger pain in the ass than it was before.<br />
<br />
I'm taking time out of my amazing Hawaiian vacation to write this blog post because that's how much I care about this issue, and believe that it is not good for anyone. Of course, I wouldn't be surprised to learn that Google Analytics will somehow magically be able to track these secure searches. Wouldn't that be convenient for the likes of every other analytics service on the planet?<br />
<br />
This all seems <a href=http://getclicky.com/blog/150/googles-new-ajax-powered-search-results-breaks-search-keyword-tracking-for-everyone>very familiar</a>, doesn't it? Other search engines may start doing this too, but really, with 90% marketshare, Google is the only one that matters. So what can you do? Blog about it. Tweet. Complain. Let Google you know that you do not like this, and let DuckDuckGo and any other engine who does this in the future know the same.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=a5ljLFTDBi0:BPPvpF4FVbU:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=a5ljLFTDBi0:BPPvpF4FVbU:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=a5ljLFTDBi0:BPPvpF4FVbU:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=a5ljLFTDBi0:BPPvpF4FVbU:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=a5ljLFTDBi0:BPPvpF4FVbU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/a5ljLFTDBi0" height="1" width="1"/>";}i:35;a:9:{s:5:"title";s:22:"New engagement reports";s:4:"link";s:78:"http://feedproxy.google.com/~r/getclicky/~3/4EPH2hDuo4U/new-engagement-reports";s:8:"comments";s:52:"http://getclicky.com/blog/215/new-engagement-reports";s:4:"guid";s:52:"http://getclicky.com/blog/215/new-engagement-reports";s:11:"description";s:1890:"We have a couple of new reports for Pro and higher members. These break down your visitors' engagement levels to quite a bit of detail, both in terms of time on site as well as number of actions performed. The reports are quite self explanatory, as you can see from the screenshots below, so there's really not a whole lot to say here. We think these will be a big hit in particular with those of you who don't like our <a href=http://getclicky.com/blog/214/why-clickys-new-bounce-rate-is-the-best-in-the-biz>new bounce rate</a>, because part of this report basically shows you the old school bounce rate: the number of visitors who had only 1 action.<br />
<br />
This is available in a new dashboard module, as well as full reports with a bit more detail under the Visitors tab. We also added it to the iPhone web app. You can also get the data from the API. The <a href=http://getclicky.com/help/api>docs</a> have been updated with the new <i>type</i> values you will need to request.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201005-engagement-dashboard.gif><br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201005-engagement.gif><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=4EPH2hDuo4U:g7v9KfdiJ_o:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=4EPH2hDuo4U:g7v9KfdiJ_o:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=4EPH2hDuo4U:g7v9KfdiJ_o:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=4EPH2hDuo4U:g7v9KfdiJ_o:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=4EPH2hDuo4U:g7v9KfdiJ_o:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/4EPH2hDuo4U" height="1" width="1"/>";s:7:"pubdate";s:31:"Tue, 11 May 2010 21:32:51 -0800";s:5:"bonus";s:10:"1273638771";s:10:"feedburner";a:1:{s:8:"origlink";s:52:"http://getclicky.com/blog/215/new-engagement-reports";}s:7:"summary";s:1890:"We have a couple of new reports for Pro and higher members. These break down your visitors' engagement levels to quite a bit of detail, both in terms of time on site as well as number of actions performed. The reports are quite self explanatory, as you can see from the screenshots below, so there's really not a whole lot to say here. We think these will be a big hit in particular with those of you who don't like our <a href=http://getclicky.com/blog/214/why-clickys-new-bounce-rate-is-the-best-in-the-biz>new bounce rate</a>, because part of this report basically shows you the old school bounce rate: the number of visitors who had only 1 action.<br />
<br />
This is available in a new dashboard module, as well as full reports with a bit more detail under the Visitors tab. We also added it to the iPhone web app. You can also get the data from the API. The <a href=http://getclicky.com/help/api>docs</a> have been updated with the new <i>type</i> values you will need to request.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201005-engagement-dashboard.gif><br />
<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201005-engagement.gif><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=4EPH2hDuo4U:g7v9KfdiJ_o:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=4EPH2hDuo4U:g7v9KfdiJ_o:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=4EPH2hDuo4U:g7v9KfdiJ_o:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=4EPH2hDuo4U:g7v9KfdiJ_o:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=4EPH2hDuo4U:g7v9KfdiJ_o:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/4EPH2hDuo4U" height="1" width="1"/>";}i:36;a:9:{s:5:"title";s:51:"Why Clicky's new bounce rate is the best in the biz";s:4:"link";s:106:"http://feedproxy.google.com/~r/getclicky/~3/MH23Ers4aIk/why-clickys-new-bounce-rate-is-the-best-in-the-biz";s:8:"comments";s:80:"http://getclicky.com/blog/214/why-clickys-new-bounce-rate-is-the-best-in-the-biz";s:4:"guid";s:80:"http://getclicky.com/blog/214/why-clickys-new-bounce-rate-is-the-best-in-the-biz";s:11:"description";s:5716:"The standard definition of a bounce is a visitor who only viewed one page on your web site. Your web site's bounce rate is the percentage of visitors who bounced. This metric is supposed to give you a very generic estimate of your visitors' engagement level. If you have a high bounce rate, then your site is apparently very unengaging.<br />
<br />
But are single-pageview visits really the best way to define engagement? In the age of blogs and social media, we don't think so.<br />
<br />
Our <a href=http://getclicky.com/blog/211/heres-what-new>new release</a> added pinging support to our tracking code. This means that as a visitor to your site stays on a single page, they are still talking to our tracking servers, so we know they are still on your web site. This lets us determine how long a visitor is actually on your web site, even if they only have one pageview.<br />
<br />
There is a significant difference between a visitor with one pageview who spends less than 30 seconds on your site, and a visitor with one pageview who spends 5 minutes on your site. But no other analytics service will tell you about this difference - no matter how long any single-pageview visitors are on your site, they are all considered bounces. We think this is horribly broken and misleading, so we decided to redefine what a bounce is. <br />
<br />
<h4>How Clicky determines a bounce</h4>A visitor who has only one pageview, <i>and</i> who is on your site for less than 30 seconds is what we now consider a bounce. So any visitor who has more than one pageview, <i>or</i> any visitor who has only one pageview but is on your site for at least 30 seconds, is now what we consider engaged / not a bounce.<br />
<br />
Say you have a blog post that you have shared on a few social media networks like Facebook and Reddit, and you get 1000 visitors to it. Chances are that 95% of these visitors will only view the article that is being linked to - one pageview. Maybe half will read the whole article, half will read part of it, and a few will click through to your front page to see more. Any other analytics service would report a 95% bounce rate for these visitors. But a bounce is negative, so it makes it sound like only 5% of these visitors were engaged. But that's not true at all - half of them read the entire stinking article!<br />
<br />
Since Clicky now sends pings, we can measure how long each visitor is actually online. For the example above, Clicky would report a bounce rate closer to 50% for these visitors. This is a much more accurate representation of how many of these visitors actually bounced from your site, versus how many actually stayed online long enough to read what you had to say. Because of this, we think we now have the best bounce rate metric in the industry.<br />
<br />
<h4>Arguments against this change</h4>We've had some feedback that this new measurement is no good either, because there are lots of people who used tabbed browsing and open a bunch of tabs in the background, then go and read them later. This is true, but this is also more of a power user tactic. As long as less than 50% of users are doing this (and we think it's probably more like 10%), then our bounce rate is a much more accurate representation of engagement.<br />
<br />
Some people also suggested we make this a different metric altogether, such as engagement rate. We considered this, but ultimately we decided that the term bounce rate is just defined incorrectly in the first place. This shouldn't be a new metric - this is the way bounces should be defined, period. This is why it's called analytics - your traffic data is analyzed to help you make sense of it. Reporting that 90% of your visitors only had one pageview doesn't really tell you anything, but reporting that 50% of your visitors had one pageview <i>and</i> were online less than 30 seconds <i>does</i> tell you <i>a lot</i> about your web site's traffic.<br />
<br />
This doesn't mean we don't want to make it better though. We will probably add something that detects whether or not the page being viewed is in focus or not, and only do the pinging if it is actually being read. This will require a lot of testing, however. For example, a visitor opens a link to your site in the background, but doesn't actually read it until an hour later. If we don't ping until the page comes to the foreground, their session will have already expired so the pings won't register when they are processed on our end. Should we delay the page view log until the page comes to the foreground? That might work, but what if they move the window/tab to the background again and then come back to it another hour later? As you can see, it gets a bit complicated, so we're not going to change it until we have taken the time to determine the absolute best way to do it, and test the heck out of it.<br />
<br />
We'd still like to hear your feedback on this change of course, and what you think would make it better. So have at it in the comments.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=MH23Ers4aIk:cdxP0FtFmx0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=MH23Ers4aIk:cdxP0FtFmx0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=MH23Ers4aIk:cdxP0FtFmx0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=MH23Ers4aIk:cdxP0FtFmx0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=MH23Ers4aIk:cdxP0FtFmx0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/MH23Ers4aIk" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 26 Apr 2010 17:43:44 -0800";s:5:"bonus";s:10:"1272329024";s:10:"feedburner";a:1:{s:8:"origlink";s:80:"http://getclicky.com/blog/214/why-clickys-new-bounce-rate-is-the-best-in-the-biz";}s:7:"summary";s:5716:"The standard definition of a bounce is a visitor who only viewed one page on your web site. Your web site's bounce rate is the percentage of visitors who bounced. This metric is supposed to give you a very generic estimate of your visitors' engagement level. If you have a high bounce rate, then your site is apparently very unengaging.<br />
<br />
But are single-pageview visits really the best way to define engagement? In the age of blogs and social media, we don't think so.<br />
<br />
Our <a href=http://getclicky.com/blog/211/heres-what-new>new release</a> added pinging support to our tracking code. This means that as a visitor to your site stays on a single page, they are still talking to our tracking servers, so we know they are still on your web site. This lets us determine how long a visitor is actually on your web site, even if they only have one pageview.<br />
<br />
There is a significant difference between a visitor with one pageview who spends less than 30 seconds on your site, and a visitor with one pageview who spends 5 minutes on your site. But no other analytics service will tell you about this difference - no matter how long any single-pageview visitors are on your site, they are all considered bounces. We think this is horribly broken and misleading, so we decided to redefine what a bounce is. <br />
<br />
<h4>How Clicky determines a bounce</h4>A visitor who has only one pageview, <i>and</i> who is on your site for less than 30 seconds is what we now consider a bounce. So any visitor who has more than one pageview, <i>or</i> any visitor who has only one pageview but is on your site for at least 30 seconds, is now what we consider engaged / not a bounce.<br />
<br />
Say you have a blog post that you have shared on a few social media networks like Facebook and Reddit, and you get 1000 visitors to it. Chances are that 95% of these visitors will only view the article that is being linked to - one pageview. Maybe half will read the whole article, half will read part of it, and a few will click through to your front page to see more. Any other analytics service would report a 95% bounce rate for these visitors. But a bounce is negative, so it makes it sound like only 5% of these visitors were engaged. But that's not true at all - half of them read the entire stinking article!<br />
<br />
Since Clicky now sends pings, we can measure how long each visitor is actually online. For the example above, Clicky would report a bounce rate closer to 50% for these visitors. This is a much more accurate representation of how many of these visitors actually bounced from your site, versus how many actually stayed online long enough to read what you had to say. Because of this, we think we now have the best bounce rate metric in the industry.<br />
<br />
<h4>Arguments against this change</h4>We've had some feedback that this new measurement is no good either, because there are lots of people who used tabbed browsing and open a bunch of tabs in the background, then go and read them later. This is true, but this is also more of a power user tactic. As long as less than 50% of users are doing this (and we think it's probably more like 10%), then our bounce rate is a much more accurate representation of engagement.<br />
<br />
Some people also suggested we make this a different metric altogether, such as engagement rate. We considered this, but ultimately we decided that the term bounce rate is just defined incorrectly in the first place. This shouldn't be a new metric - this is the way bounces should be defined, period. This is why it's called analytics - your traffic data is analyzed to help you make sense of it. Reporting that 90% of your visitors only had one pageview doesn't really tell you anything, but reporting that 50% of your visitors had one pageview <i>and</i> were online less than 30 seconds <i>does</i> tell you <i>a lot</i> about your web site's traffic.<br />
<br />
This doesn't mean we don't want to make it better though. We will probably add something that detects whether or not the page being viewed is in focus or not, and only do the pinging if it is actually being read. This will require a lot of testing, however. For example, a visitor opens a link to your site in the background, but doesn't actually read it until an hour later. If we don't ping until the page comes to the foreground, their session will have already expired so the pings won't register when they are processed on our end. Should we delay the page view log until the page comes to the foreground? That might work, but what if they move the window/tab to the background again and then come back to it another hour later? As you can see, it gets a bit complicated, so we're not going to change it until we have taken the time to determine the absolute best way to do it, and test the heck out of it.<br />
<br />
We'd still like to hear your feedback on this change of course, and what you think would make it better. So have at it in the comments.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=MH23Ers4aIk:cdxP0FtFmx0:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=MH23Ers4aIk:cdxP0FtFmx0:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=MH23Ers4aIk:cdxP0FtFmx0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=MH23Ers4aIk:cdxP0FtFmx0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=MH23Ers4aIk:cdxP0FtFmx0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/MH23Ers4aIk" height="1" width="1"/>";}i:37;a:9:{s:5:"title";s:13:"What happened";s:4:"link";s:69:"http://feedproxy.google.com/~r/getclicky/~3/qCJD0HAxScQ/what-happened";s:8:"comments";s:43:"http://getclicky.com/blog/213/what-happened";s:4:"guid";s:43:"http://getclicky.com/blog/213/what-happened";s:11:"description";s:6030:"At approximately 6:30AM PST, our load balancers went offline. We have server monitoring tools that check our public IPs from a remote location every minute, so we were aware of the issue immediately. But it took a bit to figure out what was wrong and get them back online. Total downtime was about 90 minutes.<br />
<br />
At first we thought it was a network problem, as happens from time to time, but quickly noticed that a few public IPs we have that are not behind load balancers were fine. Ok, so it's the load balancers then? We have a double load balancer setup with automatic failover, so if one dies, the other takes over. We've tested this and it works great. But the chances of both dying at the same time? Impossible. But we couldn't access their public IPs. That was mildly depressing.<br />
<br />
But then we remembered they also have internal management IPs for admins to login to. We tunneled into the network and we were able to login to both load balancers, but after looking around a bit, there was nothing obviously wrong. They were online, they could see the internet, they just weren't passing traffic through to the servers behind them. After a bit of banging head upon keyboard, we checked the load balancer logs and saw some messages we'd never seen before, repeating over and over every minute:<br />
<br />
<i>Apr 19 07:09:11 : Machine rebooting too often - Passifying</i><br />
<br />
Passifying? Ok, well at least we see that the load balancers were rebooting themselves for some reason. So we did a manual reboot on one to see what would happen, because they weren't rebooting anymore - this message was simply being output every minute so that the admin looking at the log files could not miss it.<br />
<br />
Upon reboot, they would pass traffic through for about 20-30 seconds, then go boom. We managed to check the load stats before they went offline, and saw they were at 100%. Well that's not good.<br />
<br />
So the problem was that our load balancers were extremely overloaded. We just added <a href=http://getclicky.com/blog/211/heres-what-new>pinging</a> to our tracking code, which means visitors to your web sites talk to our tracking servers a lot more often than they used to. We obviously knew this would happen, so what we did was we actually activated our new tracking code last Tuesday for all sites, well before the actual release (Friday night), so we could see the effects that it had on our tracking servers. The load went up significantly, on both the load balancers and the tracking servers, but not enough to be concerned about. It was still a very manageable level.<br />
<br />
But at that point, our tracking servers were not actually logging the pings. They were receiving them, but they were discarded. That makes a difference. We made our full release on Friday night so it's been running over the weekend and were watching it very closely. Things seemed great. Of course, the weekend's traffic is quite a bit lower than during the week, particularly Monday. Monday is the biggest traffic day of the week for most sites, so it's the biggest day of the week for our service too.<br />
<br />
So Monday morning rolls around, and once most of the US is awake, the spike went up quite a bit higher than it did over the weekend. What happened was the load balancers were getting timeouts when talking to the tracking servers, which means they were keeping connections open for a lot longer than they normally would. This type of thing quickly spirals out of control, hence, the problem this morning.<br />
<br />
When our database servers process traffic every minute, they keep a log of what they just did - how many actions were processed, how many pings, how long the process took, etc. This is extremely useful data. So we took a peak at this and saw that pings were accounting for over 80% of traffic being processed. This means that the pinging functionality increased the hits to our tracking servers by 400%, overnight. That's a little more than we were expecting. We were expecting maybe a 200% increase at the most.<br />
<br />
In an effort to get things back online as quickly as possible, we changed the tracking code so that the total pings it will send are half as many, and the initial 15 second quick-check ping doesn't happen. After uploading that to the CDN, we rebooted the load balancers again and they came online and have stayed online since, with a load of about 65%. When viewing the database logs now, the pings are more inline with our initial expectations - about a 200% increase over normal traffic.<br />
<br />
We want to ping more often though, so we'll be tweaking all sorts of things over the course of the day and probably throughout the week, to get the most pings possible with the least amount of load on our servers. We'll post an update later to let you know how it's going. <br />
<br />
This is another one of <a href=http://getclicky.com/blog/199/cdn-update>those unfortunate cases</a> that aren't really testable until they're live. We knew there would be a big spike on our end, and we thought we had it under control, but we just didn't know quite how big it was going to be until the system was fully live and all of our sites were sending us Monday traffic. But for now, things are stable, and that's what's important.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=qCJD0HAxScQ:DNCRpyF73-E:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=qCJD0HAxScQ:DNCRpyF73-E:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=qCJD0HAxScQ:DNCRpyF73-E:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=qCJD0HAxScQ:DNCRpyF73-E:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=qCJD0HAxScQ:DNCRpyF73-E:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/qCJD0HAxScQ" height="1" width="1"/>";s:7:"pubdate";s:31:"Mon, 19 Apr 2010 09:27:54 -0800";s:5:"bonus";s:10:"1271694474";s:10:"feedburner";a:1:{s:8:"origlink";s:43:"http://getclicky.com/blog/213/what-happened";}s:7:"summary";s:6030:"At approximately 6:30AM PST, our load balancers went offline. We have server monitoring tools that check our public IPs from a remote location every minute, so we were aware of the issue immediately. But it took a bit to figure out what was wrong and get them back online. Total downtime was about 90 minutes.<br />
<br />
At first we thought it was a network problem, as happens from time to time, but quickly noticed that a few public IPs we have that are not behind load balancers were fine. Ok, so it's the load balancers then? We have a double load balancer setup with automatic failover, so if one dies, the other takes over. We've tested this and it works great. But the chances of both dying at the same time? Impossible. But we couldn't access their public IPs. That was mildly depressing.<br />
<br />
But then we remembered they also have internal management IPs for admins to login to. We tunneled into the network and we were able to login to both load balancers, but after looking around a bit, there was nothing obviously wrong. They were online, they could see the internet, they just weren't passing traffic through to the servers behind them. After a bit of banging head upon keyboard, we checked the load balancer logs and saw some messages we'd never seen before, repeating over and over every minute:<br />
<br />
<i>Apr 19 07:09:11 : Machine rebooting too often - Passifying</i><br />
<br />
Passifying? Ok, well at least we see that the load balancers were rebooting themselves for some reason. So we did a manual reboot on one to see what would happen, because they weren't rebooting anymore - this message was simply being output every minute so that the admin looking at the log files could not miss it.<br />
<br />
Upon reboot, they would pass traffic through for about 20-30 seconds, then go boom. We managed to check the load stats before they went offline, and saw they were at 100%. Well that's not good.<br />
<br />
So the problem was that our load balancers were extremely overloaded. We just added <a href=http://getclicky.com/blog/211/heres-what-new>pinging</a> to our tracking code, which means visitors to your web sites talk to our tracking servers a lot more often than they used to. We obviously knew this would happen, so what we did was we actually activated our new tracking code last Tuesday for all sites, well before the actual release (Friday night), so we could see the effects that it had on our tracking servers. The load went up significantly, on both the load balancers and the tracking servers, but not enough to be concerned about. It was still a very manageable level.<br />
<br />
But at that point, our tracking servers were not actually logging the pings. They were receiving them, but they were discarded. That makes a difference. We made our full release on Friday night so it's been running over the weekend and were watching it very closely. Things seemed great. Of course, the weekend's traffic is quite a bit lower than during the week, particularly Monday. Monday is the biggest traffic day of the week for most sites, so it's the biggest day of the week for our service too.<br />
<br />
So Monday morning rolls around, and once most of the US is awake, the spike went up quite a bit higher than it did over the weekend. What happened was the load balancers were getting timeouts when talking to the tracking servers, which means they were keeping connections open for a lot longer than they normally would. This type of thing quickly spirals out of control, hence, the problem this morning.<br />
<br />
When our database servers process traffic every minute, they keep a log of what they just did - how many actions were processed, how many pings, how long the process took, etc. This is extremely useful data. So we took a peak at this and saw that pings were accounting for over 80% of traffic being processed. This means that the pinging functionality increased the hits to our tracking servers by 400%, overnight. That's a little more than we were expecting. We were expecting maybe a 200% increase at the most.<br />
<br />
In an effort to get things back online as quickly as possible, we changed the tracking code so that the total pings it will send are half as many, and the initial 15 second quick-check ping doesn't happen. After uploading that to the CDN, we rebooted the load balancers again and they came online and have stayed online since, with a load of about 65%. When viewing the database logs now, the pings are more inline with our initial expectations - about a 200% increase over normal traffic.<br />
<br />
We want to ping more often though, so we'll be tweaking all sorts of things over the course of the day and probably throughout the week, to get the most pings possible with the least amount of load on our servers. We'll post an update later to let you know how it's going. <br />
<br />
This is another one of <a href=http://getclicky.com/blog/199/cdn-update>those unfortunate cases</a> that aren't really testable until they're live. We knew there would be a big spike on our end, and we thought we had it under control, but we just didn't know quite how big it was going to be until the system was fully live and all of our sites were sending us Monday traffic. But for now, things are stable, and that's what's important.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=qCJD0HAxScQ:DNCRpyF73-E:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=qCJD0HAxScQ:DNCRpyF73-E:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=qCJD0HAxScQ:DNCRpyF73-E:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=qCJD0HAxScQ:DNCRpyF73-E:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=qCJD0HAxScQ:DNCRpyF73-E:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/qCJD0HAxScQ" height="1" width="1"/>";}i:38;a:9:{s:5:"title";s:57:"Unexpected side effects of our recent changes to tracking";s:4:"link";s:113:"http://feedproxy.google.com/~r/getclicky/~3/DDf8G8y9An0/unexpected-side-effects-of-our-recent-changes-to-tracking";s:8:"comments";s:87:"http://getclicky.com/blog/212/unexpected-side-effects-of-our-recent-changes-to-tracking";s:4:"guid";s:87:"http://getclicky.com/blog/212/unexpected-side-effects-of-our-recent-changes-to-tracking";s:11:"description";s:4404:"There have been two side effects of our <a href=http://getclicky.com/blog/211/heres-what-new>recent changes to tracking</a> that we didn't really anticipate. This doesn't mean that something is broken, things just work differently now. We wanted to post about them here so you can understand what's going on.<br />
<br />
<h4>More visitors / less actions per visit</h4>You may have seen your daily visitor account increase substantially, but the number of actions remains the same. The main types of sites that are seeing this are those that have user accounts (e.g. people login to your site to do whatever it is they do on it).<br />
<br />
What's happening here? First, people tend to share their accounts with other people. We are seeing this big time on in our stats for getclicky.com, for example. We see multiple sessions from the same user account and the same IP address at around the same time, which previously would have been counted as the same session. Because we have cookies now, we are able to determine that these are in fact two unique users. We can tell because when we view these sessions, in almost all cases the computer details are different. One might have Windows XP and Firefox 3.0, the other Windows Vista and Internet Explorer. Since the old method was just using the IP address, they would have been clumped together into one visit. The new system seperates them into two unique sessions, as they should be, since they are occurring on two different computers.<br />
<br />
What about the other cases? Well, the same thing can also happen for one visitor using two different browsers on one computer to access our site. Since cookies are stored at the browser level, their cookie ID will be different in each browser used. This isn't really desirable here, but it's also quite rare. Not many people use multiple browsers at the same time. All other analytics services that use cookies will have the same problem. If you think about it though, it really is two different sessions, because the person is doing two seperate things in the two browsers.<br />
<br />
<h4>Visitors online in Spy is lower</h4>If you have a moderate traffic site (at least ~5,000 daily visitors), you may have noticed that when you load up Spy, the visitors online value is quite a bit lower than the one you see reported on the dashboard.<br />
<br />
The reason this is happening is because we only store the last X number of actions in the Spy cache for each site. Although we don't count pings as actions in your stats, the way that they are processed in the backend is the same. Since pings are now stored in that cache, when you first load Spy, the cache may not actually have all of the data for your visitors that are all online at that moment. So you will see lower number initially, but once Spy has been running for a few minutes, it should have a much more accurate number. We want to fix this and will probably increase the size of the cache, but we need to be careful about doing that.<br />
<br />
You also may be seeing lower numbers because you don't actually have as many visitors online at one time. As we explained in our last post, Spy now uses the pings to determine when visitors are truly online or not, rather than a generic 5 minute timeout that we were doing before. Now Spy will know within 1 minute of a visitor leaving your site that they have actually left (because the pings have stopped), instead of waiting 5 minutes to remove them. The end result here is that we remove visitors a lot quicker from Spy than we used to, so the value we report here might be lower than it used to be. But it's more accurate, and that's a good thing.<br />
<br />
Hope that helps.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=DDf8G8y9An0:bJvcvpc0xoE:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=DDf8G8y9An0:bJvcvpc0xoE:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=DDf8G8y9An0:bJvcvpc0xoE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=DDf8G8y9An0:bJvcvpc0xoE:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=DDf8G8y9An0:bJvcvpc0xoE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/DDf8G8y9An0" height="1" width="1"/>";s:7:"pubdate";s:31:"Sun, 18 Apr 2010 16:07:58 -0800";s:5:"bonus";s:10:"1271632078";s:10:"feedburner";a:1:{s:8:"origlink";s:87:"http://getclicky.com/blog/212/unexpected-side-effects-of-our-recent-changes-to-tracking";}s:7:"summary";s:4404:"There have been two side effects of our <a href=http://getclicky.com/blog/211/heres-what-new>recent changes to tracking</a> that we didn't really anticipate. This doesn't mean that something is broken, things just work differently now. We wanted to post about them here so you can understand what's going on.<br />
<br />
<h4>More visitors / less actions per visit</h4>You may have seen your daily visitor account increase substantially, but the number of actions remains the same. The main types of sites that are seeing this are those that have user accounts (e.g. people login to your site to do whatever it is they do on it).<br />
<br />
What's happening here? First, people tend to share their accounts with other people. We are seeing this big time on in our stats for getclicky.com, for example. We see multiple sessions from the same user account and the same IP address at around the same time, which previously would have been counted as the same session. Because we have cookies now, we are able to determine that these are in fact two unique users. We can tell because when we view these sessions, in almost all cases the computer details are different. One might have Windows XP and Firefox 3.0, the other Windows Vista and Internet Explorer. Since the old method was just using the IP address, they would have been clumped together into one visit. The new system seperates them into two unique sessions, as they should be, since they are occurring on two different computers.<br />
<br />
What about the other cases? Well, the same thing can also happen for one visitor using two different browsers on one computer to access our site. Since cookies are stored at the browser level, their cookie ID will be different in each browser used. This isn't really desirable here, but it's also quite rare. Not many people use multiple browsers at the same time. All other analytics services that use cookies will have the same problem. If you think about it though, it really is two different sessions, because the person is doing two seperate things in the two browsers.<br />
<br />
<h4>Visitors online in Spy is lower</h4>If you have a moderate traffic site (at least ~5,000 daily visitors), you may have noticed that when you load up Spy, the visitors online value is quite a bit lower than the one you see reported on the dashboard.<br />
<br />
The reason this is happening is because we only store the last X number of actions in the Spy cache for each site. Although we don't count pings as actions in your stats, the way that they are processed in the backend is the same. Since pings are now stored in that cache, when you first load Spy, the cache may not actually have all of the data for your visitors that are all online at that moment. So you will see lower number initially, but once Spy has been running for a few minutes, it should have a much more accurate number. We want to fix this and will probably increase the size of the cache, but we need to be careful about doing that.<br />
<br />
You also may be seeing lower numbers because you don't actually have as many visitors online at one time. As we explained in our last post, Spy now uses the pings to determine when visitors are truly online or not, rather than a generic 5 minute timeout that we were doing before. Now Spy will know within 1 minute of a visitor leaving your site that they have actually left (because the pings have stopped), instead of waiting 5 minutes to remove them. The end result here is that we remove visitors a lot quicker from Spy than we used to, so the value we report here might be lower than it used to be. But it's more accurate, and that's a good thing.<br />
<br />
Hope that helps.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=DDf8G8y9An0:bJvcvpc0xoE:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=DDf8G8y9An0:bJvcvpc0xoE:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=DDf8G8y9An0:bJvcvpc0xoE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=DDf8G8y9An0:bJvcvpc0xoE:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=DDf8G8y9An0:bJvcvpc0xoE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/DDf8G8y9An0" height="1" width="1"/>";}i:39;a:9:{s:5:"title";s:16:"Here's what new!";s:4:"link";s:70:"http://feedproxy.google.com/~r/getclicky/~3/EdEmzvXKNaM/heres-what-new";s:8:"comments";s:44:"http://getclicky.com/blog/211/heres-what-new";s:4:"guid";s:44:"http://getclicky.com/blog/211/heres-what-new";s:11:"description";s:6432:"The new Clicky is live! In the form of a novel, here's what new:<ul><li><h4>Cookies</h4>We now use cookies to more accurately track unique visitors. As mentioned previously, you can disable cookies if you don't want them on your site, with <a href=http://getclicky.com/help/customization#no_cookies>clicky_custom.no_cookies</a>. If a visitor does not have cookies enabled or you have disabled them on your site, then we fallback on the visitor's IP address, which is how we were doing this previously.<br />
<br />
<li><h4>Pinging</h4>When a visitor remains on a single page of your site, our tracking code will ping our tracking servers in the background so we know they are still online. This will also let us give you much more accurate time online values, both per visitor and average.<br />
<br />
By default, a visitor will ping us for 20 minutes while on one page. Depending on the type of site you are running, you may wish for a longer time that that. Don't worry, you can customize it! Using <a href=http://getclicky.com/help/customization#timeout>clicky_custom.timeout</a>, you can extend the pinging time up to 4 hours. This is perfect for sites that are focused on things like videos or games.<br />
<br />
<li><h4>Spy + Ping</h4>Spy uses the new pinging functionality to more accurately display who is actually on your site right now. Previously, we were just using a 5 minute timeout period of no activity to determine that a visitor was gone. Pinging allows us to actually know who is on your site, so Spy will be much more accurate. Pinging starts at every 15 seconds but quickly decays to once per minute, so there's still a timeout of 1 minute on Spy before a visitor will disappear. Pinging will also let us display visitors who are just sitting there on one page. Previosly they would disappear after 5 minutes but now they will stay there as long as they keep pinging us.<br />
<br />
The result of this is a lot more spikes in the visitors online graph, rather than a fairly smooth one as you may be used to. Here's an example of what we mean:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201004-spy.gif><br />
<br />
<li><h4>New vs returning visitors</h4>We now track new vs returning visitors. You will see in the basics dashboard module, there's a new expand link. Clicking this will show your unique visitors and your new visitors for the date or date range you are viewing. Because we are only tracking new visitors from this point forward, this metric won't be terribly accurate for the first week or two until most of your regulars have visited your site again.<br />
<br />
You can also filter by new or returning visitors, it's in the filter drop down box on the visitors page.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201004-new-visitors.gif><br />
<br />
<li><h4>Bounce rates</h4> Our bounce rate calculations also take pinging into account now. As far as we know, all other analytics services define a bounce as a visitor who only views one page. But if they actually stay on your site for a little bit, they are probably more engaged with your site. The first ping occurs after 15 seconds, so that's our new threshold for determining what a bounce is. Anyone who is on your site less than 15 seconds is a bounce, anyone on longer is NOT a bounce - regardless of how many actions they had. We think this is a much better way to calculate this metric.<br />
<br />
<li><h4>Self hosted tracking code</h4>If you are self-hosting the tracking code, you will need to grab a fresh copy to get cookie and ping support. We'd also like to make clear that we no longer support this option. Our tracking code is now on a CDN and we also offer asynchronous tracking code, so there's no need for it anymore. Making this update backwards compatible for people doing the self-hosted thing was a bit of a pain. From this point on, we cannot guarantee backwards compatibility with those of your self-hosting, so you are doing so at your own risk!<br />
<br />
<li><h4>More efficient</h4>The way we process and store visitors has dramatically changed, and the result is about an 80% increase in efficiency - which is a very big deal. This means we'll have to do database maintenance a lot less often (e.g. what we do every few months to a couple of servers, such as last week with db7/8/9). Smaller storage also means much faster filtering. You should notice a dramatic increase in filtering (segmentation) of your visitors for most data types.<br />
<br />
This also results in much faster processing of traffic. We think it's going to allow us to track higher traffic sites. The highest level of traffic we allow for any site is 500,000 page views per day. We think our new system will be able to double that capacity - but we're not sure yet. We're going to be monitoring things and will certainly let people know if we increase this limit.<br />
<br />
Please note, converting your existing visitors to this new format will take up to 48 hours on some servers. So rather than keep these servers offline during the conversion, the conversion will be occuring over the weekend while the servers are live. It should be finished by Sunday though. The point is, when viewing your visitors list, some visitors may have incomplete data (e.g. just an IP address). Don't panic - their data *will* appear! We're doing this from newest to oldest visitors, so you probably won't even notice it unless you go back in your history a bit.<br />
</ul><br />
<br />
There may be a few bugs lying around. We'll be monitoring and fixing anything unusual over the weekend. If you see anything strange, don't hesitate to leave a comment here or send us an email. Hope you enjoy!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=EdEmzvXKNaM:S9enGkYLji8:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=EdEmzvXKNaM:S9enGkYLji8:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=EdEmzvXKNaM:S9enGkYLji8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=EdEmzvXKNaM:S9enGkYLji8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=EdEmzvXKNaM:S9enGkYLji8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/EdEmzvXKNaM" height="1" width="1"/>";s:7:"pubdate";s:31:"Fri, 16 Apr 2010 22:08:30 -0800";s:5:"bonus";s:10:"1271480910";s:10:"feedburner";a:1:{s:8:"origlink";s:44:"http://getclicky.com/blog/211/heres-what-new";}s:7:"summary";s:6432:"The new Clicky is live! In the form of a novel, here's what new:<ul><li><h4>Cookies</h4>We now use cookies to more accurately track unique visitors. As mentioned previously, you can disable cookies if you don't want them on your site, with <a href=http://getclicky.com/help/customization#no_cookies>clicky_custom.no_cookies</a>. If a visitor does not have cookies enabled or you have disabled them on your site, then we fallback on the visitor's IP address, which is how we were doing this previously.<br />
<br />
<li><h4>Pinging</h4>When a visitor remains on a single page of your site, our tracking code will ping our tracking servers in the background so we know they are still online. This will also let us give you much more accurate time online values, both per visitor and average.<br />
<br />
By default, a visitor will ping us for 20 minutes while on one page. Depending on the type of site you are running, you may wish for a longer time that that. Don't worry, you can customize it! Using <a href=http://getclicky.com/help/customization#timeout>clicky_custom.timeout</a>, you can extend the pinging time up to 4 hours. This is perfect for sites that are focused on things like videos or games.<br />
<br />
<li><h4>Spy + Ping</h4>Spy uses the new pinging functionality to more accurately display who is actually on your site right now. Previously, we were just using a 5 minute timeout period of no activity to determine that a visitor was gone. Pinging allows us to actually know who is on your site, so Spy will be much more accurate. Pinging starts at every 15 seconds but quickly decays to once per minute, so there's still a timeout of 1 minute on Spy before a visitor will disappear. Pinging will also let us display visitors who are just sitting there on one page. Previosly they would disappear after 5 minutes but now they will stay there as long as they keep pinging us.<br />
<br />
The result of this is a lot more spikes in the visitors online graph, rather than a fairly smooth one as you may be used to. Here's an example of what we mean:<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201004-spy.gif><br />
<br />
<li><h4>New vs returning visitors</h4>We now track new vs returning visitors. You will see in the basics dashboard module, there's a new expand link. Clicking this will show your unique visitors and your new visitors for the date or date range you are viewing. Because we are only tracking new visitors from this point forward, this metric won't be terribly accurate for the first week or two until most of your regulars have visited your site again.<br />
<br />
You can also filter by new or returning visitors, it's in the filter drop down box on the visitors page.<br />
<br />
<img src=http://static.getclicky.com/media/screenshots/201004-new-visitors.gif><br />
<br />
<li><h4>Bounce rates</h4> Our bounce rate calculations also take pinging into account now. As far as we know, all other analytics services define a bounce as a visitor who only views one page. But if they actually stay on your site for a little bit, they are probably more engaged with your site. The first ping occurs after 15 seconds, so that's our new threshold for determining what a bounce is. Anyone who is on your site less than 15 seconds is a bounce, anyone on longer is NOT a bounce - regardless of how many actions they had. We think this is a much better way to calculate this metric.<br />
<br />
<li><h4>Self hosted tracking code</h4>If you are self-hosting the tracking code, you will need to grab a fresh copy to get cookie and ping support. We'd also like to make clear that we no longer support this option. Our tracking code is now on a CDN and we also offer asynchronous tracking code, so there's no need for it anymore. Making this update backwards compatible for people doing the self-hosted thing was a bit of a pain. From this point on, we cannot guarantee backwards compatibility with those of your self-hosting, so you are doing so at your own risk!<br />
<br />
<li><h4>More efficient</h4>The way we process and store visitors has dramatically changed, and the result is about an 80% increase in efficiency - which is a very big deal. This means we'll have to do database maintenance a lot less often (e.g. what we do every few months to a couple of servers, such as last week with db7/8/9). Smaller storage also means much faster filtering. You should notice a dramatic increase in filtering (segmentation) of your visitors for most data types.<br />
<br />
This also results in much faster processing of traffic. We think it's going to allow us to track higher traffic sites. The highest level of traffic we allow for any site is 500,000 page views per day. We think our new system will be able to double that capacity - but we're not sure yet. We're going to be monitoring things and will certainly let people know if we increase this limit.<br />
<br />
Please note, converting your existing visitors to this new format will take up to 48 hours on some servers. So rather than keep these servers offline during the conversion, the conversion will be occuring over the weekend while the servers are live. It should be finished by Sunday though. The point is, when viewing your visitors list, some visitors may have incomplete data (e.g. just an IP address). Don't panic - their data *will* appear! We're doing this from newest to oldest visitors, so you probably won't even notice it unless you go back in your history a bit.<br />
</ul><br />
<br />
There may be a few bugs lying around. We'll be monitoring and fixing anything unusual over the weekend. If you see anything strange, don't hesitate to leave a comment here or send us an email. Hope you enjoy!<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/getclicky?a=EdEmzvXKNaM:S9enGkYLji8:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/getclicky?i=EdEmzvXKNaM:S9enGkYLji8:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=EdEmzvXKNaM:S9enGkYLji8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/getclicky?i=EdEmzvXKNaM:S9enGkYLji8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/getclicky?a=EdEmzvXKNaM:S9enGkYLji8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/getclicky?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/getclicky/~4/EdEmzvXKNaM" height="1" width="1"/>";}}s:7:"channel";a:9:{s:5:"title";s:18:"getclicky.com/blog";s:8:"language";s:5:"en-us";s:4:"docs";s:37:"http://blogs.law.harvard.edu/tech/rss";s:8:"category";s:23:"WebTechnologyStatistics";s:9:"generator";s:10:"Papa v0.3b";s:13:"lastbuilddate";s:31:"Thu, 03 Mar 2011 12:42:57 +0000";s:4:"link";s:25:"http://getclicky.com/blog";s:11:"description";s:3:"Fun";s:7:"tagline";s:3:"Fun";}s:9:"textinput";a:0:{}s:5:"image";a:0:{}s:9:"feed_type";s:3:"RSS";s:12:"feed_version";s:3:"2.0";s:5:"stack";a:0:{}s:9:"inchannel";b:0;s:6:"initem";b:0;s:9:"incontent";b:0;s:11:"intextinput";b:0;s:7:"inimage";b:0;s:13:"current_field";s:0:"";s:17:"current_namespace";b:0;s:19:"_CONTENT_CONSTRUCTS";a:6:{i:0;s:7:"content";i:1;s:7:"summary";i:2;s:4:"info";i:3;s:5:"title";i:4;s:7:"tagline";i:5;s:9:"copyright";}s:4:"etag";s:27:"kopGZ26vKKiu0d9Zv+L+eXD2+hs";s:13:"last_modified";s:29:"Thu, 03 Mar 2011 21:16:35 GMT";}