This documentation describes the process of integrating the wrapper tag in OpenWrap. For more information about generating a wrapper tag, see the OpenWrap User Guide
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.
This table provides an overview of the integration process.
If you have questions or concerns, feel free to reach out to PubMatic.
Phase 1: Solution design (1 day)
|Phase 2: Implement and test (2-3 days)|
|Inventory setup (sites & tags)||PubMatic|
|Create Partner Profiles & Provide Partner Mapping Details||Publisher|
|Wrapper Profile Setup||PubMatic|
|Ad server setup (order, line item, creative)|
|On-page setup & Integration Testing||PubMatic|
|Phase 3: Launch and ramp (2-3 days)|
OpenWrap supports two integration options:
Use the information in the tables provided in the Partner Integrations Available in OpenWrap document.
Complete the following steps to ensure that each header tag in the Wrapper is working successfully:
Refer to instructions provided in documents mentioned below according to your ad server.
Ad Server Configuration
If using SafeFrames, see SafeFrames.
Please refer to PMP-Guaranteed Implementation Guide for Publishers to understand how PubMatic supports PMP and PMP-G.
Publishers using PubMatic’s OpenWrap can place the creative script in a Friendly iframe or a SafeFrame. Using a Friendly iframe, the content from the ad server renders in a frame on the same server as the host content. SafeFrame is a managed, API-enabled iframe that opens a line of communication between the publisher page content and the iframe-contained external contend (for example, ads). This provides a line of communication that affords data collection and rich interaction (for example, ad expansion), unavailable within a Friendly iframe.
Navigate to the Creative Settings for a line item and enter the appropriate creative script.
|There are different methods for rendering creatives for PMP bids and Open Market bids. Use the appropriate related script below|
SafeFrame for rendering PMP bids
SafeFrame for rendering Open Auction bids
Wrapper keys sent to GAM
Additional keys sent for Send All Bid
When Send All Bids is enable, the following additional keys will be sent for every bidder with a non-zero bid on an ad unit:
Inside GAM, SafeFrame creative code added but SafeFrame option is not selected.
Creative rendered correctly if it does not use SafeFrame feature. For example, a static image creative renders correctly but an expandable creative that relies on SafeFrame will not work correctly.
Inside GAM, legacy/regular pwt creative code added, SafeFrame option selected and SafeFrame creative rendered.
Error seen on browser console. Creative is rendered but if it is rich media creative/expandable then it will not work as expected.
Display non-compatible expandable creative inside SafeFrame
Creative does not render correctly or post creative expansion results into page error or unknown behavior.
Display SafeFrame creative inside a non-SafeFrame
Error seen on the browser console. Creative is rendered but if it is rich media creative/expandable then it will not work as expected.
Creative to be rendered inside SafeFrame must be SafeFrame compatible and needs to be tested on the page.
To learn more about SafeFrames see:
The following sections describe known limitations for OpenWrap.
The table below shows how performance of API code generation with gulp execution varies according to the number of adapter partners.
|Number of Partners||Time to Execute|
This impacts flow, user flows, and API calls when:
Upon a stable code release of OpenWrap (with Prebid), prior code builds are unsupported. All subsequent OpenWrap profile versions will use the new stable code build.
OpenWrap no longer supports Rubicon legacy adapter in any future code builds. Rubicon Legacy adapter works only in releases prior to OpenWrap (with Prebid).
|Publishers must migrate Rubicon accounts to Rubicon Fastlane and get new IDs to map in OpenWrap.|
OpenWrap ignores bids from Index Exchange adapter in a non-SRA setup. Perform the SRA GPT setup process to make the IndexExchange adapter work in OpenWrap.