What is jsHub?
jgc.org
jgc.org
I then went to your site to check out the demo and found a page with lots and lots of external javascript requests, and something about a microformat.
I'm still confused.
Suppose you accept that idea that instead of having 10 different web analytics tags on your page it would be better to have one tag (let's assume it's jsHub), then you can move up a level.
Rather than have each vendor define the metadata they want from the page, it's better to have a single set of metadata that all the vendors can use. So the point of the microformats is that they'll simplify even more the art of page tagging.
If vendors agreed to mark up the page name, or the products shown on the page, using a microformat then a single tag could read them and then fan the data out to various vendors. That way there's no ambiguity about what's being gathered.
"jsHub is a single piece of JavaScript (a "tag") that can handle reading different sorts of page information and then send them to many different vendors' products. One piece of code to send to Google Analytics, Omniture SiteCatalyst, WebTrends and Mixpanel."
Microformats aside, I'm trying to understand the solution to the hub part because that sounds like a problem many people would be interested in fixing.
The reasons to do that are laid out in my blog post but the most important is consistency. If one piece of JavaScript gathers the data once and passes it to various vendors, then you know that the same data was sent, and was actually sent.
You'll probably find that most of the requests you saw in Firebug are for the Inspector tool (built using YUI2).
The jshub.js file is the only 'tag' needed on a website (+ jquery if not already in use) and is designed to provide a 'hub' API for each vendors plug-in to query the data collected and send it on its way to a receiving server so only one file need be maintained as vendors come and go.
I want jsHub because it makes my sites load faster, right? How much faster? Any way to get some test cases or examples?
Differences in hit counts and visits between products are indeed annoying, but it serves as a check. How else would we know if traffic dipped overnight or jsHub went down? Also, I think part of the difference in those counts is due to different algorithms for what constitutes a "visit" and different filtering for bots.
And for the microformats, I hope you realize that's an uphill battle. I can't justify redesigning my pages to use some new format without a material benefit.
Microformats aren't asking for a page redesign. They are just class names. Our argument is that a clear specification is many times better than obscure JavaScript variables inside a Omniture tag, or parameters in a comScore Beacon, ...
Finally, the whole point of jsHub is that won't have to tag your site again. Adding a new product to a jsHub tagged web site means just changing the plugins in your jsHub set up.
You'd really prefer to have to register to read every site?
One of the key reasons for using a microformat (hPage) is the principle to "design for humans first and machines second".
We provide an Inspector tool on our Demo store to meet this principle and hope that, with the microformat's community's help, we can make the data visible in many other tools.
We would like to make website publishers and users more aware of the data being declared and collected so it can be more accurate and therefore more beneficial to all involved.
Currently many users are unaware data is being collected at all.
Am I missing something? Unless consumers start demanding to know what information is collected about them, I don't think that the benefits jsHub has for ad providers are important, and that they won't implement a plugin until they're pushed by some other forces. In other words: the merit of technical innovation isn't enough for them to change their behavior, and they need a bigger incentive in order to consider using jsHub at all.