OpenWrap simplifies header tag integration and post-integration management for publishers. OpenWrap provides a transparent enterprise wrapper solution for Prebid to publishers who want to increase monetization with access to the broadest set of exchanges and unique demand. OpenWrap simplifies partner management with hybrid client-side and sever-to-server management capabilities in an intuitive UI, with enterprise-grade analytics and a dedicated team for account optimization and support.
This guide describes key features and functions of OpenWrap and step-by-step instructions to use configurable controls and generate wrapper tags.
|Client-side||The user's web browser (the client) sends ad requests directly to partners. Client-side request processing has the highest user match rate but can slow web page loading.|
|Partners||SSP/Exchanges whose header tag is included in the wrapper.|
|Profile||Defines inventory for the wrapper. Includes configuration settings for the OpenWrap.|
|Server-side||Ad requests go first to an OpenWrap server, which then sends them to partners. Server-side request processing can speed web page loading but can reduce user match rate compared to client-side processing.|
|Version||A version of a profile. Refers to the settings included in the profile. One profile can include multiple versions (only one can be the live version in production).|
Provides a transparent enterprise wrapper solution for Prebid with GAM as a publisher ad server.
Simplifies partner management with hybrid client-side and server-to-server management capabilities in an intuitive UI with enterprise-grade analytics.
Contains multiple underlying header tags. The wrapper tag ensures that header tags can run concurrently.
Auto-detects ad units on a page. OpenWrap collects the necessary identifiers such as unit name, div ID, and size to send partner-specific identifiers.
Example: PubMatic requires ad unit name and ad size to identify the ad opportunity. This removes the burden on your engineering team to collect, map, and maintain all the ad unit identification data on a partner-by-partner basis for every page.
Provides an ad unit to partner-specific identifier mapping interface.
Offers the ability to configure controls such as traffic allocation, bid adjustment, and timeout values.
Handles decisioning on page, then passes the partner’s information and the winning bid to the Ad server.
Creates line items in the publishers’ ad server.
Delivers critical insights with analytics. Analytics include volume-related, monetization-related, and latency-related metrics.
Using PubMatic OpenWrap requires the following:
Access to web pages that will include the wrapper.
Define inventory groups of less than 500 ad units per group. Configure each inventory group in a separate profile.
Ad Unit Mapping:
Identify all ad units with ad unit names, div IDs, and ad sizes. Enter this information in the mapping file format for each partner (you'll find the file format in the Actions drop-down menu for a specific profile within the OpenWrap Profile Management tab (learn more).
Register those ad units with each partner you want to work with, and get a unique ID from each partner. For example, provide ad unit name and size to your PubMatic contact and in return receive corresponding site id and ad tag id.
Inspect the contents of the file to make sure it is complete.
Access to Ad server: Provide trafficker level access to the PubMatic team to assist with creating line items in the ad server. This is required if the publisher's ad server is GAM.
Use the instructions in this section to configure OpenWrap.
|When you see DFP mentioned in this guide, it is referring to GAM. This will be updated in the Publisher UI in an upcoming release.|
Select Inventory > OpenWrap. There are three OpenWrap tabs:
Partner Management: Add a new partner.
Profile Management: Create a new profile or manage an existing profile.
Tag Management: Retrieve wrapper tags for a selected profile.
Before you edit profiles and generate tags, you must first add them in the Partner Management tab.
Follow these steps to edit account-level information.
Profiles define groups of inventory that use the same configuration settings. Manage your profiles in the Profile Management tab. See OpenWrap Profile Management for details.
If you want to use OpenWrap with AMP pages see OpenWrap AMP Support.
OpenWrap makes it easy to change most settings. For example:
Choose Actions > Create New Version next to the most recent version.
One of two different styles of the Edit Profile dialog will display. Use the instructions below for the Edit Profile dialog that matches your configuration:
Make changes to the Traffic Allocation, Bid Adjustment, and Timeout (ms) fields.
|Continue to the Add or Remove Partners section below.|
Make changes to the Traffic Allocation, Bid Adjustment, and Timeout (ms) fields. Additionally, also check the Server-Side box for each partner that you want to run server-side. Leave the Server-Side box unchecked for any partners that you want to continue to run client-side.
|If all partners in the profile are configured as server-side, make sure at least one of them has timeout more than 500 ms (preferably 100 ms or more) to account for network round trip from user browser to server-side wrapper component. Even if the timeout is more than 500, server-side component would cap the timeout for outbound bid requests to 500 ms.|
|Continue to the Add or Remove Partners section below.|
Select AdServer, then choose either DFP or CUSTOM from the list.
Select the OpenWrap build version that will generate OpenWrap code for your profile.
Select Send All Bids if you don't want the wrapper to conduct the auction and send bids from all configured partners directly to DFP (GAM).
|Ad Server is DFP.|
Select USD from the AdServer Currency dropdown to use as your base currency.
Platform is Display and Ad Server is DFP or CUSTOM.
Consent Management for GDPR
Enable consent management if this profile is going to get traffic from European regions regulated by GDPR.
|See OpenWrap Profile Management for more details around all configuration related to consent management.|
|When you have finalized all settings and have completed mappings as mentioned earlier in this guide, you will have a new DRAFT version.|
To start testing the next version, push the draft version to staging by selecting Push to Staging. The Status of the version then updates to, STAGING.
|The update may take 15-30 seconds.|
Do not select Push to Production until the new version has been tested.
In order to test, select Actions > Debug URL, to append to your page URL where the new version is expected to run.
A debug URL looks like this:
For example: a publisher who is running version 1 on
yourdomain.com, would test Version 2 using this URL:
Once testing in complete, select Actions > Push to Production. This replaces the active version (previous production version), with the new version.
|No on-page changes are required when you create a new version for the same profile.|
|Each profile can have only one active version running in production. It may take 5-10 minutes to reflect the change.|
Please refer to PMP-Guaranteed Implementation Guide for Publishers to understand how PubMatic supports PMP-G.
Publishers using PubMatic’s OpenWrap have the opportunity to place the creative script in a SafeFrame instead of a standard Friendly iframe. Using a Friendly iframe, the ad server renders the content into a SafeFrame on the same server as the host content. But a SafeFrame is a managed, API-enabled iframe that communicates between the publisher page content and the ad rendered in the iframe. This lets SafeFrame collect data and provide rich interaction (such as ad expansion), that is unavailable with a standard 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:
Inside GAM, SafeFrame creative code added but the 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.
|Any creative to be rendered inside a SafeFrame must be SafeFrame compatible and must be tested on the page.|
To learn more about SafeFrames see:
The following sections describe the current known limitations of OpenWrap.
Below is the performance of code generation with gulp execution through the API with varying the number of adapter partners.
|Number of Partners||Time to Execute|
This has an impact on flow, user flows and API calls:
Expandable creatives do not work correctly after rendering inside of a SafeFrame on Safari, IE11/Edge.
When a stable code build of OpenWrap (with Prebid) is released, we will not support prior code builds. All subsequent OpenWrap profile versions will use the new stable code build.
For display profile in OpenWrap, currently we don't support server side partners for video inventory.