OpenWrap Profile Management

Document created by pubmatic-archivist on Mar 27, 2017Last modified by catherine.racette on Feb 26, 2018
Version 7Show Document
  • View in full screen mode

A Profile defines groups of inventory units that have the same configuration settings.

Example: A website’s home page may have different requirements than its subpages based on user behavior. Users tend to spend little time on a home page of a site, instead, they use it to transition to other subpages where they spend more time digesting content. This may result in different latency requirements for the home page than its subpages. You can configure separate profiles in PubMatic to optimize different latency requirements. 


From the Profile Management tab you can:


  • Create a profile.
  • Create a new version of an existing profile.

Creating a Profile

Add a new profile to OpenWrap when you have a group of inventory that share similar configuration settings.


  1. Select the Inventory & Rules > OpenWrap > Profile Management tabs.
  2. Choose Create Profile.
  3. In the Create Profile dialog, enter a Profile Name and Comment.
    A red asterisk ( * ) denotes required values.
    The Create Profile dialog

  4. Select a release version from the Release Version drop-down menu. There are two types of releases: Stable and Nightly. Stable releases go through planned release cycles and testing. Nightly releases expose new features that have not yet completed PubMatic’s testing and release cycles.

    Use nightly releases only in consultation with a PubMatic solutions engineer. Carefully monitor metrics when using nightly releases. Upgrade to a stable release as soon as PubMatic incorporates your desired features into the new release.

  5. Select the partners that apply to your profile. PubMatic appears by default; to add additional partners, choose the Select Partners drop-down menu, select partner names, then choose Done to add your selections.
  6. Check Send All Bids to send additional key values to the ad server with bid information for every bidder.
    Sending all bids to the ad server is a prerequisite to enabling bid landscape or per partner reporting on the ad server. Sending all bids is also necessary when a publisher wants to provide priority to PMP bids. When Send All Bids is selected, OpenWrap still sets the OpenWrap key values for the winning bid in addition to the per-bidder key values.
  7. Configure the following for each partner:
  8. Choose Save. Status will display 'DRAFT (Mapping Pending).'

Continue with Mapping Ad Units.

Managing a Profile

  1. Select the Profile Management tab.
  2. Select a profile from the menu.
  3. Choose an option form the Actions menu based on the action you want to perform.

Mapping Ad Units

After adding a new profile or creating a new profile version with additional partners, you will need to create and upload a mapping file for each partner. The mapping process allows the wrapper tag to include a partner-specific identifier (for example, PubMatic requires a site id and ad tag id in the ad call) that allows each partner to understand which ad unit is generating the impression. Partners use this information to apply various settings in their own platform, such as floor price, demand sources, etc.

A mapping file needs to be uploaded for each partner. Template type below refers to the on-page information that the wrapper looks for in runtime and then maps to the partner-specific ids uploaded in the mapping file. There are several template type choices below as mentioned.


Template Type


Ad Unit Name + Size                             

The AD Unit Code of the slot defined for GPT (e.g., /12345/Adunit1/Adunit2/

Size will be Width x Height

Div ID + Size

The Div ID on the page

Size is specified as Width x Height

Div IDOnly Div ID (PubMatic header tag always requires size, therefore this option is not available)
SizeMapping is only for sizes; i.e., for a particular size across all inventory, the same partner tag id/ad unit will be called.


Synchronous and Asynchronous Tags

OpenWrap provides options to generate both synchronous and asynchronous wrapper tags. Synchronous and asynchronous tags determine how the wrapper (and not the underlying header tags) is loaded on the page.


In the synchronous version, the publisher doesn’t have to delay gpt.js load explicitly to ensure pubmatic pwt.js is loaded before it (pwt.js still needs to load before gpt.js)


All the partner calls occur asynchronously in parallel.


On-Page Integration

  1. Select either Synchronous or Asynchronous.
  2. Copy code from the editable portion of the Document Layout section.
  3. Paste the code into the <head> section of the relevant pages or tag management solution.


⇧ Top