<?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: Snap Rides Click Fraud&apos;s Coattails</title>
	<atom:link href="http://staging.blog.biakelsey.com/index.php/2005/07/20/Snap-Rides-Click-Frauds-Coattails/feed/" rel="self" type="application/rss+xml" />
	<link>http://staging.blog.biakelsey.com/index.php/2005/07/20/Snap-Rides-Click-Frauds-Coattails/</link>
	<description>LOCAL MEDIA WATCH. The Nexus of All Things Local</description>
	<lastBuildDate>Mon, 01 Jun 2015 22:23:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.39</generator>
	<item>
		<title>By: Greg</title>
		<link>http://staging.blog.biakelsey.com/index.php/2005/07/20/Snap-Rides-Click-Frauds-Coattails/comment-page-1/#comment-337</link>
		<dc:creator><![CDATA[Greg]]></dc:creator>
		<pubDate>Wed, 20 Jul 2005 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-337</guid>
		<description><![CDATA[PPCall isn&apos;t going to display an actual phone number -- it requires a unique phone number for tracking purposes. Billing would be automatic and based on call duration; merchants can argue with vendors later about whether charges were justified. But the system isn&apos;t based on whether the leads actually turned into business. 

The merchant temptation in the PPCall scenario is &quot;call me back on this number&quot; to beat the system; however, they generally won&apos;t have any way of knowing where the call came from until the tracking data are delivered later or reviewed later by the merchant online.]]></description>
		<content:encoded><![CDATA[<p>PPCall isn&apos;t going to display an actual phone number &#8212; it requires a unique phone number for tracking purposes. Billing would be automatic and based on call duration; merchants can argue with vendors later about whether charges were justified. But the system isn&apos;t based on whether the leads actually turned into business. </p>
<p>The merchant temptation in the PPCall scenario is &quot;call me back on this number&quot; to beat the system; however, they generally won&apos;t have any way of knowing where the call came from until the tracking data are delivered later or reviewed later by the merchant online.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D</title>
		<link>http://staging.blog.biakelsey.com/index.php/2005/07/20/Snap-Rides-Click-Frauds-Coattails/comment-page-1/#comment-336</link>
		<dc:creator><![CDATA[D]]></dc:creator>
		<pubDate>Tue, 19 Jul 2005 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-336</guid>
		<description><![CDATA[SME self reporting/integrity also comes into play in the Pay Per Call model; Calls may be logged, but is business generated tracked/reported? The SME instinct to under estimate/report business generated through directional advertising helps fuel directional properties&apos; quest to develop tracking systems, such tracking systems, however, may not always be in the complete long term interest of SMEs. The Pay Per Call system, for example, does not always display SMEsâ€™ real phone numbers.]]></description>
		<content:encoded><![CDATA[<p>SME self reporting/integrity also comes into play in the Pay Per Call model; Calls may be logged, but is business generated tracked/reported? The SME instinct to under estimate/report business generated through directional advertising helps fuel directional properties&apos; quest to develop tracking systems, such tracking systems, however, may not always be in the complete long term interest of SMEs. The Pay Per Call system, for example, does not always display SMEsâ€™ real phone numbers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
