<?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: Turn Announces Agency Holding Company Client: Omnicom Media Group; Upgrades Platform Features</title>
	<atom:link href="http://www.adexchanger.com/ad-exchange-news/turn-announces-agency-holding-company-client-omnicom-media-group-also-upgrades-platform-features/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adexchanger.com/ad-exchange-news/turn-announces-agency-holding-company-client-omnicom-media-group-also-upgrades-platform-features/</link>
	<description>Digital media optimization news and discussion website.</description>
	<lastBuildDate>Fri, 10 Feb 2012 23:33:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Philip Smolin</title>
		<link>http://www.adexchanger.com/ad-exchange-news/turn-announces-agency-holding-company-client-omnicom-media-group-also-upgrades-platform-features/#comment-4522</link>
		<dc:creator>Philip Smolin</dc:creator>
		<pubDate>Wed, 27 Jan 2010 01:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=14420#comment-4522</guid>
		<description>Mea culpa!

Turn&#039;s policy is to never use a client&#039;s confidential data when providing screen shots.  In the original version posted here, an outlying data point was inadvertently used that showed a high CPA for PubMatic.  This was in no way indicative of the performance our clients typically see with PubMatic (to the contrary, actually), and AdExchanger was nice enough to remove the original screen shot at our request. Apologies for any confusion.

Philip
Turn Inc.</description>
		<content:encoded><![CDATA[<p>Mea culpa!</p>
<p>Turn's policy is to never use a client's confidential data when providing screen shots.  In the original version posted here, an outlying data point was inadvertently used that showed a high CPA for PubMatic.  This was in no way indicative of the performance our clients typically see with PubMatic (to the contrary, actually), and AdExchanger was nice enough to remove the original screen shot at our request. Apologies for any confusion.</p>
<p>Philip<br />
Turn Inc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Schumacher</title>
		<link>http://www.adexchanger.com/ad-exchange-news/turn-announces-agency-holding-company-client-omnicom-media-group-also-upgrades-platform-features/#comment-4518</link>
		<dc:creator>Ryan Schumacher</dc:creator>
		<pubDate>Tue, 26 Jan 2010 17:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=14420#comment-4518</guid>
		<description>Some interesting data in this post.  I&#039;m curious why Pubmatic is backing out to such a high CPA vs the rest.</description>
		<content:encoded><![CDATA[<p>Some interesting data in this post.  I'm curious why Pubmatic is backing out to such a high CPA vs the rest.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

