Archive for the ‘RTB’ Category
Auctions conducted—impression by impression—inside of 125 milliseconds.
Real time bidding (RTB) holds the promise of making our digital plumbing smart—solving major challenges around media, audience and data fragmentation. But in practice, despite all the promises, and despite all the actually capabilities, most of the time we still have a dumb pipe.

But the market is about to bifurcate—to the supply (RTB Exchanges) and demand sources (Ad Networks, DSPs and Agency Trading Desks) that make the leap to what I call “smart pipe” and to those that get left behind with a “dumb pipe” approach.
For all the talk, many implementations of RTB and the ad technology stack today result in the equivalent of running glorified re-targeting ad networks—user targeting across dark pools of inventory—or other situations that are only marginally better.
For all the press releases and sponsored iMedia presentations proclaiming the newest capabilities, the truth is the ad technology stack is super complicated and it takes both good intentions and coordinated work up and down the supply chain—publisher, RTB supply, RTB buyer, ad servers, ad creative producers—to deliver a smart pipe. Way too much exchange traded media gets lost in a sea of iFrames, entering a vast black hole that drives down its value for both the brand (ex.: I care about environment and audience) and the direct response (ex.: I care about ones and zeros—data to optimize) buyer.
Who is culpable in regards to our industry’s dumb pipe syndrome?
There is plenty of blame to hand out:
- Publishers need to work with exchanges to provide a clear view into the source of the impression.
- Exchanges need to pass this transparency along with data about the page, ad slot and user to its bidders to provide the greatest liquidity and demand for each impression.
- RTB Buyers (ad networks, DSPs) must accept and consume this data to create value by offering advanced targeting, optimization and reporting/insights.
- Agency Trading Desks and operating agencies need to develop & expand the workforce that can utilize this value; must be able to explain and convey this value to clients and must capture client budget that is about media investment not only cost reduction.
- Clients need to demand smart solutions and put their money where their mouth is. Programmatic buying can deliver a full suite of value from direct response to brand—clients need to understand, demand and fund these smart pipe capabilities when working with their suppliers.
Everyone in the supply chain has a job to do to deliver the smart pipe and some companies are further along than others. Anyone in this supply chain can drop in one or two Iframes, or not catch and pass along an important piece of data, and there is diminished value for everyone.
The good news is many in the ad tech stack are stepping up. In addition to specific company-to-company cooperation, initiatives through the IAB Networks & Exchanges committee and OpenRTB will assist in facilitating the smart pipe approach.
I declare 2012 the year of the SMART PIPE!
SSPs are Dead.
Admeld. Dead.
Pubmatic. Dead.
Rubicon. Dead.
Niedermeyer. Dead. (anyone?)

SSPs (supply side platforms) began to emerge in 2007 to help large publishers “YIELD OPTIMIZE” demand from ad networks—all 400 of them.
It was a great pitch: Mr. Big Publisher, you utilize 20-70% of your inventory to make 80% of your revenue from direct sales. Let me manage all the second channel (remnant) demand via ad networks—you’ll make more because I the SSP know how to “YIELD OPTIMIZE” among this crazy world of 400 ad networks.
The YIELD OPTIMIZATION business—the reason for the creation of SSPs—is Dead. Finito. Over.
Ben, Rajeev, Frank—before you lunge for the phone (or lunge at me), I’m actually going to explain to everyone your bright future. Bankers please get your pencils ready.
SSPs are now Exchanges. There has been a buzz word merger. Someone tell Terry Kawaja so he can adjust his bubble chart (bubble chart, get it?).
Effective immediately all digital media executives are to cease and desist all usage of the acronym S.S.P. and use the fully formed noun “Exchange”.
Optimization has moved to the buy side.
Real Time Bidding enabled supply (otherwise known as Exchange) allows all RTB buyers—ad networks, DSPs, agency trading desks—to bring their own optimization to the table. RTB caused the death of SSPs and their emergence as exchanges.
In fact at a recent conference, Admeld’s own Ben Barokas said his business has shifted from 15% RTB/85% YIELD OPTIMIZATION in January 2010 to 54% RTB/46% YIELD OPTIMIZATION in January 2011. At best, yield optimization is a legacy business among SSPs.
OLD: SSPs
Admeld
Pubmatic
Rubicon
OLD: Exchanges
AdX (Google)
CONTEXTWEB
OpenX
NEW: Merger to Exchanges—all RTB Enabled
Admeld
AdX (Google)
CONTEXTWEB
OpenX
Pubmatic
Rubicon
Google did not buy Admeld the SSP for $400 million. Google bought Admeld the Exchange for $400 million.
See my earlier post Google, Admeld & The Need for Diabolical Liquidity.
What do you think? Leave a comment below or contact me.
[These views are my own. If you want to speak with CONTEXTWEB in regards to RTB, go here.]
Thanks to DOH for the movie reference.
Recently an industry peer asked me if I was concerned that Google was diabolical.

My concern is just the opposite—that Google’s peers—Microsoft, Yahoo! and others—are not being diabolical enough. We need more diabolical liquidity; otherwise we will have a display advertising monopoly. And that’s only fun for one person at the party. Google has been building its dominance in display in plain sight yet few seem to understand how to counterbalance its cunning and impactful moves.
The Admeld transaction will be yet another example of this. Pundits will say Google bought publisher relationships and Admeld’s yield optimization service for large publishers. Now Michael and Ben and their team at Admeld have done an excellent job of pulling in top, large publishers such as CBS, IDG Tech Network, NBC, Quadrant One and Weather.com, but this misses the point entirely.
Google bought QPS volume, period. [QPS is queries per second, a measure of liquidity or volume of display ads being offered via real time bidding or RTB.]
It’s the QPS, Stupid…
Based on my own estimates, Google represents between 50-90% of display volume (QPS) being purchased by DSPs, ad networks and agency trading desks on a RTB basis. Incremental QPS volume comes from the SSPs (Admeld, Pubmatic, Rubicon), Microsoft (new to the game via Appnexus), my company CONTEXTWEB, OpenX and a few others.
Beyond Google, Admeld (although much, much smaller) is the major contributor of QPS volume to most RTB buyers, although this may soon be displaced by Microsoft with its recent RTB enablement of all non-guaranteed supply by Appnexus.
So why did Google buy Admeld?
- QPS volume? Yes.
- Publisher relationships? Sorta. But remember, people in New York like relationships and people in California like scale. Google is headquartered in California, and they are winning.
- Private exchange? Kinda. I spoke with four large publishers just yesterday active in private exchange area and all are pre-revenue. Not worth $400 million.
- Yield optimization? No. RTB makes yield optimization a legacy business. RTB moves the optimization to the buy side. RTB makes all SSPs into ad exchanges (RTB supply enablement).
Now this morning the phones are burning at Yahoo!, Microsoft and other companies—should we buy a SSP (only two left, get ‘em while they are hot…)? Wrong question.
Here are some of the right questions Yahoo!, Microsoft and others should be asking:
- How do I increase my overall QPS volume share from RTB buyers (ad networks, DSPs, agency trading desks)?
- How can I increase the clearing percentage, clearing price & overall liquidity of my existing QPS volume based on the evolving needs of RTB buyers?
- Where is the vast majority of Google display QSP share coming from? (hint: not SSP-type customers)
- How do I make my RTB monetization offer relevant to large publishers and/or quality supply?
I’ll address these questions in future posts. What do you think? Leave a comment below or contact me.
[These views are my own. If you want to speak with CONTEXTWEB in regards to RTB, go here.]