Merge branch 'master' into addStellormedia

.github/pull_request_template.md

@@ -4,6 +4,8 @@ Please give a short description and check the matching checkboxes to help us rev
 
 Please make the PR writeable. This allows us to fix typos, grammar and linting errors ourselves, which makes
 merging and reviewing a lot faster for everybody.
+
+⚠️ The documentation is merged after the related code changes are merged and release ⚠️
 -->
 
 ## 🏷 Type of documentation

_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/adport.md

@@ -0,0 +1,115 @@
+---
+layout: bidder
+title: AdPort
+description: Prebid AdPort Bidder Adapter
+aliasCode: adverxo
+pbjs: true
+pbs: false
+pbs_app_supported: false
+biddercode: adport
+userIds:
+media_types: banner, native, video
+schain_supported: true
+dchain_supported: false
+ortb_blocking_supported: true
+floors_supported: true
+multiformat_supported: will-bid-on-any
+tcfeu_supported: false
+dsa_supported: false
+gvl_id: none
+usp_supported: false
+coppa_supported: false
+gpp_sids: none
+userId: no
+safeframes_ok: false
+deals_supported: true
+fpd_supported: true
+prebid_member: false
+privacy_sandbox: no
+sidebarType: 1
+---
+
+### Note
+
+The AdPort Bidding adapter requires setup and approval before beginning. Please reach out to <[email protected]> for
+more details.
+
+### Bid Params
+
+{: .table .table-bordered .table-striped }
+| Name | Scope | Description | Example | Type |
+|----------|----------|-----------------------|---------------------------|----------|
+| `adUnitId`   | required | Unique identifier for the ad unit in AdPort platform. | `1` | `integer` |
+| `auth`       | required | Authentication token provided by AdPort platform for the AdUnit. |`'61336e75e414c77c367eq5c47c2599ce80a8032b'` | `string` |
+
+### Setting First Party Data (FPD)
+
+Publishers should use the `ortb2` method of setting First Party Data. The following fields are supported:
+
+- ortb2.site.\*
+- ortb2.app.\*
+- ortb2.user.\*
+
+Example first party data:
+
+```javascript
+pbjs.setConfig({
+    ortb2: {
+        site: {
+            keywords: "kw1,kw2",
+            content: {
+                title: "title1",
+                series: "series1"
+            }
+        },
+        user: {
+            keywords: "a,b",
+            gender: "M",
+            yob: 1984
+        }
+    }
+});
+```
+
+### ORTB Blocking
+
+AdPort supports the next blocking parameters:
+
+- Blocked advertisers list (`badv`) is an array of domains as strings.
+- Blocked apps list (`bapp`) is an array of apps names as strings, for mobile apps in Google Play Store, these should be
+  bundle or package names (e.g. com.foo.mygame). For apps in Apple App Store, these should be a numeric ID.
+- Blocked categories list (`bcat`) is an array of IAB categories as strings.
+- Blocked attributes list (`battr`) is an array of integers. Refer to section 5.3 of the IAB specification for a list of
+  attributes.
+
+#### Globally defined ORTB Blocking
+
+```javascript
+pbjs.setConfig({
+    ortb2: {
+        badv: ["domain1.com", "domain2.com"],
+        bapp: ["com.foo.mygame", "284708449"],
+        bcat: ["IAB23-1", "IAB23-5", "IAB25-3", "IAB25-2"]
+    }
+});
+```
+
+#### ORTB Blocking specific only to the AdPort bidder
+
+```javascript
+pbjs.setBidderConfig({
+    bidders: ['adport'], // Or alias
+    config: {
+        ortb2: {
+            badv: ["domain1.com", "domain2.com"],
+            bapp: ["com.foo.mygame"],
+            bcat: ["IAB23-1", "IAB23-5", "IAB25-3", "IAB25-2"]
+        }
+    }
+});
+```
+
+#### Media Type defined ORTB Blocking
+
+Additionally `battr` ORTB blocking param may be set on media types to specify blocked creative
+attributes. Refer to section 5.3 of the IAB specification for a list of attributes.

dev-docs/bidders/adverxo.md

@@ -0,0 +1,115 @@
+---
+layout: bidder
+title: Adverxo
+description: Prebid Adverxo Bidder Adapter
+pbjs: true
+pbs: true
+pbs_app_supported: true
+biddercode: adverxo
+userIds:
+media_types: banner, native, video
+schain_supported: true
+dchain_supported: false
+ortb_blocking_supported: true
+floors_supported: true
+multiformat_supported: will-bid-on-any
+tcfeu_supported: false
+dsa_supported: false
+gvl_id: none
+usp_supported: false
+coppa_supported: false
+gpp_sids: none
+userId: no
+safeframes_ok: false
+deals_supported: true
+fpd_supported: true
+prebid_member: false
+privacy_sandbox: no
+sidebarType: 1
+---
+
+### Note
+
+The Adverxo Bidding adapter requires setup and approval before beginning. Please reach out to <[email protected]> for
+more details.
+
+### Bid Params
+
+{: .table .table-bordered .table-striped }
+| Name | Scope | Description | Example | Type |
+|----------|----------|-----------------------|---------------------------|----------|
+| `host`   | optional | Ad network host | `'js.pbsadverxo.com'` | `string` |
+| `adUnitId`   | required | Unique identifier for the ad unit in Adverxo platform. | `1` | `integer` |
+| `auth`       | required | Authentication token provided by Adverxo platform for the AdUnit. | `'61336e75e414c77c367eq5c47c2599ce80a8032b'` | `string` |
+
+### Setting First Party Data (FPD)
+
+Publishers should use the `ortb2` method of setting First Party Data. The following fields are supported:
+
+- ortb2.site.\*
+- ortb2.app.\*
+- ortb2.user.\*
+
+Example first party data:
+
+```javascript
+pbjs.setConfig({
+    ortb2: {
+        site: {
+            keywords: "kw1,kw2",
+            content: {
+                title: "title1",
+                series: "series1"
+            }
+        },
+        user: {
+            keywords: "a,b",
+            gender: "M",
+            yob: 1984
+        }
+    }
+});
+```
+
+### ORTB Blocking
+
+Adverxo supports the next blocking parameters:
+
+- Blocked advertisers list (`badv`) is an array of domains as strings.
+- Blocked apps list (`bapp`) is an array of apps names as strings, for mobile apps in Google Play Store, these should be
+  bundle or package names (e.g. com.foo.mygame). For apps in Apple App Store, these should be a numeric ID.
+- Blocked categories list (`bcat`) is an array of IAB categories as strings.
+- Blocked attributes list (`battr`) is an array of integers. Refer to section 5.3 of the IAB specification for a list of
+  attributes.
+
+#### Globally defined ORTB Blocking
+
+```javascript
+pbjs.setConfig({
+    ortb2: {
+        badv: ["domain1.com", "domain2.com"],
+        bapp: ["com.foo.mygame", "284708449"],
+        bcat: ["IAB23-1", "IAB23-5", "IAB25-3", "IAB25-2"]
+    }
+});
+```
+
+#### ORTB Blocking specific only to the Adverxo bidder
+
+```javascript
+pbjs.setBidderConfig({
+    bidders: ['adverxo'], // Or alias
+    config: {
+        ortb2: {
+            badv: ["domain1.com", "domain2.com"],
+            bapp: ["com.foo.mygame"],
+            bcat: ["IAB23-1", "IAB23-5", "IAB25-3", "IAB25-2"]
+        }
+    }
+});
+```
+
+#### Media Type defined ORTB Blocking
+
+Additionally `battr` ORTB blocking param may be set on media types to specify blocked creative
+attributes. Refer to section 5.3 of the IAB specification for a list of attributes.

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.