<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: SEOmoz - An Interview About Compete.com Metrics</title>
	<link>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/</link>
	<description>web insights powered by over 2 million U.S. online consumers</description>
	<pubDate>Mon, 06 Oct 2008 19:24:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Mexico seo</title>
		<link>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/#comment-362799</link>
		<dc:creator>Mexico seo</dc:creator>
		<pubDate>Thu, 21 Feb 2008 22:08:41 +0000</pubDate>
		<guid>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/#comment-362799</guid>
		<description>Analytics are fundamental for any website, specially if you want to have a competitive site, this is a very extensive and interesting article, besides, your toolbar seems to have nice features.

Regards.</description>
		<content:encoded><![CDATA[<p>Analytics are fundamental for any website, specially if you want to have a competitive site, this is a very extensive and interesting article, besides, your toolbar seems to have nice features.</p>
<p>Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Profesionalnet</title>
		<link>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/#comment-331998</link>
		<dc:creator>Profesionalnet</dc:creator>
		<pubDate>Mon, 04 Feb 2008 09:33:55 +0000</pubDate>
		<guid>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/#comment-331998</guid>
		<description>We thought it was a very good tool, lacking in Spanish language, for example. We have seen and we want to continue to use and testing this useful tool. 
From Spain. A very cordial greeting. 
www.profesionalnet.net</description>
		<content:encoded><![CDATA[<p>We thought it was a very good tool, lacking in Spanish language, for example. We have seen and we want to continue to use and testing this useful tool.<br />
From Spain. A very cordial greeting.<br />
<a href="http://www.profesionalnet.net" rel="nofollow">http://www.profesionalnet.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Opi</title>
		<link>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/#comment-331320</link>
		<dc:creator>Adam Opi</dc:creator>
		<pubDate>Mon, 04 Feb 2008 05:52:22 +0000</pubDate>
		<guid>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/#comment-331320</guid>
		<description>great comment from the post:

&lt;blockquote&gt;Is it something where you can say (like Avinash Kaushik suggests doing), well, I don't have full confidence in the data, and I don't even have 50% confidence -- 

But maybe I have 10% confidence, and I can still make a (small) decision based on that. 
&lt;/blockquote&gt;


from the post:

&lt;blockquote&gt;You mentioned that Compete will attempt to verify and reconcile its numbers against what many of the larger sites listed are reporting. Can you talk about that process and what's entailed? This seems like something that might give Compete a real competitive edge - do you publicize when these connections are complete? How many have you done over the past year?

The process is somewhat ad hoc. Essentially when a company or site owner contacts us about discrepancies between their data and our own or even between our data and another third party source we look at the variation to determine if the gap is substantial or not. If it does look substantial we dive into a couple of areas. First we look across our 10+ different sources of data to see if there are any panel bias issues. For instance does a certain type of panel have abnormally low statistics for the given site. If we do see this than we can apply an adjustment to our normalization process that accounts for this. If this does not address the issue we then take a look at external factors that might address the issue.

In most cases if we can’t identify a normalization adjustment we can generally find an external factor that at least rationalizes the issue. At the end of the process there is really no “public” announcement or anything of that kind. Over the past year or so we have probably gone through this process for at least 50 domains. The bottom line is that we don’t simply change the numbers to match the sites internal numbers. We look for a logic explanation as to why our projection and normalization process is generating different values and adjust as necessary. 
&lt;/blockquote&gt;

i recommend reading the interview. learnt a lot.</description>
		<content:encoded><![CDATA[<p>great comment from the post:</p>
<blockquote><p>Is it something where you can say (like Avinash Kaushik suggests doing), well, I don&#8217;t have full confidence in the data, and I don&#8217;t even have 50% confidence &#8212; </p>
<p>But maybe I have 10% confidence, and I can still make a (small) decision based on that.
</p></blockquote>
<p>from the post:</p>
<blockquote><p>You mentioned that Compete will attempt to verify and reconcile its numbers against what many of the larger sites listed are reporting. Can you talk about that process and what&#8217;s entailed? This seems like something that might give Compete a real competitive edge - do you publicize when these connections are complete? How many have you done over the past year?</p>
<p>The process is somewhat ad hoc. Essentially when a company or site owner contacts us about discrepancies between their data and our own or even between our data and another third party source we look at the variation to determine if the gap is substantial or not. If it does look substantial we dive into a couple of areas. First we look across our 10+ different sources of data to see if there are any panel bias issues. For instance does a certain type of panel have abnormally low statistics for the given site. If we do see this than we can apply an adjustment to our normalization process that accounts for this. If this does not address the issue we then take a look at external factors that might address the issue.</p>
<p>In most cases if we can’t identify a normalization adjustment we can generally find an external factor that at least rationalizes the issue. At the end of the process there is really no “public” announcement or anything of that kind. Over the past year or so we have probably gone through this process for at least 50 domains. The bottom line is that we don’t simply change the numbers to match the sites internal numbers. We look for a logic explanation as to why our projection and normalization process is generating different values and adjust as necessary.
</p></blockquote>
<p>i recommend reading the interview. learnt a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Search◆ Engines WEB</title>
		<link>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/#comment-331311</link>
		<dc:creator>Search◆ Engines WEB</dc:creator>
		<pubDate>Mon, 04 Feb 2008 05:44:52 +0000</pubDate>
		<guid>http://blog.compete.com/2008/02/03/seomoz-an-interview-about-competecom-metrics/#comment-331311</guid>
		<description>&lt;blockquote&gt;&lt;i&gt;///If you compare our data and the SELand data to what Compete, Quantcast or Alexa are reporting, you can see how tragically inaccurate those services are. Sadly, that's no anomally. Everytime I get access to a client's visit data, I'm always curious to check the three and have not once found accuracy, even on a relative basis. Third party traffic metrics still have a very, very long way to go&lt;/i&gt;&lt;/blockquote&gt;

http://www.seomoz.org/blog/seomozs-stats-for-2007</description>
		<content:encoded><![CDATA[<blockquote><p><i>///If you compare our data and the SELand data to what Compete, Quantcast or Alexa are reporting, you can see how tragically inaccurate those services are. Sadly, that&#8217;s no anomally. Everytime I get access to a client&#8217;s visit data, I&#8217;m always curious to check the three and have not once found accuracy, even on a relative basis. Third party traffic metrics still have a very, very long way to go</i></p></blockquote>
<p><a href="http://www.seomoz.org/blog/seomozs-stats-for-2007" rel="nofollow">http://www.seomoz.org/blog/seomozs-stats-for-2007</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
