<?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: Google Fights Back at Inflated Click-Fraud Studies</title>
	<atom:link href="http://www.marketingpilgrim.com/2006/08/google-fights-back-at-inflated-click-fraud-studies.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.marketingpilgrim.com/2006/08/google-fights-back-at-inflated-click-fraud-studies.html</link>
	<description>Internet Marketing News</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:00:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Andrey Milyan</title>
		<link>http://www.marketingpilgrim.com/2006/08/google-fights-back-at-inflated-click-fraud-studies.html/comment-page-1#comment-626</link>
		<dc:creator>Andrey Milyan</dc:creator>
		<pubDate>Wed, 09 Aug 2006 02:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/wp_import/2006/08/google-fights-back-at-inflated-click-fraud-studies.htm#comment-626</guid>
		<description>Correction, Andy. Google is not attacking the companies releasing click fraud studies. It is attacking the click fraud monitoring services. Instead of concentrating on how to deal with the click fraud problem, Google is attacking the sources suggesting that there is a problem.

In the study Google decides to pick and choose the problems of the three services by attributing the problems of one to the rest. For example, page reload issue was reported only in one service while it was attributed to all three.

As far as the back button issue goes, give me a break. Most of these services need at least 5-7 clicks to report the visitor as fraudulent. Even if some of them do make a mistake of counting back button visits as another click, how many times do you need to hit &quot;back&quot; and &quot;forward&quot; buttons in order to trigger the click fraud warning?

Now let&#039;s look at the issue of confusing the ad networks. Each of these services works the same way: it generates a unique tracking code for each campaign which user then pastes into his pay-per-click campaign. Because each tracking URL is unique, the only way to &quot;mix up&quot; the ad networks is to have the same URL for all your campaigns on all search engines. So this issue results from users making a mistake of using the same URL for multiple ad networks and has nothing to do with the service itself.

These services are not perfect but neither is AdWords, which lacked any kind of fraudulent click reporting up until now. And even now, the definition of &quot;invalid click&quot; is not very clear.

Third party monitoring services need to exist in order to keep Google honest, even if they are not always 100% accurate.</description>
		<content:encoded><![CDATA[<p>Correction, Andy. Google is not attacking the companies releasing click fraud studies. It is attacking the click fraud monitoring services. Instead of concentrating on how to deal with the click fraud problem, Google is attacking the sources suggesting that there is a problem.</p>
<p>In the study Google decides to pick and choose the problems of the three services by attributing the problems of one to the rest. For example, page reload issue was reported only in one service while it was attributed to all three.</p>
<p>As far as the back button issue goes, give me a break. Most of these services need at least 5-7 clicks to report the visitor as fraudulent. Even if some of them do make a mistake of counting back button visits as another click, how many times do you need to hit &#8220;back&#8221; and &#8220;forward&#8221; buttons in order to trigger the click fraud warning?</p>
<p>Now let&#8217;s look at the issue of confusing the ad networks. Each of these services works the same way: it generates a unique tracking code for each campaign which user then pastes into his pay-per-click campaign. Because each tracking URL is unique, the only way to &#8220;mix up&#8221; the ad networks is to have the same URL for all your campaigns on all search engines. So this issue results from users making a mistake of using the same URL for multiple ad networks and has nothing to do with the service itself.</p>
<p>These services are not perfect but neither is AdWords, which lacked any kind of fraudulent click reporting up until now. And even now, the definition of &#8220;invalid click&#8221; is not very clear.</p>
<p>Third party monitoring services need to exist in order to keep Google honest, even if they are not always 100% accurate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

