MASS Module

• MASS Module
  • Overview
  • Disclosure
  • Custom Mode
  • Integration
  • Module Configuration
    • Configuration Parameters
    • Example Configurations
    • Only (official) MASS support enabled
    • MASS support disabled, custom renderer enabled
    • Custom match and render
  • Integration Example
    • Option 1 - Your own development environment
  • Testing MASS
    • Testing using MASS compliant tags
    • For third-party technology companies
    • Testing on live sites

Overview

This module does not exist in PBJS 8.0 or later.

This module enables the MASS protocol for Prebid. To use it, you’ll need to work with a MASS enabled provider.

This module scans incoming bids for the presence of a “mass” flag being set to true in the bid meta or a publisher specified DealID pattern and uses external resources to decypher and process the MASS:// URI found within the ad markup. This modules is designed to work with MASS enabled Exchanges and DSP’s.

This module only loads external JavaScript resources if the publisher ad server has selected a MASS enabled bid as a winner.

Disclosure

This module loads external JavaScript to render creatives

Custom Mode

You can specify your own dealIdPattern and renderUrl by adding one or more entries into the custom configuration option (see Configuration Parameters below). When specifying a custom renderer, quality assurance is your responsibility.

Integration

Build the MASS module into the Prebid.js package with:

gulp build --modules=mass,...

Module Configuration

pbjs.que.push(function() {
  pbjs.setConfig({
    mass: {
      enabled: true,
      renderUrl: 'https://cdn.massplatform.net/bootloader.js',
      dealIdPattern: /^MASS/i,
      custom: [
        {
          dealIdPattern: /xyz/,
          renderUrl: 'https://my.domain.com/render.js',
          namespace: 'xyz'
        }
      ]
    }
  });
});

Configuration Parameters

Example Configurations

Only (official) MASS support enabled

pbjs.que.push(function() {
  pbjs.setConfig({
    mass: {
      renderUrl: 'https://cdn.massplatform.net/bootloader.js'
    }
  });
});

MASS support disabled, custom renderer enabled

pbjs.que.push(function() {
  pbjs.setConfig({
    mass: {
      custom: [
        {
          dealIdPattern: /xyz/,
          renderUrl: 'https://my.domain.com/render.js',
          namespace: 'xyz'
        }
      ]
    }
  });
});

Custom match and render

pbjs.que.push(function() {
  pbjs.setConfig({
    mass: {
      custom: [
        {
          match: function(bid) {
            // return true/false if matching/non-matching bid
          },

          render: function(payload) {
            console.log(payload);
          }
        }
      ]
    }
  });
});

Integration Example

There are two options to view the integration example:

Option 1 - Your own development environment

To view the integration example:

1. Build Prebid using the following required options

    gulp build --modules=ixBidAdapter,mass
   

2. Use a http server with a valid hostname to access its content. It is not advised to run the bid simulation using localhost or 127.0.0.1

    http://hostname/integrationExamples/mass/index.html
   

Testing MASS

Testing requires valid bids to be returned to Prebid. To assist with this process, we recommend you use the MASS Bid Simulation tool found at https://github.com/massplatform/bidsim. Your Exchange partner might be able to assist you with other specialist tools and browser plugins to achieve similar resuls.

The instructions below assume that you have followed the installation instructions for the MASS Bidsim tool found at https://github.com/massplatform/bidsim/blob/master/README.md.

Testing using MASS compliant tags

The bidsim tool ships with working DSP example tags that can be found under the bidsim/tags folder.

A quick way to test the Integration test page in combination with the official bootloader is to use the following command:

node bidsim --inject --bid 2000 --width 300 --height 250 --dealid 'MASS' --tag "tags/inskin-housead-desktop.js" -o https://demo.massplatform.net/ix/prebid

For third-party technology companies

Third-parties that wish to integrate with the official MASS bootloader can get started by running the following command:

node bidsim --inject --bid 2000 --width 300 --height 250 --dealid 'MASS' --tag "tags/test.js" -o https://demo.massplatform.net/ix/prebid

Explanation: The tags/test.js tag calls a reference endpoint for developers that can be accessed here: https://demo.massplatform.net/reference/endpoint.js. When running the above command to invoke this reference endpoint, you will see all the params that MASS collected and passed onto your endpoint. This includes inputs, parsed inputs, tag parameters and MASS/Provider specific configurations.

Testing on live sites

Any sites that have been MASS configured will work with the Bidsim tool. This is a convenient way to test whether your publisher ad server and slot is correctly configured.