This interview was originally published in eMarketer, reprinted with permission.
Most premium publishers who sell inventory programmatically rely on a tactic called header bidding, which allows them to simultaneously offer inventory to all of their ad exchanges before making calls to their ad servers. While header bidding has steadily gained adoption on the open web, it has been slower to gain popularity among app publishers.
Because there is not an actual header within apps, the phrase “mobile header bidding” is a misnomer, which is why industry insiders instead call this practice “mobile bidding,” “advanced bidding” or “unified auction.” Casie Jordan, director of professional services at Twitter-owned mobile ad tech company MoPub, spoke with eMarketer’s Ross Benes about how header bidding is moving into apps.
The in-app world tends to get ignored by the broader ad tech community a little bit. It’s like we’re at the middle school dance and nobody wants to dance with us. Chronologically, the cool stuff happens in desktop, and then mobile apps eventually get the benefit. For example, native ads in mobile apps took a few years to gain traction.
The app ecosystem is such a different animal. With the business practices of how ads are transacted, there’s quite a bit more to figure out, and it can take a longer time.
Mobile app exchanges have sold inventory programmatically for quite some time. What’s different is that there’s a call to action for every type of demand source—including exchanges and ad networks, which are popular in the app world—to buy inventory in real time. Mobile app bidding is just about allowing the publisher to offer up all of their inventory at once to all of their demand sources.
An SDK is just the technical mechanism that ad platforms use to get their ads inserted into mobile apps. Regarding the usage of SDKs, it should really be completely up to the publisher based on who they want to work with.
An exchange can work with a bunch of demand-side platforms [DSPs] that don’t require their own SDK, which means that the publisher needs only one SDK from the exchange to tap into those DSPs. But in order to get a lot of bang for their buck, publishers may work with a few exchanges and other demand sources.
Learn more about MoPub's approach to in-app bidding for the mobile app world here.
Today we’re excited to announce that we’re launching a new analytics solution: MoPub Analytics. It’s fast, offers a wide range of visualizations, and is built with an intuitive user experience in mind. This new solution provides our clients with a number of new capabilities beyond what they've had access to in the past, while at the same time ensuring that they can continue running their core reporting use cases.read more
Traffic quality is a top priority for MoPub and our clients, and invalid traffic (IVT) is an industry-wide concern. Today marks the launch of our comprehensive, multi-step approach to ensuring traffic quality through direct integrations with best-in-class IVT-management vendors while continuing to leverage Twitter’s global policy operations resources to enforce stringent policies for controlling traffic quality across our exchange.read more