<?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 for On The Trail</title>
	<atom:link href="http://blog.keyes.us/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.keyes.us</link>
	<description></description>
	<lastBuildDate>Thu, 12 Feb 2009 17:04:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Debugging Toolkit by Adam Berlinger</title>
		<link>http://blog.keyes.us/2006/09/15/debugging-toolkit/comment-page-1/#comment-34886</link>
		<dc:creator>Adam Berlinger</dc:creator>
		<pubDate>Thu, 12 Feb 2009 17:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://keyes.tracerss.com/blog/?p=46#comment-34886</guid>
		<description>Hi. Your WT Debugger does not work. I put it in my Favorites and click on it when I&#039;m on a site that has WebTrends tags, e.g. icoke.ca. Any suggestions? Thanks!</description>
		<content:encoded><![CDATA[<p>Hi. Your WT Debugger does not work. I put it in my Favorites and click on it when I&#8217;m on a site that has WebTrends tags, e.g. icoke.ca. Any suggestions? Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tealeaf vs. Web Analytics by Ted</title>
		<link>http://blog.keyes.us/2008/03/04/tealeaf-vs-web-analytics/comment-page-1/#comment-17373</link>
		<dc:creator>Ted</dc:creator>
		<pubDate>Tue, 13 May 2008 23:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.keyes.us/2008/03/04/tealeaf-vs-web-analytics/#comment-17373</guid>
		<description>Brilliantly stated! We are currently defending omniture&#039;s existence on our site now that we have ponied up for tea leaf and all the hardware behind it.</description>
		<content:encoded><![CDATA[<p>Brilliantly stated! We are currently defending omniture&#8217;s existence on our site now that we have ponied up for tea leaf and all the hardware behind it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The sorry state of usability by Robin</title>
		<link>http://blog.keyes.us/2008/04/10/the-sorry-state-of-usability/comment-page-1/#comment-14236</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Fri, 11 Apr 2008 03:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.keyes.us/2008/04/10/the-sorry-state-of-usability/#comment-14236</guid>
		<description>I think usability is something that&#039;s very often overlooked in favour of over-zealous adherence to tickbox web accessibility standards. Too many people fail to realise that &quot;accessibility&quot; in this particular context doesn&#039;t really mean that the site is accessible to the general user as a visitor experience. It&#039;s also surprising how many things can be easily overlooked by the tech savvy developer, things that I think are simple and obvious clearly aren&#039;t when I get a web novice to evaluate the site for me. As a simple example of a wider problem, on my homepage I used to have no &quot;Home&quot; menu button because I thought it was obvious and common practice that one could reach the homepage by clicking on the main logo...but that wasn&#039;t the case when it came to testing it with less experienced web users.</description>
		<content:encoded><![CDATA[<p>I think usability is something that&#8217;s very often overlooked in favour of over-zealous adherence to tickbox web accessibility standards. Too many people fail to realise that &#8220;accessibility&#8221; in this particular context doesn&#8217;t really mean that the site is accessible to the general user as a visitor experience. It&#8217;s also surprising how many things can be easily overlooked by the tech savvy developer, things that I think are simple and obvious clearly aren&#8217;t when I get a web novice to evaluate the site for me. As a simple example of a wider problem, on my homepage I used to have no &#8220;Home&#8221; menu button because I thought it was obvious and common practice that one could reach the homepage by clicking on the main logo&#8230;but that wasn&#8217;t the case when it came to testing it with less experienced web users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Tealeaf vs. Web Analytics by Jacques Warren</title>
		<link>http://blog.keyes.us/2008/03/04/tealeaf-vs-web-analytics/comment-page-1/#comment-12768</link>
		<dc:creator>Jacques Warren</dc:creator>
		<pubDate>Mon, 31 Mar 2008 17:03:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.keyes.us/2008/03/04/tealeaf-vs-web-analytics/#comment-12768</guid>
		<description>Great account! I especially like your ROI approach of it: often, he prepackaged solution offers peac of mind, since you know what you&#039;re getting. Hownever, being able to use web analytic on a database is quit attractive, cf. products such as Visitor Intelligence (WebTrends)and Dicover (Omniture).</description>
		<content:encoded><![CDATA[<p>Great account! I especially like your ROI approach of it: often, he prepackaged solution offers peac of mind, since you know what you&#8217;re getting. Hownever, being able to use web analytic on a database is quit attractive, cf. products such as Visitor Intelligence (WebTrends)and Dicover (Omniture).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Debugging Toolkit by The devil is in the details with running a website. The glamorous side of web analytics. &#124; Ubermarketer</title>
		<link>http://blog.keyes.us/2006/09/15/debugging-toolkit/comment-page-1/#comment-12681</link>
		<dc:creator>The devil is in the details with running a website. The glamorous side of web analytics. &#124; Ubermarketer</dc:creator>
		<pubDate>Sun, 30 Mar 2008 18:49:14 +0000</pubDate>
		<guid isPermaLink="false">http://keyes.tracerss.com/blog/?p=46#comment-12681</guid>
		<description>[...] WT Debugger, from Mike Keyes over at On the Trail. WT Debugger is an itsy-bitsy script that displays all the parameters sent by a web page tracked by WebTrends back to the data server. Obviously that last sentence only makes sense to the small minority of people who deal with web analytics and, in all likelihood, there are probably three people in the universe who actually might be excited by this insight. Let me assure you, WT Debugger is very cool, especially if you happen to manage a very large website and work for a management team that likes to have superior data on their internet business. You see, gathering web analytics data requires that your website is properly tagged &#8212; a trifling matter for the typical neighborhood blog, but one giant headache for large commercial websites with multiple technical providers and content suppliers. Enter WT Debugger, which is a wonderful way to spend a Friday evening. Who says web analytics isn&#8217;t interesting? [...]</description>
		<content:encoded><![CDATA[<p>[...] WT Debugger, from Mike Keyes over at On the Trail. WT Debugger is an itsy-bitsy script that displays all the parameters sent by a web page tracked by WebTrends back to the data server. Obviously that last sentence only makes sense to the small minority of people who deal with web analytics and, in all likelihood, there are probably three people in the universe who actually might be excited by this insight. Let me assure you, WT Debugger is very cool, especially if you happen to manage a very large website and work for a management team that likes to have superior data on their internet business. You see, gathering web analytics data requires that your website is properly tagged &#8212; a trifling matter for the typical neighborhood blog, but one giant headache for large commercial websites with multiple technical providers and content suppliers. Enter WT Debugger, which is a wonderful way to spend a Friday evening. Who says web analytics isn&#8217;t interesting? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Brand feud? by Michael</title>
		<link>http://blog.keyes.us/2008/01/07/brand-feud/comment-page-1/#comment-376</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 07 Jan 2008 23:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.keyes.us/2008/01/07/brand-feud/#comment-376</guid>
		<description>Ha. I saw the same thing. And I was going to blog about it but you beat me to it. Oh well, I blogged about it anyway. I suppose it is one way to create buzz.</description>
		<content:encoded><![CDATA[<p>Ha. I saw the same thing. And I was going to blog about it but you beat me to it. Oh well, I blogged about it anyway. I suppose it is one way to create buzz.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Brand feud? by Eric Peterson Equips his WebCast of +7 to Irony - Mymotech</title>
		<link>http://blog.keyes.us/2008/01/07/brand-feud/comment-page-1/#comment-375</link>
		<dc:creator>Eric Peterson Equips his WebCast of +7 to Irony - Mymotech</dc:creator>
		<pubDate>Mon, 07 Jan 2008 23:05:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.keyes.us/2008/01/07/brand-feud/#comment-375</guid>
		<description>[...] Dang you, Mike Keyes for beating me to the punch on this post! Share with the world:These icons link to social bookmarking sites where readers can share and discover new web pages. [...]</description>
		<content:encoded><![CDATA[<p>[...] Dang you, Mike Keyes for beating me to the punch on this post! Share with the world:These icons link to social bookmarking sites where readers can share and discover new web pages. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WA Detector Bookmarklet Update by Robbin Steif</title>
		<link>http://blog.keyes.us/2008/01/04/wa-detector-update/comment-page-1/#comment-134</link>
		<dc:creator>Robbin Steif</dc:creator>
		<pubDate>Sat, 05 Jan 2008 18:49:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.keyes.us/2008/01/04/wa-detector-update/#comment-134</guid>
		<description>Thank you so much for doing this update and then fixing it so that it works. I use your Detector all the time.</description>
		<content:encoded><![CDATA[<p>Thank you so much for doing this update and then fixing it so that it works. I use your Detector all the time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

