<?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: Defragmenting Media With Real-Time Bidding</title>
	<atom:link href="http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/</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: Zach Coelius</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4391</link>
		<dc:creator>Zach Coelius</dc:creator>
		<pubDate>Tue, 12 Jan 2010 22:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4391</guid>
		<description>Good questions Anton.  I am not sure how standardization will happen officially.  We are already seeing an unofficial process where everyone is copying Google and are making their systems the same in order to make it easier for DSPs like us to plug in.  Thankfully the implementation is straight forward enough that I only know one small company that has a different enough RTB system to cause a problem.  Everyone else is pretty much the same.

Though you are wrong about text ads being RTB.  One of the core elements to RTB is being able to know who the user is and to bid and target based off user data; text ads are not user targeted at all.    

John, when are you going to make a matrix like Anton is asking for?  Maybe something like the GCA Savvian map?</description>
		<content:encoded><![CDATA[<p>Good questions Anton.  I am not sure how standardization will happen officially.  We are already seeing an unofficial process where everyone is copying Google and are making their systems the same in order to make it easier for DSPs like us to plug in.  Thankfully the implementation is straight forward enough that I only know one small company that has a different enough RTB system to cause a problem.  Everyone else is pretty much the same.</p>
<p>Though you are wrong about text ads being RTB.  One of the core elements to RTB is being able to know who the user is and to bid and target based off user data; text ads are not user targeted at all.    </p>
<p>John, when are you going to make a matrix like Anton is asking for?  Maybe something like the GCA Savvian map?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4368</link>
		<dc:creator>Anton</dc:creator>
		<pubDate>Mon, 11 Jan 2010 23:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4368</guid>
		<description>Glad we agree Zach, so lets call it a paradigm shift :) - essentially text was RTB from the beginning (at least for advertisers, though APIs are not readily compatible), so now its time of display and publishers. Who do you think will be first to come up with something uniform? Standards bodies move slowly, in industry IAB could lead, but I think they&#039;ve lost power over years and not very up to speed on many developments. Commercial adoption with agencies and publishers seems to be the key, which leaves us pretty much with Doubleclick &amp; Atlas, but not sure how much invested they are into RTB (though haven&#039;t followed them recently). On a similar note - do you know is there somewhere a list of platforms which support RTB and some kind of compatibility matrix?</description>
		<content:encoded><![CDATA[<p>Glad we agree Zach, so lets call it a paradigm shift <img src='http://www.adexchanger.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  - essentially text was RTB from the beginning (at least for advertisers, though APIs are not readily compatible), so now its time of display and publishers. Who do you think will be first to come up with something uniform? Standards bodies move slowly, in industry IAB could lead, but I think they've lost power over years and not very up to speed on many developments. Commercial adoption with agencies and publishers seems to be the key, which leaves us pretty much with Doubleclick &amp; Atlas, but not sure how much invested they are into RTB (though haven't followed them recently). On a similar note - do you know is there somewhere a list of platforms which support RTB and some kind of compatibility matrix?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach Coelius</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4363</link>
		<dc:creator>Zach Coelius</dc:creator>
		<pubDate>Mon, 11 Jan 2010 18:46:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4363</guid>
		<description>Anton,
   I can&#039;t agree more.  When I use the term standard I mean it in the loose sense that the industry generally understands what the format of an RTB call and response should be and it is pretty easy to integrate into multiple partners with RTB.  That general understanding takes us a long way from where we were before with completely different proprietary apis like the ones you mentioned at Adwords and Right Media.  I think that as the industry settles in with RTB over the next year we will certainly see a push for a standards body.   

Zach</description>
		<content:encoded><![CDATA[<p>Anton,<br />
   I can't agree more.  When I use the term standard I mean it in the loose sense that the industry generally understands what the format of an RTB call and response should be and it is pretty easy to integrate into multiple partners with RTB.  That general understanding takes us a long way from where we were before with completely different proprietary apis like the ones you mentioned at Adwords and Right Media.  I think that as the industry settles in with RTB over the next year we will certainly see a push for a standards body.   </p>
<p>Zach</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4362</link>
		<dc:creator>Anton</dc:creator>
		<pubDate>Mon, 11 Jan 2010 18:35:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4362</guid>
		<description>Zach, I&#039;ve read your RTB articles and coming from a technical background I think that presenting the concept alone doesn&#039;t qualify for a standard. In Internet terms, would be great to come up with RFC or similar for such process and get some kind of standard body to agree a protocol for connecting all these systems. After all there some APIs around (Rightmedia, Google Adwords API) plus many &quot;client&quot; systems which could benefit from a single standard. So that an Adops manager plugins yet another RTB/exchange service into his/her system with a few clicks and can start tapping into more inventory/advertisers.</description>
		<content:encoded><![CDATA[<p>Zach, I've read your RTB articles and coming from a technical background I think that presenting the concept alone doesn't qualify for a standard. In Internet terms, would be great to come up with RFC or similar for such process and get some kind of standard body to agree a protocol for connecting all these systems. After all there some APIs around (Rightmedia, Google Adwords API) plus many "client" systems which could benefit from a single standard. So that an Adops manager plugins yet another RTB/exchange service into his/her system with a few clicks and can start tapping into more inventory/advertisers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach Coelius</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4320</link>
		<dc:creator>Zach Coelius</dc:creator>
		<pubDate>Fri, 08 Jan 2010 22:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4320</guid>
		<description>Oh yes, we are about to see a wild scramble as everyone figures out that their old business model is kaput...   It will be a ton of fun this year.</description>
		<content:encoded><![CDATA[<p>Oh yes, we are about to see a wild scramble as everyone figures out that their old business model is kaput...   It will be a ton of fun this year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Mendez</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4318</link>
		<dc:creator>Jonathan Mendez</dc:creator>
		<pubDate>Fri, 08 Jan 2010 22:00:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4318</guid>
		<description>Zach,

You&#039;re unquestionably right. The serving performance and data capture alone will ensure everyone will plug into it -- not to mention the ad performance/ROAS benefits that can be delivered for really smart systems. I have the strong suspicion someone&#039;s going to get disintermediated in all of this, but I&#039;m not yet sure who, why and what the consequences will be. Will be fun to watch over the next few years, won&#039;t it?</description>
		<content:encoded><![CDATA[<p>Zach,</p>
<p>You're unquestionably right. The serving performance and data capture alone will ensure everyone will plug into it -- not to mention the ad performance/ROAS benefits that can be delivered for really smart systems. I have the strong suspicion someone's going to get disintermediated in all of this, but I'm not yet sure who, why and what the consequences will be. Will be fun to watch over the next few years, won't it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach Coelius</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4317</link>
		<dc:creator>Zach Coelius</dc:creator>
		<pubDate>Fri, 08 Jan 2010 20:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4317</guid>
		<description>Happy New Years Jonathan, I hope things are going well on your end.

My argument is simply that as RTB becomes an industry standard, every scale media company and media aggregator (ie networks like Adsense or pub side optimizers like AdMeld, Pubmatic, Yeildbuild, etc) will offer it.  Because RTB is a standard, that makes it easy for demand side platforms to plug into all the providers and provide unified buying power across a large percentage of the web and eventually video, DOOH, mobile and all other digital media.  You can think of RTB as functionally like the connection points that tie it all together. I think that because RTB is open, and anyone can deploy it, that we will see a very rapid industry adoption as the virtuous cycle kicks in.    Just think what would happen when RTB access is available for 50% or more of all digital media.  At that scale things get really interesting.</description>
		<content:encoded><![CDATA[<p>Happy New Years Jonathan, I hope things are going well on your end.</p>
<p>My argument is simply that as RTB becomes an industry standard, every scale media company and media aggregator (ie networks like Adsense or pub side optimizers like AdMeld, Pubmatic, Yeildbuild, etc) will offer it.  Because RTB is a standard, that makes it easy for demand side platforms to plug into all the providers and provide unified buying power across a large percentage of the web and eventually video, DOOH, mobile and all other digital media.  You can think of RTB as functionally like the connection points that tie it all together. I think that because RTB is open, and anyone can deploy it, that we will see a very rapid industry adoption as the virtuous cycle kicks in.    Just think what would happen when RTB access is available for 50% or more of all digital media.  At that scale things get really interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Mendez</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4315</link>
		<dc:creator>Jonathan Mendez</dc:creator>
		<pubDate>Fri, 08 Jan 2010 16:43:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4315</guid>
		<description>Zac,

Great to get your leading edge perspective here. There&#039;s no question RTB insanely optimizes the workflow but I&#039;m having a hard time getting my head around how the scale needed for it to be effective works with the real fragmentation that caused the inefficiency in first place. The fragmentation of people&#039;s interests and intent. Thoughts?</description>
		<content:encoded><![CDATA[<p>Zac,</p>
<p>Great to get your leading edge perspective here. There's no question RTB insanely optimizes the workflow but I'm having a hard time getting my head around how the scale needed for it to be effective works with the real fragmentation that caused the inefficiency in first place. The fragmentation of people's interests and intent. Thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Article on AdExchanger &#8250; Triggit</title>
		<link>http://www.adexchanger.com/data-driven-thinking/defragmenting-media-with-real-time-bidding/#comment-4302</link>
		<dc:creator>New Article on AdExchanger &#8250; Triggit</dc:creator>
		<pubDate>Thu, 07 Jan 2010 18:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.adexchanger.com/?p=13225#comment-4302</guid>
		<description>[...] today about RTB and the promise it holds for addressing media fragmentation. You can find it here. Happy New [...]</description>
		<content:encoded><![CDATA[<p>[...] today about RTB and the promise it holds for addressing media fragmentation. You can find it here. Happy New [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

