<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Web Analytics Association Standards Document</title>
	<atom:link href="http://www.blackbeak.com/2009/01/13/web-analytics-association-standards-document/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blackbeak.com/2009/01/13/web-analytics-association-standards-document/</link>
	<description></description>
	<lastBuildDate>Thu, 12 Jan 2012 14:21:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: web analytics standards</title>
		<link>http://www.blackbeak.com/2009/01/13/web-analytics-association-standards-document/comment-page-1/#comment-12807</link>
		<dc:creator>web analytics standards</dc:creator>
		<pubDate>Tue, 10 Feb 2009 07:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackbeak.com/?p=242#comment-12807</guid>
		<description>Thanks for this information. It is great to learn about that document in here.</description>
		<content:encoded><![CDATA[<p>Thanks for this information. It is great to learn about that document in here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Captain Blackbeak</title>
		<link>http://www.blackbeak.com/2009/01/13/web-analytics-association-standards-document/comment-page-1/#comment-12638</link>
		<dc:creator>Captain Blackbeak</dc:creator>
		<pubDate>Wed, 21 Jan 2009 08:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackbeak.com/?p=242#comment-12638</guid>
		<description>@Angie;

Thanks for the detailed response. 
I do feel it&#039;s possible to get closer to an accurate count of UV&#039;s but that is a whole different story. 

What I mean is as you point out the tool-to-tool differences and I think this was what Brandt was also alluding to in his somewhat blunt way. 

By creating a roadmap for the tools to develop towards the WAA sets the agenda. By giving the tools precise definitions to work towards the tool differences come closer together.

By designing something like this an opportunity exists to become an auditing body which could also bring in revenue for the WAA.</description>
		<content:encoded><![CDATA[<p>@Angie;</p>
<p>Thanks for the detailed response.<br />
I do feel it&#8217;s possible to get closer to an accurate count of UV&#8217;s but that is a whole different story. </p>
<p>What I mean is as you point out the tool-to-tool differences and I think this was what Brandt was also alluding to in his somewhat blunt way. </p>
<p>By creating a roadmap for the tools to develop towards the WAA sets the agenda. By giving the tools precise definitions to work towards the tool differences come closer together.</p>
<p>By designing something like this an opportunity exists to become an auditing body which could also bring in revenue for the WAA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: angie</title>
		<link>http://www.blackbeak.com/2009/01/13/web-analytics-association-standards-document/comment-page-1/#comment-12631</link>
		<dc:creator>angie</dc:creator>
		<pubDate>Mon, 19 Jan 2009 19:03:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackbeak.com/?p=242#comment-12631</guid>
		<description>Brandt, it seems you and I have different recollections of the way the committee works. A relationship or liaison with another organization does not mean that the WAA must adopt their standards as is, especially if they are not appropriate for a large number of the people we represent. A relationship with JICWEBS was never formalized that committed us to anything of the sort. The way the committee understood it was that it was a &quot;We&#039;ll try to keep each other informed of what we&#039;re doing&quot; arrangement. We did indeed consider JICWEBS definitions when creating ours, along with those of the IAB and any other sources we could find.

I find the accusation &quot;dumped without formal process&quot; to be incredible. There&#039;s not a single definition in the document that didn&#039;t incur exhaustive discussion and review by the whole committee, and final approval for any definition took place over two meetings so anyone who missed the preliminary approval meeting still had a chance to speak up. The lively discussions (and occasional arguments) over the terms is one of the reasons that the document took so long to create, and it&#039;s one of the reasons that I&#039;m proud of the outcome. We have read your recent criticisms and they will also go into the pot for our future discussions. After all, we did ask for feedback and we are obligated to consider the bad as well as the good. 

On a committee, everyone gets to share their opinion, but not everyone will get their way (including me). It&#039;s an amazingly democratic process, and we have members with a wide range of experience. Not everyone buys/sells advertising, so specifications aimed at the advertising world simply aren&#039;t relevant to everyone. We would never suggest that an analyst or tool should not comply to JICWEBS or IAB specs if they are relevant to their business, but our audience for WAA Standards is the web analytics practitioner, not the ad buyer or seller. It amazes me that so many people can&#039;t see the distinction. There is overlap, yes, but the focus of the web analytics practitioner is to understand visitor behavior on a website, to improve both the visitor experience and the goals of the business. And we purposely wrote the definitions in such a way that the average marketing professional can understand them. 

Steve, the industry is very young indeed, and the Standards Committee is working towards more this-is-how-it&#039;s done specs (that&#039;ll be in v3 of the doc, not the final release of the 9/22 one). There are going to be diminishing returns on precision, and we need to find out where is the turning point. However &quot;precise&quot; we calculate a metric, it still isn&#039;t &quot;accurate&quot; because of cookie-deletion and other issues. Granted, we do want to eliminate as much of the tool-to-tool calculation differences as possible so we don&#039;t add insult to injury. But we need to balance changing the old metrics, with getting ahead of the curve with some of the newer metrics, as we are attempting to do with our Social Media Subcommittee.

angie</description>
		<content:encoded><![CDATA[<p>Brandt, it seems you and I have different recollections of the way the committee works. A relationship or liaison with another organization does not mean that the WAA must adopt their standards as is, especially if they are not appropriate for a large number of the people we represent. A relationship with JICWEBS was never formalized that committed us to anything of the sort. The way the committee understood it was that it was a &#8220;We&#8217;ll try to keep each other informed of what we&#8217;re doing&#8221; arrangement. We did indeed consider JICWEBS definitions when creating ours, along with those of the IAB and any other sources we could find.</p>
<p>I find the accusation &#8220;dumped without formal process&#8221; to be incredible. There&#8217;s not a single definition in the document that didn&#8217;t incur exhaustive discussion and review by the whole committee, and final approval for any definition took place over two meetings so anyone who missed the preliminary approval meeting still had a chance to speak up. The lively discussions (and occasional arguments) over the terms is one of the reasons that the document took so long to create, and it&#8217;s one of the reasons that I&#8217;m proud of the outcome. We have read your recent criticisms and they will also go into the pot for our future discussions. After all, we did ask for feedback and we are obligated to consider the bad as well as the good. </p>
<p>On a committee, everyone gets to share their opinion, but not everyone will get their way (including me). It&#8217;s an amazingly democratic process, and we have members with a wide range of experience. Not everyone buys/sells advertising, so specifications aimed at the advertising world simply aren&#8217;t relevant to everyone. We would never suggest that an analyst or tool should not comply to JICWEBS or IAB specs if they are relevant to their business, but our audience for WAA Standards is the web analytics practitioner, not the ad buyer or seller. It amazes me that so many people can&#8217;t see the distinction. There is overlap, yes, but the focus of the web analytics practitioner is to understand visitor behavior on a website, to improve both the visitor experience and the goals of the business. And we purposely wrote the definitions in such a way that the average marketing professional can understand them. </p>
<p>Steve, the industry is very young indeed, and the Standards Committee is working towards more this-is-how-it&#8217;s done specs (that&#8217;ll be in v3 of the doc, not the final release of the 9/22 one). There are going to be diminishing returns on precision, and we need to find out where is the turning point. However &#8220;precise&#8221; we calculate a metric, it still isn&#8217;t &#8220;accurate&#8221; because of cookie-deletion and other issues. Granted, we do want to eliminate as much of the tool-to-tool calculation differences as possible so we don&#8217;t add insult to injury. But we need to balance changing the old metrics, with getting ahead of the curve with some of the newer metrics, as we are attempting to do with our Social Media Subcommittee.</p>
<p>angie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Captain Blackbeak</title>
		<link>http://www.blackbeak.com/2009/01/13/web-analytics-association-standards-document/comment-page-1/#comment-12607</link>
		<dc:creator>Captain Blackbeak</dc:creator>
		<pubDate>Tue, 13 Jan 2009 18:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackbeak.com/?p=242#comment-12607</guid>
		<description>@Brandt; I find it laughable (I mean I actually laughed with disbelief when I read your comment) when you state &#039;you didn&#039;t want to bitch&#039;. Clearly the tone of your article was highly insulting to the folks involved in writing the current standard. 

That said if you have written standards  yourself it may be that the community can use them. I would urge that you produce them. Your recent article has at least raised an issue of importance. 

If they are made publicly available and as open to criticism as any other document (such as the current standards are) then no-one can argue with your stance. 

If you read carefully I actually never accused you of doing nothing. I challenged you to fix the situation which you have yet to do. I accused you of being a keyboard warrior  which I defined as someone who writes rhetoric in a confrontational manner simply to be noticed. I have no intention of withdrawing that statement until you prove otherwise.</description>
		<content:encoded><![CDATA[<p>@Brandt; I find it laughable (I mean I actually laughed with disbelief when I read your comment) when you state &#8216;you didn&#8217;t want to bitch&#8217;. Clearly the tone of your article was highly insulting to the folks involved in writing the current standard. </p>
<p>That said if you have written standards  yourself it may be that the community can use them. I would urge that you produce them. Your recent article has at least raised an issue of importance. </p>
<p>If they are made publicly available and as open to criticism as any other document (such as the current standards are) then no-one can argue with your stance. </p>
<p>If you read carefully I actually never accused you of doing nothing. I challenged you to fix the situation which you have yet to do. I accused you of being a keyboard warrior  which I defined as someone who writes rhetoric in a confrontational manner simply to be noticed. I have no intention of withdrawing that statement until you prove otherwise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandt Dainow</title>
		<link>http://www.blackbeak.com/2009/01/13/web-analytics-association-standards-document/comment-page-1/#comment-12606</link>
		<dc:creator>Brandt Dainow</dc:creator>
		<pubDate>Tue, 13 Jan 2009 16:25:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackbeak.com/?p=242#comment-12606</guid>
		<description>Actually I was on the WAA standards committee.  I was the one who did all the work getting liason relationships in place with JICWEBS.  The arrangements I negotiated were approved by WAA then ignored.  I also wrote definitions for several standards, including visit and session, which were precise, and - though approved by the committee - dumped without formal process and replaced with something looser.  Since I could not get anyone on the committee to see anything wrong with either situation, let alone deal with it, I left.  I did not place this information in my article because I did not want to bitch.  However, since I am accused here of doing nothing, just criticising, I feel I must defend myself.  I tried to get tighter standards in WAA and failed.   I even designed a rigorous international approval process as part of the planning of WAA before it was formed, but that too was ignored.  If I had my way WAA standards would be modelled on IETF and W3C, but the senior figures in WAA don&#039;t seem to agree.</description>
		<content:encoded><![CDATA[<p>Actually I was on the WAA standards committee.  I was the one who did all the work getting liason relationships in place with JICWEBS.  The arrangements I negotiated were approved by WAA then ignored.  I also wrote definitions for several standards, including visit and session, which were precise, and &#8211; though approved by the committee &#8211; dumped without formal process and replaced with something looser.  Since I could not get anyone on the committee to see anything wrong with either situation, let alone deal with it, I left.  I did not place this information in my article because I did not want to bitch.  However, since I am accused here of doing nothing, just criticising, I feel I must defend myself.  I tried to get tighter standards in WAA and failed.   I even designed a rigorous international approval process as part of the planning of WAA before it was formed, but that too was ignored.  If I had my way WAA standards would be modelled on IETF and W3C, but the senior figures in WAA don&#8217;t seem to agree.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

