Use this guide to understand the open-source integrations supported by PubMatic.
Publishers typically set lower priorities for programmatic demand in their ad servers, thus limiting it to remnant impressions via trafficked tags. The programmatic marketplace can only propose bids for that limited volume of inventory it's exposed to. As a result, publishers lose visibility and monetization of high-value programmatic demand on a large share of their traffic.
OpenWrap provides a transparent enterprise wrapper solution for Prebid and lets publishers evaluate programmatic bids from multiple sources concurrently for every impression. OpenWrap also lets ad servers begin utilizing real-time bids returned instead of the static bids that are used in case of yield tags.
OpenWrap provides the pricing from programmatic open marketplaces from multiple SSP partners, which can be consumed by passing key-value pairs to ad servers in real-time.
An easy-to-use UI provides the option of controlling partners and inventory mapping allowing for quick application and testing.
Step-by-step integration process: OpenWrap Integration Guide
The OpenWrap SDK lets you leverage PubMatic's robust platform of OpenWrap capabilities within your mobile app. Publishers who want to increase monetization and access the broadest set of exchanges and unique demand, use OpenWrap's transparent enterprise wrapper solution for Prebid. OpenWrap simplifies partner management with an intuitive UI. Enterprise-grade analytics and a dedicated support team help you optimize your inventory's monetization. OpenWrap SDK takes the power of OpenWrap mobile.
Scaled demand in one SDK: integrate with 200+ demand partners, our direct relationships with buyers give you access to premium brand spend rather than CPI campaigns
Increased revenue through parallel auctions: unified auctions with real-time prices offers efficiency , transparency and increased revenue
Simplified demand partner management: leverage enterprise-grade analytics to optimize yield, and manage demand partners in a cloud-based UI that requires no changes to your SDK, app, or app store approval
Lightweight: at under 500KB , our SDK is smaller than other solutions and you only need one for multiple partners, parallel auctions in sub-200 m s reducing latency over traditional waterfall and SDK mediation solutions
Flexible deployment model: supports mainstream ad server, custom ad servers, and no ad server
|Step-by-step integration process: OpenWrap Mobile In-App Support|
Prebid.js is a feature-rich header bidding platform for the web, including more than 200 demand sources and 15 analytics adapters. It supports currency conversion, GDPR, TCF2 (from version 3.12), common ID systems, and multiple ad servers.
At a high level, header bidding with Prebid.js involves just a few steps:
The Prebid.js library is composed of these components:
The Prebid.js Adapters plug into Prebid.js Core and are meant to be interchangeable depending on who the publisher wants to work with. There are two types of adapters: bidder and analytics.
Bidder Adapters represent the SSPs & Exchanges you want to work with. There are currently over 200 bidder adapters. This set of working header bidding integrations is part of what makes Prebid.js so special. Each company maintains its own Prebid.js adapter to provide the freshest code for publishers, rather than a proprietary wrapper solution trying to reverse engineer another company’s adapter. It’s a win-win for everyone.
PubMatic has a Prebid.js adaptor.
|Step-by-step adaptor addition process: How to Add a New Bidder Adapter|
Prebid Mobile is an open-source library that provides an end-to-end header bidding solution for mobile app publishers. Use this library with your ad server’s Mobile SDK to communicate with Prebid Server to request and receive bids over RTB. These bids can then compete directly with bids from your primary ad server.
Step-by-step Prebid Mobile setup process: Getting Started with PreBid Mobile
|Step-by-step tag implementation process: Video-specific parameters|
|Step-by-step S2S implementation process: OpenRTB 2.3|