From 486c3eb8781457d4383b3baf369d44005a536196 Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 21 Jul 2026 13:39:37 +0200 Subject: [PATCH 01/12] Add documentation for new scoremedia aliases (msftstalia) Add documentation for new msftstalia aliases (prebid/Prebid.js#15012) create msftstalia.md --- dev-docs/bidders/msftstalia.md | 101 +++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 dev-docs/bidders/msftstalia.md diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md new file mode 100644 index 0000000000..ad89b959cd --- /dev/null +++ b/dev-docs/bidders/msftstalia.md @@ -0,0 +1,101 @@ +--- +layout: bidder +title: msftstaila +description: Prebid Microsoft Bidder Adaptor +biddercode: msftstaila +aliasCode : msft +media_types: banner, video, native +tcfeu_supported: true +dsa_supported: true +prebid_member: true +userIds: all (with commercial activation) +schain_supported: true +coppa_supported: true +usp_supported: true +gpp_supported: true +floors_supported: true +fpd_supported: true +pbjs: true +pbjs_version_notes: +pbs: true +gvl_id: 32 +sidebarType: 1 +--- + +### Bid Params + +**NOTE** +msftstaila is an aliased bidder of Microsoft. +Either `placement_id` OR both `member` and `inv_code` are required. Please don't specify all three together, it may impact delivery. + +**NOTE** +We recommend to use the “use_pmt_rule” parameter set to true, when integrating, to ensure the bidding is net. + +For setup with Staila Media, please reach out to prebid@stailamedia.com. + + +{: .table .table-bordered .table-striped } + +| Name | Scope | Description | Example | Type | +| :--- | :--- | :--- | :--- | :--- | +| `placement_id` | required (see note above) | The placement ID from Microsoft Monetize. You may identify a placement using the `inv_code` and `member` instead of a placement ID. | `11223344` | `integer` | +| `member` | required (see note above) | The member ID from Microsoft Monetize. Must be used with `inv_code`. | `1234` | `integer` | +| `inv_code` | required (see note above) | The inventory code from Microsoft Monetize. Must be used with `member`. | `'abc123'` | `string` | +| `allow_smaller_sizes` | optional | If `true`, ads smaller than the values in your ad unit's `sizes` array will be allowed to serve. Defaults to `false`. | `true` | `boolean` | +| `use_pmt_rule` | optional | If `true`, Microsoft Monetize will return net price to Prebid.js after publisher payment rules have been applied. | `true` | `boolean` | +| `keywords` | optional | A comma-delimited string of key-value pairs (or terms) applied to this specific ad slot on the page. Mapped to [buy-side segment targeting](https://learn.microsoft.com/en-us/xandr/monetize/segment-targeting) (login required). A maximum of 100 key/value pairs can be defined at the request/page level. Each tag can have up to 100 additional key/value pairs defined. If you want to pass keywords for all adUnits, please use the relevant keywords fields in the First Party Data feature. Note that to use keyword with the Prebid Server adapter, that feature must be enabled for your account by an Microsoft Monetize account manager. | `pet=dog,food,brand=oldroy` | `string` | +| `traffic_source_code` | optional | Specifies the third-party source of this impression. | `'my_traffic_source'` | `string` | +| `pubclick` | optional | Specifies a publisher-supplied URL for third-party click tracking. This is just a placeholder into which the publisher can insert their own click tracker. This parameter should be used for an unencoded tracker. This parameter is expected to be the last parameter in the URL. Please note that the click tracker placed in this parameter will only fire if the creative winning the auction is using Microsoft Monetize click tracking properly. | `'http://click.adserver.com/'` | `string` | +| `ext_inv_code` | optional | Specifies predefined value passed on the query string that can be used in reporting. The value must be entered into the system before it is logged. | `'10039'` | `string` | +| `ext_imp_id` | optional | Specifies the unique identifier of an externally generated auction. | `'bacbab02626452b097f6030b3c89ac05'` | `string` | +| `banner_frameworks` | optional | Array of integers listing API frameworks for Banner supported by the publisher. | `[1,2]` | `array of integers` | + + + +### 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 Microsoft Bid Adapter connects to Microsoft's advertising exchange for bids. This adapter supports banner, video (instream and outstream), and native ad formats using OpenRTB 2.5 standards. + +For reference, here is the IAB OpenRTB 2.5 [specification](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf) + +The following table shows how the bid parameters have changed between the two adapters: + +{: .table .table-bordered .table-striped } + +| AppNexus Parameter | Microsoft Parameter | Description | +| :--- | :--- | :--- | +| `params.placementId` | `params.placement_id` | Placement ID (**only** the underscore case is now supported in the name, value **only** accepts integers) | +| `params.member` | `params.member` | Member ID (value **only** accepts integers) | +| `params.inv_code` | `params.inv_code` | Inventory code (unchanged) | +| `params.publisher_id` | Use `ortb2.publisher.id` | Publisher ID (moved to ortb2 config) | +| `params.frameworks` | `params.banner_frameworks` | Banner API frameworks array (small name change to clarify banner only) | +| `params.user` | Use `ortb2.user` | User data (moved to ortb2 config) | +| `params.allow_smaller_sizes` | `params.allow_smaller_sizes` | Allow smaller ad sizes (unchanged) | +| `params.use_pmt_rule` | `params.use_pmt_rule` | Use payment rule (unchanged) | +| `params.keywords` | `params.keywords` | Tag/Imp-level keywords (use ORTB format of comma-delimited string value; eg `'pet=cat,food,brand=fancyfeast'`) | +| `params.video` | Use `mediaTypes.video` | Video parameters (moved to mediaTypes) | +| `params.video.frameworks` | Use `mediaTypes.video.api` | Video API frameworks (moved to mediaTypes) | +| `params.app` | Use `ortb2.app` | App data (moved to ortb2 config) | +| `params.reserve` | Use bidfloor module | Reserve price (use bidfloor module) | +| `params.position` | Use `mediaTypes.banner.pos` | Banner position (moved to mediaTypes) | +| `params.traffic_source_code` | `params.traffic_source_code` | Traffic source code (unchanged) | +| `params.supply_type` | Use `ortb2.site` or `ortb2.app` | Supply type (moved to ortb2 config) | +| `params.pub_click` | `params.pubclick` | Publisher click URL (dropped underscore to align to endpoint) | +| `params.ext_inv_code` | `params.ext_inv_code` | External inventory code (unchanged) | +| `params.external_imp_id` | `params.ext_imp_id` | External impression ID (shortend to ext) | + +### Keywords +With the AppNexus adapter, keywords followed this format: keyname=keyvalue1,keyvalue2,keyvalue3 + +In the Microsoft Bid Adapter, the new required format is: keyname=keyvalue1,keyname=keyvalue2,keyname=keyvalue3 + + +### First Party Data + +Publishers should use the `ortb2` method of setting [First Party Data](https://docs.prebid.org/features/firstPartyData.html). + +PBS/PSP supports all first party data fields: site, user, segments, and imp-level first party data. + + From 472f2ae155b1c8eeb18ab5f826a34b06fc17a9e8 Mon Sep 17 00:00:00 2001 From: CPG Date: Sun, 9 Aug 2026 10:49:20 +0200 Subject: [PATCH 02/12] Update msftstalia.md Cleanup --- dev-docs/bidders/msftstalia.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index ad89b959cd..efd5d3320f 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -22,7 +22,7 @@ gvl_id: 32 sidebarType: 1 --- -### Bid Params +## Bid Params **NOTE** msftstaila is an aliased bidder of Microsoft. @@ -31,8 +31,7 @@ Either `placement_id` OR both `member` and `inv_code` are required. Please don' **NOTE** We recommend to use the “use_pmt_rule” parameter set to true, when integrating, to ensure the bidding is net. -For setup with Staila Media, please reach out to prebid@stailamedia.com. - +For setup with Staila Media, please reach out to [prebid@stailamedia.com](mailto:prebid@stailamedia.com). {: .table .table-bordered .table-striped } @@ -91,7 +90,6 @@ With the AppNexus adapter, keywords followed this format: keyname=keyvalue1,keyv In the Microsoft Bid Adapter, the new required format is: keyname=keyvalue1,keyname=keyvalue2,keyname=keyvalue3 - ### First Party Data Publishers should use the `ortb2` method of setting [First Party Data](https://docs.prebid.org/features/firstPartyData.html). From f342234325887fa8c6758a14e0ebd025da58313b Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:27:20 +0200 Subject: [PATCH 03/12] Update dev-docs/bidders/msftstalia.md Co-authored-by: Muki Seiler --- dev-docs/bidders/msftstalia.md | 1 - 1 file changed, 1 deletion(-) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index efd5d3320f..c644c6d4f5 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -49,7 +49,6 @@ For setup with Staila Media, please reach out to [prebid@stailamedia.com](mailto | `ext_imp_id` | optional | Specifies the unique identifier of an externally generated auction. | `'bacbab02626452b097f6030b3c89ac05'` | `string` | | `banner_frameworks` | optional | Array of integers listing API frameworks for Banner supported by the publisher. | `[1,2]` | `array of integers` | - ### Migrating from the AppNexus Bid Adapter & Bid Params From 7ccb0c81ceef8f00094163419123d78b9bf33d75 Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:27:37 +0200 Subject: [PATCH 04/12] Update dev-docs/bidders/msftstalia.md Co-authored-by: Muki Seiler --- dev-docs/bidders/msftstalia.md | 1 + 1 file changed, 1 insertion(+) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index c644c6d4f5..e360ce61f8 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -85,6 +85,7 @@ The following table shows how the bid parameters have changed between the two ad | `params.external_imp_id` | `params.ext_imp_id` | External impression ID (shortend to ext) | ### Keywords + With the AppNexus adapter, keywords followed this format: keyname=keyvalue1,keyvalue2,keyvalue3 In the Microsoft Bid Adapter, the new required format is: keyname=keyvalue1,keyname=keyvalue2,keyname=keyvalue3 From faaec844ab91d701efa8c0fa323669be4286e323 Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:27:46 +0200 Subject: [PATCH 05/12] Update dev-docs/bidders/msftstalia.md Co-authored-by: Muki Seiler --- dev-docs/bidders/msftstalia.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index e360ce61f8..f506c4a064 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -24,7 +24,7 @@ sidebarType: 1 ## Bid Params -**NOTE** +{: .alert.alert-note :} msftstaila is an aliased bidder of Microsoft. Either `placement_id` OR both `member` and `inv_code` are required. Please don't specify all three together, it may impact delivery. From 781cfe318db862e50c87ef762669509e3fbb61ef Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:27:52 +0200 Subject: [PATCH 06/12] Update dev-docs/bidders/msftstalia.md Co-authored-by: Muki Seiler --- dev-docs/bidders/msftstalia.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index f506c4a064..4b1605d759 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -92,7 +92,7 @@ In the Microsoft Bid Adapter, the new required format is: keyname=keyvalue1,keyn ### First Party Data -Publishers should use the `ortb2` method of setting [First Party Data](https://docs.prebid.org/features/firstPartyData.html). +Publishers should use the `ortb2` method of setting [First Party Data](/features/firstPartyData.html). PBS/PSP supports all first party data fields: site, user, segments, and imp-level first party data. From 20a1c9696d7470fdcbb8fe4421990915ba16126e Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:28:00 +0200 Subject: [PATCH 07/12] Update dev-docs/bidders/msftstalia.md Co-authored-by: Muki Seiler --- dev-docs/bidders/msftstalia.md | 1 - 1 file changed, 1 deletion(-) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index 4b1605d759..0ec55bd7d1 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -96,4 +96,3 @@ Publishers should use the `ortb2` method of setting [First Party Data](/features PBS/PSP supports all first party data fields: site, user, segments, and imp-level first party data. - From a3d077679170195e928ed49293fec8788defb19c Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:28:05 +0200 Subject: [PATCH 08/12] Update dev-docs/bidders/msftstalia.md Co-authored-by: Muki Seiler --- dev-docs/bidders/msftstalia.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index 0ec55bd7d1..61e6848050 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -88,7 +88,7 @@ The following table shows how the bid parameters have changed between the two ad With the AppNexus adapter, keywords followed this format: keyname=keyvalue1,keyvalue2,keyvalue3 -In the Microsoft Bid Adapter, the new required format is: keyname=keyvalue1,keyname=keyvalue2,keyname=keyvalue3 +In the Microsoft Bid Adapter, the new required format is: `keyname=keyvalue1,keyname=keyvalue2,keyname=keyvalue3` ### First Party Data From 4c3ad507503144fa6c81ccdf4ad021f811d8ab34 Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:28:15 +0200 Subject: [PATCH 09/12] Update dev-docs/bidders/msftstalia.md Co-authored-by: Muki Seiler --- dev-docs/bidders/msftstalia.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index 61e6848050..332753f875 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -28,7 +28,7 @@ sidebarType: 1 msftstaila is an aliased bidder of Microsoft. Either `placement_id` OR both `member` and `inv_code` are required. Please don't specify all three together, it may impact delivery. -**NOTE** +{: .alert.alert-note :} We recommend to use the “use_pmt_rule” parameter set to true, when integrating, to ensure the bidding is net. For setup with Staila Media, please reach out to [prebid@stailamedia.com](mailto:prebid@stailamedia.com). From c01d5cab0f94a501766ac95879a4c398570ede8e Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:28:22 +0200 Subject: [PATCH 10/12] Update dev-docs/bidders/msftstalia.md Co-authored-by: Muki Seiler --- dev-docs/bidders/msftstalia.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstalia.md index 332753f875..53600b1592 100644 --- a/dev-docs/bidders/msftstalia.md +++ b/dev-docs/bidders/msftstalia.md @@ -29,7 +29,7 @@ msftstaila is an aliased bidder of Microsoft. Either `placement_id` OR both `member` and `inv_code` are required. Please don't specify all three together, it may impact delivery. {: .alert.alert-note :} -We recommend to use the “use_pmt_rule” parameter set to true, when integrating, to ensure the bidding is net. +We recommend to use the `use_pmt_rule` parameter set to true, when integrating, to ensure the bidding is net. For setup with Staila Media, please reach out to [prebid@stailamedia.com](mailto:prebid@stailamedia.com). From f37f410eab0dd1694cbad5de9cb6879fe415c709 Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:36:28 +0200 Subject: [PATCH 11/12] Rename msftstalia.md to msftstaila.md --- dev-docs/bidders/{msftstalia.md => msftstaila.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename dev-docs/bidders/{msftstalia.md => msftstaila.md} (100%) diff --git a/dev-docs/bidders/msftstalia.md b/dev-docs/bidders/msftstaila.md similarity index 100% rename from dev-docs/bidders/msftstalia.md rename to dev-docs/bidders/msftstaila.md From fe85b5b50fda931e9dc93a9e7068e6fe8da3e758 Mon Sep 17 00:00:00 2001 From: CPG Date: Tue, 11 Aug 2026 13:51:46 +0200 Subject: [PATCH 12/12] apply 2 markdownlint fixes --- dev-docs/bidders/msftstaila.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/dev-docs/bidders/msftstaila.md b/dev-docs/bidders/msftstaila.md index 53600b1592..f7b1f98343 100644 --- a/dev-docs/bidders/msftstaila.md +++ b/dev-docs/bidders/msftstaila.md @@ -49,7 +49,6 @@ For setup with Staila Media, please reach out to [prebid@stailamedia.com](mailto | `ext_imp_id` | optional | Specifies the unique identifier of an externally generated auction. | `'bacbab02626452b097f6030b3c89ac05'` | `string` | | `banner_frameworks` | optional | Array of integers listing API frameworks for Banner supported by the publisher. | `[1,2]` | `array of integers` | - ### 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. @@ -95,4 +94,3 @@ In the Microsoft Bid Adapter, the new required format is: `keyname=keyvalue1,key Publishers should use the `ortb2` method of setting [First Party Data](/features/firstPartyData.html). PBS/PSP supports all first party data fields: site, user, segments, and imp-level first party data. -