<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Engine Ready &#187; life time value</title>
	<atom:link href="http://blog.engineready.com/tag/life-time-value/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.engineready.com</link>
	<description>Search Engine Marketing Blog</description>
	<lastBuildDate>Tue, 03 Jan 2012 19:19:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Why 1 CPA Target Is Not Enough</title>
		<link>http://blog.engineready.com/why-1-cpa-target-is-not-enough/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=why-1-cpa-target-is-not-enough</link>
		<comments>http://blog.engineready.com/why-1-cpa-target-is-not-enough/#comments</comments>
		<pubDate>Fri, 19 Sep 2008 21:41:47 +0000</pubDate>
		<dc:creator>Brian Lewis</dc:creator>
				<category><![CDATA[Online Marketing]]></category>
		<category><![CDATA[cpa]]></category>
		<category><![CDATA[life time value]]></category>
		<category><![CDATA[search marketing]]></category>

		<guid isPermaLink="false">http://blog.engineready.com/?p=123</guid>
		<description><![CDATA[Many marketers establish a cost per acquisition (or cost per order) metric as a key performance indicator, and use that as one of the measurements to gauge the effectiveness of their search campaign. Computing a target CPA involves understanding what your average lead or order value is (from a search campaign), less the cost of [...]]]></description>
		<wfw:commentRss>http://blog.engineready.com/why-1-cpa-target-is-not-enough/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

