<?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: The Rubicon Project manifesto is not a silver bullet for publishers</title>
	<atom:link href="http://www.keplarllp.com/blog/2010/02/the-rubicon-project-manifesto-is-not-a-silver-bullet-for-publishers/feed" rel="self" type="application/rss+xml" />
	<link>http://www.keplarllp.com/blog/2010/02/the-rubicon-project-manifesto-is-not-a-silver-bullet-for-publishers</link>
	<description>Blogging from the team at Keplar LLP</description>
	<lastBuildDate>Tue, 20 Sep 2011 14:56:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: kenny</title>
		<link>http://www.keplarllp.com/blog/2010/02/the-rubicon-project-manifesto-is-not-a-silver-bullet-for-publishers/comment-page-1#comment-2444</link>
		<dc:creator>kenny</dc:creator>
		<pubDate>Wed, 18 Aug 2010 15:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.keplarllp.com/blog/?p=370#comment-2444</guid>
		<description>Great point made. I didn&#039;t read the manifesto yet but according to previous Rubicon market reports (e.g., 2009 ones), they appear to focus on upper-nonpremium add slots. In other words, the stuff that the sales teams can&#039;t get to because they are busy dealing with unique cases like that FHM homepage you mentioned.

Maybe Rubicon&#039;s messaging has changed. I don&#039;t know but check out their older reports.</description>
		<content:encoded><![CDATA[<p>Great point made. I didn&#8217;t read the manifesto yet but according to previous Rubicon market reports (e.g., 2009 ones), they appear to focus on upper-nonpremium add slots. In other words, the stuff that the sales teams can&#8217;t get to because they are busy dealing with unique cases like that FHM homepage you mentioned.</p>
<p>Maybe Rubicon&#8217;s messaging has changed. I don&#8217;t know but check out their older reports.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JT</title>
		<link>http://www.keplarllp.com/blog/2010/02/the-rubicon-project-manifesto-is-not-a-silver-bullet-for-publishers/comment-page-1#comment-889</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Tue, 02 Mar 2010 01:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.keplarllp.com/blog/?p=370#comment-889</guid>
		<description>Good question Yali. Best way to think about it is: Rubicon&#039;s customer is the publisher. The publisher&#039;s customer is the advertiser. Our job is to give our customers the technology to effectively, effectively and profitably service their customers.

We don&#039;t work directly with advertisers-- but we do provide publishers with the tools and technology to do so. Our platform also allows publishers to connect in to the different sources of demand through the REVV Marketplace. 

In the short term, we will probably see more people in the value chain. The traditional tech platforms have done a poor job innovating. Over the long hall, we think that those offering the full platform will be the ones who win.</description>
		<content:encoded><![CDATA[<p>Good question Yali. Best way to think about it is: Rubicon&#8217;s customer is the publisher. The publisher&#8217;s customer is the advertiser. Our job is to give our customers the technology to effectively, effectively and profitably service their customers.</p>
<p>We don&#8217;t work directly with advertisers&#8211; but we do provide publishers with the tools and technology to do so. Our platform also allows publishers to connect in to the different sources of demand through the REVV Marketplace. </p>
<p>In the short term, we will probably see more people in the value chain. The traditional tech platforms have done a poor job innovating. Over the long hall, we think that those offering the full platform will be the ones who win.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yali</title>
		<link>http://www.keplarllp.com/blog/2010/02/the-rubicon-project-manifesto-is-not-a-silver-bullet-for-publishers/comment-page-1#comment-876</link>
		<dc:creator>Yali</dc:creator>
		<pubDate>Tue, 23 Feb 2010 09:10:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.keplarllp.com/blog/?p=370#comment-876</guid>
		<description>Thanks JT - I was under the impression that Rubicon provided publishers with direct access to multiple different demand sources through your solution.  Is that right - only none of those sources are advertisers themselves?  (Rather, all those sources are intermediaries like ad networks.)  If so, the issue becomes - are there too many people in the value chain to enable the publisher / advertiser to collectively deliver an optimal, bespoke solution?  (Because you have to enforce some kind of standardisation to ensure everyone can plays together?)  

If that isn&#039;t the case, and you&#039;re provided publishers with an expanded toolset they can take use with any demand source to work on an optimal solution with each advertiser, I look forward to getting a chance to see those how those tools work myself!  There&#039;s certainly a huge amount of scope for the tools that are currently available to be improved upon.</description>
		<content:encoded><![CDATA[<p>Thanks JT &#8211; I was under the impression that Rubicon provided publishers with direct access to multiple different demand sources through your solution.  Is that right &#8211; only none of those sources are advertisers themselves?  (Rather, all those sources are intermediaries like ad networks.)  If so, the issue becomes &#8211; are there too many people in the value chain to enable the publisher / advertiser to collectively deliver an optimal, bespoke solution?  (Because you have to enforce some kind of standardisation to ensure everyone can plays together?)  </p>
<p>If that isn&#8217;t the case, and you&#8217;re provided publishers with an expanded toolset they can take use with any demand source to work on an optimal solution with each advertiser, I look forward to getting a chance to see those how those tools work myself!  There&#8217;s certainly a huge amount of scope for the tools that are currently available to be improved upon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JT</title>
		<link>http://www.keplarllp.com/blog/2010/02/the-rubicon-project-manifesto-is-not-a-silver-bullet-for-publishers/comment-page-1#comment-874</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Mon, 22 Feb 2010 21:16:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.keplarllp.com/blog/?p=370#comment-874</guid>
		<description>Hi Alex-- great post.

I think you&#039;re dead right about the importance of making online a successful channel for branding. It definitely falls short of its potential today. And publishers must take the lead in solving that.

A couple things-- we don&#039;t work directly with advertisers. Publishers, 3rd party sales houses, ad networks or exchanges do the selling/interfacing with publishers.

We completely agree context (the where) matters. That&#039;s why we think publishers are best positioned to serve the advertisers needs.

Need to get back to a meeting, but really enjoyed reading your comments.

JT
Rubicon Project</description>
		<content:encoded><![CDATA[<p>Hi Alex&#8211; great post.</p>
<p>I think you&#8217;re dead right about the importance of making online a successful channel for branding. It definitely falls short of its potential today. And publishers must take the lead in solving that.</p>
<p>A couple things&#8211; we don&#8217;t work directly with advertisers. Publishers, 3rd party sales houses, ad networks or exchanges do the selling/interfacing with publishers.</p>
<p>We completely agree context (the where) matters. That&#8217;s why we think publishers are best positioned to serve the advertisers needs.</p>
<p>Need to get back to a meeting, but really enjoyed reading your comments.</p>
<p>JT<br />
Rubicon Project</p>
]]></content:encoded>
	</item>
</channel>
</rss>

