Technobabbles I try to sound like I know what I'm talking about. Don't be fooled.

4Apr/080

New: Graph by Week and Month in Google Analytics

This is an exciting one! Google Analytics has just gotten the ability to change graphs to display points by week or month instead of just by day. Google Operating System reports that there is also an hourly option, which is only available on select reports such as Visitors.

The Google Analytics Blog has a neat series of screenshots that displays the difference between the different views. They say the new graphing features are designed to help expose hidden trends in the data; the day view can get awfully crowded with points and short-term trends can be hard to see.

I think it's a good addition. Using the hourly graph, I discovered that traffic to this site, for example, surges during the afternoon, peaking around 15:00. Combined with the last set of graphing enhancements, these new features promise to give Google Analytics additional "slicing and dicing" capabilities, which is always good. Stats junkies like me need things like this to just play with. ;-) Don't worry, it's useful too. :-D

25Mar/080

Financial Reports Waste Paper; Use the Internet

Financial reports are a colossal waste of paper. Well, perhaps that's not entirely true. I'm sure some people read every last character in those thick stacks of paper sent out by investment agencies at the end of the fiscal year. But most of us just shred them and put them in the recycling (or, unfortunately and probably more commonly, the trash).

What's in one of those things? Usually it's just a summary of all transactions conducted by the agency on your behalf since the last report, with a few statistics thrown in for good measure. Yes, it can be useful. No, it does not need to be mailed out to every agency customer, in triplicate (I kid you not; this does happen on occasion).

Before the invention of the Internet, such mailings made sense. There was simply no other good way of getting the documents. It was either paper mail or paper fax. Either way, you used paper.

Now, of course, we have the Internet, and that wonderful thing called email. Adobe made the PDF file format, and we should be using that, too. There's simply no good reason to use paper for these reports in this day and age.

Considering that each report averages around 20 or 30 pages, and that there will often be multiple reports mailed by multiple agencies, that translates into a lot of paper, especially if the amount is multiplied by the number of customers receiving those documents. As I said, we could definitely email PDFs instead of putting all these reams of paper in the mail. What if, just hypothetically, there was a better way? A better way even than email?

I think there is, and it's kind of making me eat my own words. What if all the reports were simply generated on-the-fly by a Web-based console? Each customer would get a login (always transmitted over SSL, of course, as with the rest of the site), which would get them into a reporting interface tied to their transactions. Undoubtedly, the transaction data is stored in a database. That would be an efficient way to store such uniform data. The site would simply tie into that database (or a replicated read-only copy, for another layer of hacker cracker safety).

In my mind, I envision the same sort of powerful reporting interface as those used by applications like Google Analytics. Date ranges, comparisons, graphs, charts... All would be quite welcome in a world of financial data. And the best part of such a system would be the near-obsolescence of paper reports. The dynamic charting and date-range selection capabilities of the Web application would surely prove more useful than fixed paper reports.

Of course, there would be Luddites intent upon keeping their paper-based reports. Hence "near-obsolescence" rather than just "obsolescence." There would have to be an option to receive paper reports, in recognition of the views held by the few people who would want them. But that option should be turned off by default. Anyone who wanted paper mailed to them would simply call the agency and say so. It could even be a question when new customers sign up. But again, the default would be "no." As far as I can tell, most people don't use the paper, so why waste it?

It's probably obvious that this is a half-baked idea. I haven't got any interface mock-ups, server-side code (say, PHP or Python), SQL, or anything else. All I have is an ideal, that paper-based reports be sent only -- and only -- to the people who want and use them.

21Mar/080

Google Analytics Benchmarking Active

If you follow the other Google blogs such as Google Operating System or Google Blogoscoped, you'll probably already know that Google Analytics' Benchmarking feature is finally showing data. Heck, the Google Analytics Blog even announced this one. I thought I'd blog my take on it anyway, just to see how my opinion differs from those other people.

At first glance, the benchmarking data is cool. I haven't had a chance to probe every nook and cranny yet, but it looks like it is can be quite useful. That is, if your site fits into one of the categories provided.

I looked in the category list, and it didn't appear to have a "blog" category for me to select. Analytics just compared me with all other sites of similar size, however that's measured. All I know is, I have red marks on all metrics except New Visitors. I don't get as much traffic here as I'd like; hopefully that will change eventually and I'll have more green.

For those who are curious about what the benchmarking looks like, here's a screenshot I made from the data available for this site:

Like I said, red marks everywhere. If you didn't figure it out, the blue line is your site and the gray line is all the averaged data from other, similar sites. How about getting more of those blue lines above the gray ones? I'd certainly like that. I have a high bounce rate, low visits/pageviews, and a low pages/visit average. Must figure out how to grow this site... But I knew that without the benchmarks, didn't I? (Yes, I did.) Whatever, they still look cool.

5Mar/080

Google Analytics Rolling Out Benchmarking and Sharing Settings

Google Analytics makes a great way to track how your site is doing, visitor-wise, and see what content attracts the most eyeballs. If you don't have a lot of experience in the Web analytics world, like myself (I won't lie, I'm a n00b), you'll probably find these upcoming features useful.

What they'll do is allow you to see how other sites in your vertical market perform. (Your "vertical market", or "vertical", is your field, e.g. e-commerce, blog, etc. I think. Like I said, I'm a n00b.) To get the option, those of us with higher account numbers will have to wait until Google rolls out the options to our accounts.

Once you do have the option, you'll have to enable it by allowing Google access to your Analytics data for purposes of analysis. You can't get benchmarking data without sharing your own statistics, and it may be up to two weeks before you'll be able to see any benchmarking data at all. Nevertheless, it sounds like a useful feature that I will be glad to have once it's enabled on my account.

I won't go into heavy detail because the Google Analytics Blog already has it well-covered. I will say that you have to share all data in your account; you can't enable selected website profiles. That seems like an important point.

Also, there are granular data sharing options, so you can share your data with everyone (anonymously) or just with Google, allowing upcoming enhanced services to work with Google Analytics and become integrated in one interface.

For more specific details and a screenshot, hop over to the Analytics blog; I'm just writing a summary and brief opinion here. No sense writing again what has already been said by other people who understand the new stuff a whole lot better than I. ;-)

13Dec/072

Google Analytics Rolls Out New Graphing Tools and ga.js Tracking

Google Analytics just announced new graphing tools for the service. Now, apart from comparing two date ranges, users can compare different metrics to look for correlations ("Do pageviews increase as time on site goes up?"), as well as comparing individual segments with the site total.

The new ga.js tracking code, which I've been awaiting since the new code announcement made in October, has also been rolled out. The new file replaces the old urchin.js script. It is completely rewritten, appears to load faster, and has new object-based methods instead of functions and variables, meaning tracking a site in multiple accounts is a bunch easier.

The Google Analytics team also rolled out support for six new languages.

Now all I want to happen is automatic external link tracking and event tracking, both in limited beta at the moment.

3Nov/070

Google Analytics Site Search Launched

Well, I've got access to Site Search now in Google Analytics. It doesn't do much right now, since people mostly get here from Google search and view about one page, but it'll be handy for other sites I develop. Once I manage to implement search for them. Support for the AJAX Search gadget (which I have in the sidebar) is still up in the air; I've requested assistance on the Google Analytics Help group on Google Groups. Hopefully, it's supported, or the Blogger team is working on supporting it; or maybe I'll have to wait until the Analytics team adds the event tracking code and updates my account, and then for the Blogger team to implement event tracking in the widget. Sigh. I guess we'll see exactly what happens. I haven't seen anybody visiting a /search location anyway, yet.

16Oct/070

Urchin 6 Confirmed

Well, that's what I get for blogging without first reading the entire set of new posts from Analytics Talk. That nice blogger over at EpikOne has confirmed that the new beta Urchin software is indeed the long-awaited Urchin 6 update. It has a completely rewritten back-end, uses the old Analytics interface, and uses Flash graphs instead of the SVG graphics it used to (info second-hand from the post). It will cost about $3,000, and can be used with all its functionality (no more modules) for one price. Existing owners can get discounts, and users who purchased service contracts will get the upgrade for free. Google's back on the ball! That news coverage in PC World came at the right time...

16Oct/070

New Google Analytics Code

Google has released a new version of the Google Analytics JavaScript, as well, named ga.js. It replaces the old function- and variable-based calls with a new object-oriented style, and was rewritten to support event tracking. Other new features include the currently in-beta outbound link tracking and the in-rollout site search tracking. The code's structure has changed completely, so sites using calls to urchinTracker() in multiple places (i.e. not just in the tracking code) will need to plan their upgrades so as not to leave data holes. The old urchin.js should be supported for a while, as the old Analytics reporting interface was earlier this year. I'll have to update all of my sites (I have several using GA), but fortunately, I only have one, maybe two, instances of extra calls to urchinTracker(), and I will probably remove those when outbound link tracking is enabled or replace them with the new event tracking.

16Oct/070

Google Analytics Updates

Today saw some exciting announcements originally made at the eMetrics Summit in Washington, D.C. Google Analytics will be rolling out several new features in the coming weeks, including the ability to track site search (if your site has search, like this one does), tracking events in Flash and JavaScript without using urchinTracker() (which artificially increases pageviews), and Outbound Link Tracking, which will (as its name says) track outbound links. The event and outbound link tracking will first be launched as betas, meaning I might not get to use them for a while. But man, that last one's going to be a useful feature for sites like blogs!

Also announced is a new beta of Urchin (that years-late software package update, I'm guessing). Users can participate in the beta by contacting a Google "Authorized Consultant", whatever those are.

All in all, an exciting day for us Google Analytics users. Better be careful next year; I might be tracking what arrows you click in the Blog Archive sidebar... (That's actually impossible with my current knowledge; Blogger modules can't be changed like that.)

7Oct/070

Google’s Quietness About Releases

Since Google bought the Urchin company in 2005, and since then has been extremely quiet about the upgrade Urchin promised in late 2004. The Urchin 6 upgrade has never been released, though the Google Analytics website says, "Urchin 6 software will not be free when it is released." It goes on to say that customers who purchased extended service contracts that have expired will be offered a free upgrade, though there is no indication at all of the product's release date, now approximately three years overdue.

Current customers are getting antsy about Google's keeping mum, and it certainly would worry me if I had spent $10,000 of company money on an analytics package and support service with an upgrade that never came. Not to mention, part of the reason would have been to develop a relationship with the software company, which was bought out only a few short months later. Such is what happened United Diamonds, Inc., a 25-employee diamond vendor based in Sun City, California. They spent thousands of dollars on a software package with service contract and upgrades promised, and then lost their business relationship with Urchin when it was bought, and the upgrade was already a few months overdue at the time of Google's purchase.

Google has historically preferred the Software As A Service (SAAS) model over packaged software, as it keeps installation-related technical support requests at bay (they are just about nonexistent) and gives everyone instant access to updates when they are released. However, Google is very quiet about its release schedules for products, never announcing new versions until they are released. Various blogs run by Google staff members announce minor feature additions and security-related bug fixes, but version-related commentary is distinctly absent.

The recent graduation of Google Reader from the Labs testing ground (written up in a humorous letter on the Reader blog) was unknown until it actually happened, as was the search box released a couple weeks beforehand. User feedback seemed like it was being ignored when Google was actually working on features behind the scenes. They just didn't tell anyone about them.

Google might be able to keep free customers happy, but if they start delaying new releases for years on corporate customers, such as Google Apps Premier buyers, some consumers might become disgusted with their no-announcement policy and go somewhere else.