Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Phase 1: Solution design (1 day)

ActivityOwnershipDetails
Information GatheringPubMatic
Publisher
  1. Publisher completes the OpenWrap Integration Questionnaire
  2. Publisher reviews PubMatic's OpenWrap documentation and sends follow-up questions to PubMatic.
  3. Publisher reviews the demo page and identifies the appropriate API and tag for their production environment.  
      - JS API: OpenWrap JavaScript API
      - JS hooks: OpenWrap Hooks for JS 
  4. PubMatic reviews the updated questionnaire, Wrapper functionality, and set up details with the publisher and then outlines the project plan.
Phase 2: Implement and test (2-3 days)
Inventory setup (sites & tags)PubMatic
Publisher
  1. Publisher provides a list of ad unit sizes for bidder setup
  2. PubMatic sets up bidder per these guidelines: Account Setup Guide for Publishers (Sites & Ad Tags)
Create Partner Profiles & Provide Partner Mapping DetailsPublisher
  1. PubMatic shares bidder-specific configuration template with the publisher
  2. Publisher connects with each bidder and obtains bid parameter details for respective bidder configuration
  3. Publisher shares the updated bidder-specific template with PubMatic for partner configuration, and PubMatic review the details to ensure no mismatches.
Wrapper Profile Setup PubMatic
  1. PubMatic reviews the profile configuration requirements with the publisher
  2. Publisher shares profile configuration values with PubMatic
  3. PubMatic prepares for profile setup based on Publisher’s input
Ad server setup (order, line item, creative)

PubMatic
Publisher

  1. PubMatic shares the ad server configuration template with the publisher
  2. Publisher updates the ad server configuration template and sends it back to PubMatic
  3. Publisher (or PubMatic) creates the orders and line items in the ad server
On-page setup & Integration TestingPubMatic
Publisher
 
  1. Copy the wrapper tag to the test web page & provide test page to PubMatic.
  2. Ensure requests/responses are generated for each partner who is included across a given profile.
  3. Verify that key/value pairs are passed to the ad server call.
  4. Verify that ad server is responding with the winning creative and that the creative is rendered.
Phase 3: Launch and ramp (2-3 days)
Account ramp

PubMatic
Publisher
 

  1. Copy wrapper tag to a live page and repeat the on-page setup & integration testing (from phase 2)
  2. Once verified, send test traffic of 100k impressions per day from a live web page
  3. Perform discrepancy checks between OpenWrap analytics and ad server data
  4. Repeat these steps for each property set up and launch

...

The JavaScript API is the most flexible method, we recommend using it if you have multiple wrappers on the page. For example, if you're running OpenWrap & Amazon TAM together, you should use the JavaScript API. If OpenWrap is the only wrapper on the page, you can use either method, but GPT patching is only available if you're using GAM or UAS as your ad server.

Info

While GPT Patching continues to be supported, new implementations should the JavaScript API.

...

If using SafeFrames, see SafeFrames.

...

Ad Server Configuration

PMP & PMP-G support

Please refer to PMP-Guaranteed Implementation Guide for Publishers  to understand how PubMatic supports PMP and PMP-G.

...

  • Expandable creative will not work correctly after rendering inside of a SafeFrame on Safari, IE11/Edge.UAS does not support SafeFrame; only a GAM ad server supports SafeFrame.

Support for previous code build

...