Merge branch 'master' into feature/smartytech-docs-userid-consent-chunks

Author: Artem-Maliuha

dev-docs/bidders/fwssp.md

@@ -36,18 +36,18 @@ The following bid params are for use with the Prebid.js bid adapter:
 | `profile` | required | Profile Name - The value should contain a profile name. and NOT a numeric profile ID. This can either include the network ID prefix or with the profile name alone | "96749:global-js"   | `string`   |
 | `siteSectionId` | required | Custom Site Section tag or numeric Site Section ID | "ss_12345" | `string` |
 | `videoAssetId` | required | Custom content Video Asset ID | "pause_ad_video" | `string` |
+| `bidfloor` | optional | Bid floor price | 13.2118 | `number` |
+| `bidfloorcur` | optional | Bid floor currency | "USD" | `string` |
 | `flags` | optional | Optional flags to include in the ad request | '+play-uapl' | `string` |
 | `mode` | optional | Request mode. Valid values are: “on-demand", "live". Default: "on-demand" | "live" | `string` |
 | `adRequestKeyValues` | optional | An object of ad request key-value pairs. | { \_fw_player_width: '1920', \_fw_player_height: '1080' } | `object` |
 | `gdpr_consented_providers` | optional | List of Consented Providers. A comma-separated list of ids. | "216,229,80,359,479" | `string` |
 | `tpos` | optional | Slot time position in seconds. Default: 0 | 10 | `number` |
 | `slid` | optional | Slot custom ID. Any string with valid letters/digits/symbols. Default: "Preroll_1" | "CustomPreroll" | `string` |
 | `slau` | optional | Specify custom ad unit names for this slot. Multiple ad unit names can be put into this parameter, separated by "\|". Ad unit group names are also supported but you can only specify one ad unit group; multiple ad unit groups or mixed ad unit group and ad unit names are not supported. Default: "preroll" | "pre1\|pre2" | `string` |
-| `minD` | optional | The minimum duration of a slot, in seconds. | 30 | `number` |
-| `maxD` | optional | The maximum duration of a slot, in seconds. | 30 | `number` |
 | `listeners` | optional | An object of AdManager event listeners | { onSlotStarted: this.onSlotStarted, adEvent: this.onAdEvent, onSlotEnded: this.onSlotEnded } | `object` |
-| `isMuted` | optional | Constrols if ad playback should start with volume muted. Default: true | false | `boolean` |
-| `showMuteButton` | optional | Controls if a mute button should be shown during ad playback.  Default: false | true | `boolean` |
+| `isMuted` | optional | Controls if ad playback should start with volume muted. Default: true | false | `boolean` |
+| `showMuteButton` | optional | Controls if a mute button should be shown during ad playback. Default: false | true | `boolean` |
 | `playerParams` | optional | An object of AdManager player parameter values | { "renderer.video.startDetectTimeout": 5000 } | `object` |
 | `sdkVersion` | optional | The AdManager sdk version to use for playback. This is only valid for "outstream" formats. Default: "7.10.0" | "7.11.0" | `string` |
 | `format` | optional | The format to use for displaying the ad. Default: outstream | "inbanner" | `string` |

dev-docs/bidders/lane4.md

@@ -90,3 +90,30 @@ var adUnits = [
             }
         ];
 ```
+
+#### First Party Data
+
+In release 4.30 and later, publishers should use the `ortb2` method of setting [First Party Data](https://docs.prebid.org/features/firstPartyData.html). The following fields are supported:
+
+* ortb2.user.id
+* ortb2.user.buyeruid
+* ortb2.user.keywords
+* ortb2.user.ext.*
+
+Example first party data that's available to all bidders and all adunits:
+
+```javascript
+pbjs.setConfig({
+  ortb2: {
+    user: {
+      id: 123456789,        // Unique pseudonymized ID for the user (e.g., NPI).
+      buyeruid: 987654321,  // DSP-assigned user ID for identity resolution.
+      keywords: "kw1,kw2",  // Interest or specialty tags (e.g., oncology, cardiology)
+      ext: {
+        key1: "values",    // Custom healthcare metadata (e.g., icd10), single or comma seperated.
+        key2: "values"     // Additional campaign context (e.g., ndc), single or comma seperated.
+      }
+    }
+  }
+});
+```

dev-docs/bidders/pubmatic.md

@@ -47,7 +47,7 @@ Publishers can use Prebid.js to call PubMatic in any of the following ways:
 * **Call through our client-side adapter**: Prebid.js calls PubMatic directly from the browser using our client-side adapter.
 * **Call through our server-side adapter**: Prebid.js makes a call to Prebid Server and then Prebid Server uses our server-side adapter to call PubMatic.
 
-We highly recommend adding the `gptPreAuction` module to populate GPID (Global Placement ID) values. See the [gptPreAuction module documentation](https://docs.prebid.org/dev-docs/modules/gptPreAuction.html) for implementation details.
+We highly recommend adding the `gptPreAuction` module to populate GPID (Global Placement ID) values. See the [gptPreAuction module documentation](https://docs.prebid.org/dev-docs/modules/gpt-pre-auction.html) for implementation details.
 
 ### Bid Params
 

dev-docs/modules/userId.md

@@ -102,7 +102,7 @@ The table below has the options that are common across ID systems. See the secti
 
 ## Permissions
 
-Publishers can control which user ids are shared with the bid adapters they choose to work with by using the bidders array.  The bidders array is part of the User id module config, publisher may choose to send an id to some bidders but not all, the default behavior is that each user id go to all bid adapters the publisher is working with.
+Publishers can control which user ids are shared with the bid adapters they choose to work with by using the bidders array.  The bidders array is part of the User id module config, publisher may choose to send an id to some bidders but not all, the default behavior is that each user id goes to all bid adapters the publisher is working with.
 
 Use the optional `bidders` parameter to define an array of bidder codes to which this user ID may be sent.
 

dev-docs/modules/userid-submodules/intentiq.md

@@ -17,7 +17,7 @@ By leveraging the Intent IQ identity graph, our module helps publishers, SSPs, a
 ## Registration
 
 Navigate to [our portal](https://www.intentiq.com/) and contact our team for partner ID.
-check our [documentation](https://pbmodule.documents.intentiq.com/) to get more information about our solution and how utilze it's full potential
+check our [documentation](https://pbmodule.documents.intentiq.com/) to get more information about our solution and how to utilze it's full potential
 
 ## Integration