My Photo

Clicky

  • Clicky Web Analytics

Your email address:


Powered by FeedBlitz

« Measuring Online Applications | Main | Measuring Online Applications – Creating a Measurement Framework »

Comments

Interesting article Gary.

What you're describing here is very familiar - smart developers do not like the way the analytics vendors (particularly Omniture because there are so many more variables open for coding) recommend sending data.

You may want to look at http://ogilvy.com to explore the jQuery tracking modules the Ogilvy team I worked with tracked the site. The savvy developers in New York have developed re-usable scripts that extract the Omniture code from the presentation layer to make management an maintenance simpler. This approach we used on a number of installations. Creds to http://twitter.com/hikirsch for pushing this process through.

Cheers, James.

Cheers, James.

Gary,

As I mentioned in your previous post, UK-based Speed Trap seem to do a nice job of tracking applications.

I have seen the data capture process visualized. It's pretty impressive.
Unfortunately, We didn't go into the technical details in depth - too many marketing people in the meeting (plus parts of their technology is trademarked).

A little more about it can be found here:
http://www.speed-trap.com/capture.aspx

They use a single piece of JS code. The demo was on a live site that didn't have the Speed Trap code implemented. They used a laptop as a proxy and captured the data on the fly).

It might be a technology worth investigating for heavily data-driven organisations.

Thanks
Michael

(for avoidance of any doubt - I am not affiliated with Speed Trap in any form)

This is a very good statement of the requirements to build measurable websites and applications.

I'm intimately aware of the problems inherent in post-production marking up of pages and UI elements for the sake of tracking and recording data and I believe it should be part of the delivery of a project in much the same way SEO and accessibility is.

Whilst I think you are referring to providing better support within the application development environment, you may find some similarity in our ideas over at http://jshub.org/ where we are building a high quality OS solution along these lines for use on websites.

Please not that this is not another 'Universal Tag' type solution but an attempt to decouple the 'Universal Data' from the mechanism of the data transport, and so our design separates these into 2 activities:

1. Collect all the data at one state in time and create a 'measurement object'
2. Allow controlled access to this object for all interested parties with an interception point for custom mapping of properties - in our case as most vendors have differing wire-formats for the image request.

We use an event driven design to allow for each activity to operate whenever a user interaction occurs or a standard event is triggered, such as a form onSubmit(), in anticipation of the need to measure interactions that are not page views and link clicks.

This HTML mark-up + JS events approach is used very effectively within YUI Widgets, and as a developer feels more 'right' - I very much look forward to your next post.

Here are some resources for further information:

1. jsHub tag architechture: https://jshub.org/projects/jshub/#developer_information
2. Designing a mark-up standard: https://jshub.org/blog/2009/10/19/designing-hpage/

@James thanks for the pointer to Olgivy - we are also building our solutions on jQuery and its interesting to see this in action.

Thanks

Liam

I'm intimately aware of the problems inherent in post-production marking up of pages and UI elements for the sake of tracking and recording data and I believe it should be part of the delivery of a project in much the same way SEO and accessibility is.

The comments to this entry are closed.