Merge branch 'master' into add-rediads-bid-adapter

_includes/code/mobile-sdk.html

@@ -9,9 +9,17 @@
 </ul>
 <div class="tab-content" id="code-tab-content">
   <div class="tab-pane fade show active" id="{{ include.id }}-kotlin" role="tabpanel" aria-labelledby="{{ include.id }}-kotlin-tab">
-    {{ include.kotlin | markdownify }}
+    <div class="highlight">
+      <pre class="highlight language-kotlin">
+        <code class="language-kotlin">{{ include.kotlin | xml_escape }}</code>
+      </pre>
+    </div>
   </div>
   <div class="tab-pane fade" id="{{ include.id }}-swift" role="tabpanel" aria-labelledby="{{ include.id }}-swift-tab">
-    {{ include.swift | markdownify }}
+    <div class="highlight">
+      <pre class="highlight language-swift">
+        <code class="language-swift">{{ include.swift | xml_escape }}</code>
+      </pre>
+    </div>
   </div>
 </div>

dev-docs/bidders/beop.md

@@ -24,4 +24,27 @@ The BeOp bidder adaptor needs an account id that you can find as a publisher, a
 | Name | Scope | Description | Example | Type |
 |---------------|----------|-------------|---------|----------|
 | `accountId` or `networkId` | required | Your BeOp account ID | `'5a8af500c9e77c00017e4cad'` | `string` |
+| `networkPartnerId` | optional | Your own partner ID if you are a network | `'MY-WEBSITE-123'` | `string` |
 | `currency` | optional | Your currency | `'EUR'` (default) or `'USD'` | `string` |
+
+## Why BeOp Requires Storage Access in Prebid.js
+
+At BeOp, we prioritize transparency and respect for user privacy. Here’s why we request storage access:
+
+### 1. Usage of First-Party Cookies
+
+We use the first-party cookie beopid exclusively. This allows us to manage session and user preferences without relying on third-party cookies, ensuring compliance with privacy standards like GDPR.
+
+### 2. Capping Features for Publishers
+
+Storage access helps us enforce capping mechanisms directly on the publisher’s domain, ensuring a better user experience by limiting the frequency of ad displays.
+
+### 3. Enhanced User Interaction
+
+We provide engaging voting experiences on BeOp formats. By using storage, we enable features such as resuming a voting session where the user last left off, making the interaction seamless and user-friendly.
+
+### 4. Revenue Optimization in Compliance with GDPR
+
+Storage access helps us improve bidding performance by aligning with GDPR consents. This ensures that external bidders can leverage compliant data to drive better revenue outcomes for publishers.
+
+By granting storage access, publishers empower us to provide these features while respecting user privacy and enhancing the overall experience.

dev-docs/bidders/ix-server.md

@@ -35,6 +35,7 @@ privacy_sandbox: paapi
   * [Call Index from Prebid Mobile SDK](#call-index-from-prebid-mobile-sdk)
   * [Call Index from CTV/long-form video environment](#call-index-from-ctvlong-form-video-environment)
   * [Call Index from any other server-to-server OpenRTB environment](#call-index-from-any-other-server-to-server-openrtb-environment)
+* [Receive Protected Audience API demand from Index](#paapi)
 * [Bid request parameters](#bid-request-parameters)
   * [Banner](#banner)
   * [Video](#video)
@@ -83,7 +84,6 @@ If you are hosting your own Prebid Server instance, depending on whether you are
      ```
 
   * Edit the below existing entry and include your publisher ID in the `s` parameter:
-{% raw %}
 
     ```javascript
      userSync:  
@@ -129,8 +129,6 @@ If you are hosting your own Prebid Server instance, depending on whether you are
          url: "https://ssum.casalemedia.com/usermatch?s=<PUBLISHER ID>&gdpr={{.GDPR}}&gdpr_consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&cb={{.RedirectURL}}"
     ```
 
-{% endraw %}
-
 <a id="call-index"></a>
 
 ### Publisher instructions to call Index through Prebid Server
@@ -238,6 +236,44 @@ To request bids from Index:
       }],
 ```
 
+<a id="paapi"></a>
+
+### Receive Protected Audience API demand from Index
+
+Publishers who want to use the Protected Audience API with Prebid Server, must first set up their inventory to be eligible for Protected Audience API in Prebid.js. Prebid Server will automatically pass through the on-device auction signals received from Prebid.js to Index. To receive Protected Audience API auction demand from Index, contact your Index Representative.
+
+**Before you begin:** Depending on whether you are using the Prebid Server Go or Java code base and the Prebid.js version, you must make sure that you are using the appropriate Prebid Server version:
+
+* **For Prebid Server Go:** If you are using a Prebid.js version that is between 7.44.0 and 8.51.0, you must be using Prebid Server version 2.1.0 or later. For a Prebid.js version that is 8.52.0 or later, you must be using Prebid Server version 3.3.0 or later.
+* **For Prebid Server Java:** If you are using a Prebid.js version that is 7.44.0 or later, you must be using Prebid Server Java version 3.16.0 or later.
+
+1. Configure Prebid.js to send the `ae` field with a value of `1`. For more information on how to set up the Protected Audience API in Prebid.js, see the [Protected Audience API support](/dev-docs/bidders/ix.html#protected-audience-api-support) section in our Prebid.js documentation on the Prebid site.
+2. Prebid Server will now automatically pass through the `ae=1` field received from Prebid.js to Index. No other specific Prebid Server configuration is required.
+
+**Example:** The following is an example that illustrates how to set up Prebid Server in your Prebid.js configuration:
+
+```javascript
+    pbjs.setConfig({
+    s2sConfig: [{
+        accountId: '1',
+        bidders: ['ix'],
+        adapter: 'prebidServer',
+        enabled: true,
+        endpoint: 'https://prebid-server.example.com/openrtb2/auction',
+        syncEndpoint: 'https://prebid-server.example.com/cookie_sync',
+        timeout: 500,
+        extPrebid: {
+            cache: {
+                vastxml: { returnCreative: false }
+            },
+            targeting: {
+                pricegranularity: {"ranges": [{"max":40.00,"increment":1.00}]}
+            }
+        }
+    }]
+})
+```
+
 <a id="bid-request-parameters"></a>
 
 ### Bid request parameters

dev-docs/bidders/pixelpluses.md

@@ -0,0 +1,36 @@
+---
+layout: bidder
+title: Pixelpluses
+description: Pixelpluses Bidder Adaptor
+biddercode: pixelpluses
+pbjs: true
+pbs: false
+media_types: banner, native, video
+gvl_id: 1209
+tcfeu_supported: true
+usp_supported: true
+coppa_supported: true
+gpp_supported: true
+pbs_app_supported: true
+schain_supported: true
+userIds: all
+fpd_supported: true
+prebid_member: false
+ortb_blocking_supported: true
+multiformat_supported: will-bid-on-one
+floors_supported: true
+aliasCode: adkernel
+sidebarType: 1
+---
+
+### Note
+
+The Pixelpluses bidding adapter requires setup and approval before implementation. Please reach out to <[email protected]> for more details.
+
+### Bid Params
+
+{: .table .table-bordered .table-striped }
+| Name     | Scope    | Description           | Example                   | Type     |
+|----------|----------|-----------------------|---------------------------|----------|
+| `host`   | required | Host | `'cpm.pixelpluses.com'` | `string` |
+| `zoneId` | required | Zone Id           | `30164`                 | `integer` |

dev-docs/bidders/rise.md

@@ -5,7 +5,7 @@ description: Prebid Rise Bidder Adapter
 multiformat_supported: will-bid-on-any
 pbjs: true
 biddercode: rise
-media_types: banner, video
+media_types: banner, video, native
 schain_supported: true
 coppa_supported: true
 pbs: true
@@ -37,7 +37,6 @@ The Rise adapter requires setup and approval. Please reach out to [prebid-rise-e
 | `placementId` | optional | String |  A unique placement identifier  | "12345678"
 | `testMode` | optional | Boolean |  This activates the test mode  | false
 | `rtbDomain` | optional | String |  Sets the seller end point    | "www.test.com"
-| `is_wrapper` | private | Boolean |  Please don't use unless your account manager asked you to    | false
 
 ### Example
 

dev-docs/modules/gppControl_usnat.md

@@ -37,7 +37,7 @@ This module activates if the `gpp` object in the consent management configuratio
 Follow the basic build instructions in the GitHub Prebid.js repo's main [README](https://github.com/prebid/Prebid.js/blob/master/README.md). To include the consent management module and the GPP Control - USNat module, an additional option must be added to the **gulp build** command:
 
 ```bash
-gulp build --modules=consentManagementGpp,gppContol_usnat,bidAdapter1,bidAdapter2
+gulp build --modules=consentManagementGpp,gppControl_usnat,bidAdapter1,bidAdapter2
 ```
 
 You can also use the [Prebid.js Download](/download.html) page.

docs-examples/tab-example.md

@@ -10,7 +10,8 @@ The prebid documentation uses bootstrap for styling. Bootstrap offers a [tab com
 
 ## Example
 
-{% capture iosCode %}struct Player {
+{% capture iosCode %}
+struct Player {
   var name: String
   var highScore: Int = 0
   var history: [Int] = []
@@ -20,18 +21,17 @@ The prebid documentation uses bootstrap for styling. Bootstrap offers a [tab com
   }
 }
 
-var player = Player("Tomas")
-{% endcapture %}
+var player = Player("Tomas"){% endcapture %}
 
-{% capture androidCode %}fun main() {
+{% capture androidCode %}
+fun main() {
   val name = "stranger"        // Declare your first variable
   println("Hi, $name!")        // ...and use it!
   print("Current count:")
   for (i in 0..10) {           // Loop over a range from 0 to 10
     print(" $i")
   }
-}
-{% endcapture %}
+}{% endcapture %}
 
 {% include code/mobile-sdk.html id="hello-world" kotlin=androidCode swift=iosCode %}