What are your top 3 feature requests for Clicky?

We'd love to hear your top 3 feature requests for Clicky. This service has been in non-stop development for almost two and a half years, and there are still a billion things we want to do. Our todo list is 10 miles long, so it's hard to decide what to do next sometimes. That's where you come in.

Excluding all the stuff that's coming on our March roadmap - which includes things like filtering visitors by page URL, per-page analysis, and super mega ultra spy - what are you top 3 feature requests?

UPDATE This isn't a poll because we don't want to restrict your choices. We want to know exactly what you want, even if it's absolutely ridiculous.
59 comments |   Feb 18 2009 8:11pm

Feedburner has been fixed

All of you who have moved to the new Feedburner "platform" have been noticing that Clicky can no longer access your Feedburner data. I'd like to rant about the embarrassingly awful job Google did with this migration, but I'll save my efforts for something more useful. What matters is that it should be fixed if you are on the new platform. If you continue to have problems, please contact us or leave a comment here - but it should be working for everyone now!

UPDATE One of our users asked about why their FB data from more than a few months ago (around when they migrated) had disappeared. I just want to clarify this is a side effect of your migration. When you move from the old Feedburner to the new one, your data doesn't carry over - you start fresh, as if you had just signed up. I mean, that would just way too convenient, wouldn't it, to have your data carry over? Surely you weren't expecting them to spend the 15 minutes it might take to write a script that exported your data from the old database and imported it into the new one?
22 comments |   Feb 16 2009 4:13pm

Lots of new tracking features, including OnClick goals and internal script logging

Lots of new stuff related to tracking being released today.

OnClick goals

You can now declare goals from Javascript events, aka "OnClick". This has been a big request. Docs.

Internal script logging

We have documented the API that our tracking code uses to log data, which means we officially support this now. You can log any data you want to it, anytime you want, from anywhere. Validation is done with a new sitekey, called the "Admin sitekey". This is available in your site preferences. We know this will be insanely useful to all of you who use internal redirects for outbound/affiliate links. I get questions on that all the time, so you should love this! We also wrote this PHP function as a "simple" way to add this functionality to your own app. Use something other than PHP? Rewrite and send it to us, we'd love to offer it to our users.

I'm pretty sure that Clicky is the only service in the world that offers this type of functionality. Please tell me otherwise if this is incorrect.

Better customized tracking

There is now just a single Javascript variable called "clicky_custom" to deal with all aspects of customized tracking (adding custom user data, changing the pause timer, etc). Much cleaner and easier to work with, and a few extra features too. "pageview_disable" to disable the automatic logging of a page view on initial load, and "href" and "title" properties to customize the URL and page title that is logged for that page view. The docs have rewritten from scratch with all the new stuff added in. Backwards compatibility is built in so you don't need to change any of the existing features you're already using, such as custom data tracking. To use the new features, you'll need to update to the new methods though.

Update sessions after-the-fact

Using the same API mentioned above, you can update sessions well after they are expired, to add your own custom data to them, and declare goals and/or revenue. I get many emails from people who can't add tracking code and/or javascript variables to their shopping cart pages. Now you can update sessions later if you want, to declare the goal and revenue for that visitor.

It's 3am. Time for bed.
8 comments |   Feb 13 2009 2:42am

Google's new Ajax-powered search results breaks search keyword tracking for everyone

Do you run a web site? Do you use a service such as Clicky, Statcounter, AWStats, etc, to monitor the traffic to your web site? Do you find it useful how these services can tell you what search terms are leading visitors to your site? Have you ever wondered exactly how they are able to do that?

No, you probably haven't. But that's ok. Just know this: a major update that Google is testing has completely broken the ability for any external analytics service like Clicky to determine the search query used by a visitor arriving at your web site. Why would they do such a thing? Who knows. They aren't talking.

Knowing the search terms that are driving traffic to your web site is probably the #1 reason to use any kind of traffic monitoring service. And Google owns a huge chunk of the search market. If this update goes live for everyone, it effectively means that 2/3 of all searches leading to the average web site will be a complete mystery. This is huge.

So what is the problem exactly? Normally when do you a search on Google or any other search engine, the search term used become part of the URL. A search for Clicky, for example, gives you this:


When someone clicks a search result on that page, that URL above is sent as the "referrer" to the target site. An analytics app running on the target site can parse the referrer string and extract the word "clicky", and store that as a search that occured for that site. This is obviously very useful.

Here's what the new search result URLs look like with the new "Ajax" feature:


See how there's a hash mark # in there now, and the "q=test" is after it? The problem is that web browsers don't send anything after the # in the referrer string. This means organic searches from Google will now show up as just "http://www.google.com/", with no search parameters. In other words, no analytics app can track these searches anymore. I started noticing lots of hits from just "http://www.google.com/" recently in our own search logs. I thought maybe it was just a bug with Clicky. But then one of our users contacted me about this article, and my jaw about broke from hitting the floor so hard.

This change isn't live for everyone yet so if you go to google.com and do a search, you may not see it in action. But it is happening for me when I go there and do a search.

So what can we do about it? If you run a blog, write about this. Submit this story or your own story to large tech blogs like TechCrunch, CenterNetworks, ReadWriteWeb, GigaOm, etc - no large site has written about this yet, and one of them needs to. Post in Google's Web Search forums (there's no way to directly contact them about web search unfortunately). Do anything you can to spread the word and let Google know that this is not acceptable.
80 comments |   Feb 03 2009 9:50am

Clicky roadmap through March 2009

We've got a lot of buns in the oven right now, many of which are waiting for that database transform to be completed. All database servers are done, except for the one, the only, db1, which is lagging badly at barely 33% done. It should be done by this weekend though. (If you have a site on db1 and are tired of it being laggy, read this).

It's been fairly quiet around here recently, but we have in fact been working like mad behind the scenes, as usual. So I wanted to share with you the features we have planned for the next couple of months, all of which we plan to have out by the end of March 2009.

  • In depth per page analysis, e.g. for your "/contact" page, view the top countries, top searches leading to it, top referrers to it, percent of views that were landing/exit (meaning first or last action of a session), average time spent on page - ETC!
  • Filter visitors by number of actions, including support for less than, greater than, and equal to (e.g. at least 10, exactly 1, less than 3, etc)
  • Filter visitors by amount of time spent on site (at least 5 minutes, less than 1 minute, etc).
  • Filter visitors by revenue (at least $1000, exactly $100, less than $100, "any" amount of revenue, etc)
  • Filter visitors by a page URL (e.g. all visitors who viewed "/contact")
  • Goals: Support for javascript/onclick events to complete a goal
  • Goals: More up front details about revenue in views outside of the main goals page
  • Goals: View history (timeline graph) for conversion rate and/or revenue for any goal
  • API for adding data to a session after the fact (e.g. declaring a goal as completed, adding/changing revenue, etc)
  • Clicking an item under "links" or "pages" will by default invoke visitor filtering for that item, rather than going to it (e.g. clicking "/contact" would fitler your visitors by that page, instead of going to the contact page on your web site). To actually go to the link/page, there will be an arrow next to the item to click, if you want to do that instead.
  • Much better mirror/sub-domain support
  • Hourly data figures for visitors and actions
  • Track figures for page views, outbounds, downloads, and "clicks" seperately (dashboard module "the basics" will have expandable view to see this extra data for the total actions value)
  • Super Mega Ultra Spy (this will blow you away)
  • Visitor groups - kind of like a "saved" filter, e.g. all visitors from the US who arrived via Google and use Firefox. Groups will be able to be used as funnels for goals, which will be amazing.
  • Interface to update your credit card details, instead of forcing you to sign up for a new subscription when your card expires or you need to change it for whatever reason.

As you can see, that's quite a number of things coming soon. So be patient, and it will all eventually be yours!
18 comments |   Jan 26 2009 9:06am

Next Page »

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