{"id":6946,"date":"2022-01-10T20:03:13","date_gmt":"2022-01-10T20:03:13","guid":{"rendered":"https:\/\/wiki.pontiac.media\/?docs=platform-industry-glossary\/pontiac-white-papers\/header-bidding"},"modified":"2022-01-10T20:26:11","modified_gmt":"2022-01-10T20:26:11","slug":"header-bidding","status":"publish","type":"docs","link":"https:\/\/wiki.pontiac.media\/?docs=platform-industry-glossary\/pontiac-white-papers\/header-bidding","title":{"rendered":"Header Bidding"},"content":{"rendered":"\n

When online advertising hit its stride in the 2000\u2019s, DoubleClick \u201cad serving\u201d service became the  premier technology used by publishers to configure their website\u2019s ad space. With  overwhelming market share, this technology continued to grow and balloon into a massive  organization. In 2007 it was purchased by Google. Doubleclick was making $300 million in  revenue at that point, primarily from the publisher technology. Doubleclick for Publishers, or  DFP, is a program used by major publishers across the world to set up the targeting schemes  advertisers demand from their publisher partners (see Figure 1). <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

With the advancements of real-time bidding (see \u2018RTB & Programmatic Media\u2019 White Paper),  DFP would allow the publisher to sell the ad on the \u2018Ad Exchange\u2019 via Doubleclick AdExchange  (AdX). This is the ad exchange product produced by Google for publishers to use to sell their ads  in real time with very strong results. Although AdX is not the only exchange in the market.  There are several other competitors to the Doubleclick exchange which publishers can use. <\/p>\n\n\n\n

AdX integrates seamlessly with the DFP. This is not surprising, because they are both produced  by the same company and can build the technology into the same program. But, AdX is not the  only ad exchange on the market. Many other technology players have built exchanges, such as  AppNexus, Index Exchange, Rubicon, Pubmatic, Mopub, Smaato, OpenX. These systems do NOT integrate as seamlessly into DFP. In the below chart they are the \u2018other networks\u2019.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Because of Header Bidding, these other exchanges now seamlessly integrate with AdX, allowing the publisher to give these other exchanges equal opportunity to participate in auction for the ad space.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

How does this impact Demand Side Platforms? <\/strong><\/h4>\n\n\n\n

At the end of the day, the ones most effected by Header Bidding implementation are the  Demand Side Platforms (see \u2018How the Ad Exchange Works\u2019 White Paper). The instantaneous  auction the Demand Side Platform (DSP) responds to happens when the exchange makes the ad  available while the user is loading the webpage. This is the definition of Real-Time bidding and  the technology driving Programmatic advertising. Before header bidding, the SSP would only  auction the ad when their slot was called in the publisher waterfall. Now, each time the page is  loaded, the SSP makes the ad available for auction, even if it rarely is responsible for selling the  ad unit. DSPs must \u2018listen\u2019 or ingest the ad calls from billions of web pages a day. With the  advent of header bidding, now DSPs see 3x \u2013 5x the amount of traffic they saw previously. This  is an increased load on the need for servers to respond to all these available ad units. Many of  the smaller DSPs are having a difficult time keeping up and, in the end, they are not able to see  as many available ad spaces as the used to see.  <\/p>\n\n\n\n

For prospecting campaigns, or video campaigns, this is not a big deal. DSPs can still pick off the  ads they want to target and typically get performance similar to what they saw before header  bidding. But for remarketing campaigns, which are the money-makers in this business, these  smaller DSPs are having a hard time \u2018listening\u2019 to enough inventory to compete with the larger scaled DSPs on remarketing campaigns. <\/p>\n\n\n\n

Another, buyer-be-ware change with the increased use of header bidding is the introduction of  \u2018First-Priced Auctions\u2019. Typically, an SSP would see all the DSP bids, award the ad space to the  highest bidder, but charge them the PRICE OF THE SECOND HIGHEST BID. This was done to  increase competition and buyer\u2019s interest in this technology as it first appeared. As a buyer this  statement made this landscape very intriguing (although, still extremely complicated): \u201cYou will  NEVER pay more than the second highest bidder is willing to pay for each individual ad space\u201d.  It was in the interest of developing a perfect market. Well, things don\u2019t always work out like  that. <\/p>\n\n\n\n

Now, with the need for the exchanges to push the highest price to DFP through the header  auction, they are now passing the price they receive directly from the DSP to the publisher. This  is a \u2018first priced auction\u2019. Or, if as the exchange would justify \u201cwe are taking the highest bid we  saw to increase the publishers CPM\u201d. This is not a bad thing. It does question why we have the  SSP layer at all. But, ignoring that statement, this is ultimately going to drive better pricing for  the publisher who must exist for us to have the ad tech ecosystem at all!<\/p>\n\n\n\n

But, with the increase in first price auctions, DSPs must now build into their technology the\u00a0 ability to identify first-priced auctions versus second price auctions and enable the buyer to\u00a0 correct their bid strategy to avoid getting hurt by this change in auction mechanics.\u00a0<\/p>\n\n\n\n

<\/div>\n\n\n\n

What does this mean for a Trading Desks? <\/strong><\/h4>\n\n\n\n

Well, to be honest, not much. If anything, it is a positive change in the ecosystem. Most trading\u00a0 desk practices license technology from the largest DSPs in the world who have no problem\u00a0 seeing all available bids, even with the increase in header-bidding auctions. Any reputable\u00a0 trading desk, would already have implemented advanced bidding algorithms to drive the\u00a0 strongest cost per acquisition. Whether or not they pass those savings onto their client is a\u00a0 whole other story, hence the shift for a more transparent partner like ProgMechs. In the end,\u00a0 not much changes with this introduction except that publishers are able to make more money\u00a0 through programmatic channels. With that, more publishers make more inventory available,\u00a0 allowing Trading Desks to see more inventory, increase performance, and continue to offer\u00a0 stronger, more \u2018high-impact\u2019 style ad units.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Download this White Paper:<\/p>\n\n\n\n

HeaderBidding<\/a>Download<\/a><\/div>\n\n\n\n

<\/p>\n","protected":false},"author":6,"featured_media":0,"parent":6919,"menu_order":4,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-6946","docs","type-docs","status-publish","hentry","no-post-thumbnail"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/6946","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6946"}],"version-history":[{"count":3,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/6946\/revisions"}],"predecessor-version":[{"id":6970,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/6946\/revisions\/6970"}],"up":[{"embeddable":true,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/6919"}],"next":[{"title":"A Media Trader","link":"https:\/\/wiki.pontiac.media\/?docs=platform-industry-glossary\/pontiac-white-papers\/a-media-trader","href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/6961"}],"prev":[{"title":"Four Problems Solved by RTB","link":"https:\/\/wiki.pontiac.media\/?docs=platform-industry-glossary\/pontiac-white-papers\/four-problems-solved-by-rtb","href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=\/wp\/v2\/docs\/6954"}],"wp:attachment":[{"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6946"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/wiki.pontiac.media\/index.php?rest_route=%2Fwp%2Fv2%2Fdoc_tag&post=6946"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}