Back to Bidders

Microsoft

Features

Table of Contents

• Table of Contents
  • Bid Params
  • Migrating from the AppNexus Bid Adapter & Bid Params
  • Migrating from the AppNexus Bid Adapter & Ad Server Targeting
  • Migrating from the AppNexus Bid Adapter & Native
  • Migrating from the AppNexus Bid Adapter & Auction Level Keywords
  • First Party Data
  • Debug Auction

All Microsoft (formerly AppNexus/Xandr) placements included in a single call to requestBids must belong to the same parent Publisher. If placements from two different publishers are included in the call, the Microsoft bidder will not return any demand for those placements.
Note: This requirement does not apply to adapters that are aliasing the Microsoft adapter.

Bid Params

NOTE Either placement_id OR both member and inv_code are required. Please don’t specify all three together, it may impact delivery.

Migrating from the AppNexus Bid Adapter & Bid Params

If you are migrating from the AppNexus bid adapter, a number of the previously available AppNexus bid parameters have been deprecated as available options for the Microsoft bid parameters. These deprecated bid parameters are still available however, they’re just read from other standarized locations offered within Prebid.js. This change was implemented to help us align better to the publisher-aligned features (such as First Party Data) to use a single setup for many bidders.

The following table shows how the bid parameters have changed between the two adapters:

Migrating from the AppNexus Bid Adapter & Ad Server Targeting

If you are migrating from the AppNexus bid adapter and your Ad Server Line Items (or related entities) relied on bidder specific keyword targeting to the Prebid.js keys (eg hb_bidder=appnexus or hb_pb_appnexus=5.00), you will like need to adjust your setup. Some adjustments could be creating additional line-items, updating the existing targeting, reomving targeting (if it’s no longer needed), or some other variation to ensure the targeting includes the msft term in either the key-name or key-value.

Migrating from the AppNexus Bid Adapter & Native Ads

If you are migrating from the AppNexus bid adapter, the setup for Native adUnits now require the use of the Prebid.js ORTB Native setup. The Microsoft Bid Adapter no longer offers support to the legacy Prebid.js Native adUnit setup.

Requests using that legacy approach will NOT work and will need to be converted to the equivalent values in the adUnit. This change is made to better align with Prebid.js and many other Bid Adapters that support Native in an ORTB context.

Please refer to the Prebid.js Native Implementation Guide if you need additional information to implement the Native ORTB setup.

Migrating from the AppNexus Bid Adapter & Auction Level Keywords

If you are migrating from the AppNexus bid adapter, the previously available setConfig option named appnexusAuctionKeywords is not supported within the Microsoft bid adapter.

If you need to specify keyword-like data at the auction/request level, please instead specify that data within the appropriate area of the First Party Data section of your setup (eg ortb2.site.keywords). If you wish to set bidder-specific First Party Data data, please refer to this page.

First Party Data

Publishers should use the ortb2 method of setting First Party Data.

PBS/PSP supports all first party data fields: site, user, segments, and imp-level first party data.

Debug Auction

Enabling the Microsoft Monetize Debug Auction feature should only be done for diagnosing the Monetize auction. Do NOT enable this feature in a production setting where it may impact users. The debug output will take the place of the normal bid response, meaning the ad will NOT show even if the auction debug output indicated there was a winning bid.

To understand what is happening behind the scenes during an auction, you can enable a debug auction by either adding an apn_prebid_debug cookie with a JSON string or add certain key-value pairs in the page URL’s query string.

To use the cookie approach, the JSON payload for the cookie could look like:

{ "enabled": true, "dongle": "QWERTY", "debug_timeout": 1000, "member_id": 958 }

NOTE If you use this approach, you may need to grant permission to the msft Bid Adapter in the your Prebid.js config storageAllowed settings, otherwise Prebid.js will block the adapter from attempting to find/read the cookie.

To use the page URL query string approach, you can append the following set of apn_debug_... key-value pairs to the existing page URL’s query string: html https://my.site.com/page/stuff.html?normal=data_here&apn_debug_enabled=true&apn_debug_dongle=QWERTY&apn_debug_member_id=958&apn_debug_timeout=1000

To view the results of the debug auction, add the pbjs_debug=true query string parameter and open your browser’s developer console.

"Send All Bids" Ad Server Keys

Back to Bidders