Merge branch 'master' into add-permutive-consent-changes

Author: AntonioGargaro

_data/sidebar.yml

@@ -2042,3 +2042,32 @@
   isSectionHeader: 0
   sectionTitle:
   subgroup: 0
+
+#-------------- Prebid Agents --------------|
+
+- sbSecId: 10
+  title:
+  link:
+  isHeader: 0
+  isSectionHeader: 1
+  sectionTitle: Prebid Agents
+  sectionId: prebid-agents
+  subgroup: 1000
+  sbCollapseId: prebid-agents
+
+- sbSecId: 10
+  title: General
+  link:
+  isHeader: 1
+  headerId: agents-general
+  isSectionHeader: 0
+  sectionTitle:
+  subgroup: 0
+
+- sbSecId: 10
+  title: Salesagent
+  link: /agents/salesagent.html
+  isHeader: 0
+  isSectionHeader: 0
+  sectionTitle:
+  subgroup: 0

agents/salesagent.md

@@ -0,0 +1,116 @@
+---
+layout: page_v2
+title: Salesagent
+description: A media sales agent that implements the AdCP Media Buy protocol
+sidebarType: 10
+---
+
+# Prebid Sales Agent
+
+The Prebid Sales Agent is a server that exposes advertising inventory to AI agents via the Model Context Protocol (MCP) and Agent-to-Agent (A2A) protocol. It is designed to integrate with ad servers like Google Ad Manager and provides tools for managing inventory and campaigns throughout their lifecycle.
+
+<div class="alert alert-info" role="alert">
+  For the full source code and latest updates, visit the <a href="https://github.com/prebid/salesagent">prebid/salesagent repository</a>.
+</div>
+
+## Key Features
+
+### For AI Agents
+
+- **Product Discovery**: Natural language search for advertising products.
+- **Campaign Creation**: Automated media buying with targeting capabilities.
+- **Creative Management**: Streamlined upload and approval workflows.
+- **Performance Monitoring**: Real-time access to campaign metrics.
+
+### For Publishers
+
+- **Multi-Tenant System**: Isolates data per publisher for security and organization.
+- **Adapter Pattern**: Supports multiple ad servers (e.g., Google Ad Manager).
+- **Real-time Dashboard**: Live activity feed powered by Server-Sent Events (SSE).
+- **Workflow Management**: Unified system for human-in-the-loop approvals.
+- **Admin Interface**: Web UI with Google OAuth for easy management.
+
+### For Developers
+
+- **MCP Protocol**: Standard interface for AI agents.
+- **A2A Protocol**: Agent-to-Agent communication via JSON-RPC 2.0.
+- **REST API**: Programmatic tenant management.
+- **Docker Deployment**: Easy setup for both local and production environments.
+
+## Getting Started
+
+### Quick Start (Evaluation)
+
+You can try the sales agent locally using Docker:
+
+```bash
+# Clone and start
+git clone https://github.com/prebid/salesagent.git
+cd salesagent
+docker compose up -d
+
+# Test the MCP interface
+uvx adcp http://localhost:8000/mcp/ --auth test-token list_tools
+```
+
+Access services at [http://localhost:8000](http://localhost:8000):
+
+- **Admin UI**: `/admin` (Test credentials: `test123`)
+- **MCP Server**: `/mcp/`
+- **A2A Server**: `/a2a`
+
+### Production Deployment
+
+For production, publishers can deploy their own sales agent instance. The repository provides guides for various deployment methods, including Docker and cloud platforms.
+
+## The AdContext Protocol (AdCP)
+
+The Sales Agent is built on the **AdContext Protocol (AdCP)**, an open standard designed to standardize how AI agents interact with advertising platforms.
+
+<div class="alert alert-info" role="alert">
+  For comprehensive documentation, visit <a href="https://docs.adcontextprotocol.org/docs/intro">docs.adcontextprotocol.org</a>.
+</div>
+
+### Protocol Architecture
+
+AdCP operates as a layer on top of standard AI interaction protocols:
+
+- **MCP (Model Context Protocol)**: Facilitates direct integration with AI assistants (e.g., Claude Desktop).
+- **A2A (Agent-to-Agent Protocol)**: Enables complex, autonomous workflows and collaboration between agents using JSON-RPC 2.0.
+
+### Core Concepts
+
+AdCP abstracts complex advertising operations into standardized domains:
+
+1. **Inventory Discovery** (`get_products`): Agents can search for ad products using natural language criteria (e.g., "video ads in North America") rather than specific line item IDs.
+2. **Media Buying** (`create_media_buy`): A normalized workflow for proposal, negotiation, and booking that works consistently across different ad servers.
+3. **Creative Management** (`build_creative`): Standardized handling of creative assets, allowing agents to generate or upload assets that match publisher specifications.
+4. **Signal Activation** (`get_signals`, `activate_signal`): Mechanisms for passing context and identity signals to improve targeting and campaign performance.
+
+### Workflow Example
+
+A typical AI-driven campaign flow using AdCP might look like this:
+
+1. **Discovery**: Expected outcome is a list of available "Products" matching the agent's intent.
+2. **Planning**: The agent uses `create_media_buy` to submit a proposal.
+3. **Review**: The Sales Agent (and potentially a human publisher) reviews the proposal.
+4. **Execution**: Once approved, the Sales Agent pushes the orders to the underlying ad server (e.g., GAM).
+
+## Architecture
+
+The project follows a clean structure isolating core MCP components, business logic services, and ad server adapters.
+
+```text
+salesagent/
+├── src/
+│   ├── core/           # Core MCP server components
+│   ├── services/       # Business logic services
+│   ├── adapters/       # Ad server integrations (e.g., GAM)
+│   └── admin/          # Admin UI (Flask)
+├── scripts/            # Utility and deployment scripts
+└── tests/              # Comprehensive test suite
+```
+
+## Contributing
+
+Contributions are welcome! Please refer to the [Development Guide](https://github.com/prebid/salesagent/blob/main/docs/development/README.md) in the repository for details on setting up your environment and creating pull requests.

dev-docs/analytics/intentiq.md

@@ -46,11 +46,8 @@ pbjs.enableAnalytics({
     provider: 'iiqAnalytics',
     options: {
         partner: 1177538,
-        manualWinReportEnabled: false,
-        reportMethod: "GET",
-        adUnitConfig: 1,
+        ABTestingConfigurationSource: 'IIQServer',
         domainName: "currentDomain.com",
-        gamPredictReporting: false
     }
 });
 ```
@@ -91,7 +88,9 @@ originalCpm: 1.5, // Original CPM value.
 originalCurrency: 'USD', // Original currency.
 status: 'rendered', // Auction status, e.g., 'rendered'.
 placementId: 'div-1' // ID of the ad placement.
-adType: 'banner' // Specifies the type of ad served
+adType: 'banner', // Specifies the type of ad served
+size: '320x250', // Size of adUnit item,
+pos: 0 // The following values are defined in the ORTB 2.5 spec
 }
 ```
 
@@ -109,6 +108,8 @@ adType: 'banner' // Specifies the type of ad served
 | status              | String    | Status of the impression. Leave empty or undefined if Prebid is not the bidding platform                                                          | rendered                      | No        |
 | placementId         | String    | Unique identifier of the ad unit on the webpage that showed this ad                                                                               | div-1                         | No        |
 | adType              | String    | Specifies the type of ad served. Possible values: “banner“, “video“, “native“, “audio“.                                                           | banner                        | No        |
+| size              | String    | Size of adUnit item                                                           | 320x250                       | No        |
+| pos              | number    | The pos field specifies the position of the adUnit on the page according to the OpenRTB 2.5 specification                                                           | 0                        | No        |
 
 To report the auction win, call the function as follows:
 

dev-docs/bidders/alchemyx.md

@@ -0,0 +1,113 @@
+---
+layout: bidder
+title: AlchemyX
+description: Prebid AlchemyX Bidder Adapter
+aliasCode: adverxo
+pbjs: true
+pbs: false
+pbs_app_supported: false
+biddercode: alchemyx
+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: none
+safeframes_ok: false
+deals_supported: true
+fpd_supported: true
+prebid_member: false
+sidebarType: 1
+---
+
+### Note
+
+The AlchemyX Bidding adapter requires setup and approval before beginning. Please reach out to <prebid@alchemyx.io> for
+more details.
+
+### Bid Params
+
+{: .table .table-bordered .table-striped }
+| Name | Scope | Description | Example | Type |
+|----------|----------|-----------------------|---------------------------|----------|
+| `adUnitId`   | required | Unique identifier for the ad unit in AlchemyX platform. | `1` | `integer` |
+| `auth`       | required | Authentication token provided by AlchemyX 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
+
+AlchemyX 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 AlchemyX bidder
+
+```javascript
+pbjs.setBidderConfig({
+    bidders: ['alchemyx'],
+    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/intlscoop.md

@@ -0,0 +1,42 @@
+---
+layout: bidder
+title: Intellectscoop
+description: Intellectscoop Adaptor
+biddercode: intlscoop
+aliasCode: adkernel
+tcfeu_supported: true
+dsa_supported: false
+gvl_id: 14 (adkernel)
+usp_supported: true
+coppa_supported: true
+gpp_sids: tcfeu, usp
+schain_supported: true
+dchain_supported: false
+userId: all
+media_types: banner, video, native
+safeframes_ok: true
+deals_supported: false
+floors_supported: true
+fpd_supported: true
+pbjs: true
+pbs: false
+pbs_app_supported: false
+prebid_member: false
+multiformat_supported: will-bid-on-any
+ortb_blocking_supported: true
+privacy_sandbox: no
+sidebarType: 1
+
+---
+
+### Note
+
+The Intellectscoop bidding adaptor requires setup and approval before beginning. Please reach out to <apoorv@intellectscoop.com> for more details
+
+### Bid Params
+
+{: .table .table-bordered .table-striped }
+| Name     | Scope    | Description           | Example                   | Type     |
+|----------|----------|-----------------------|---------------------------|----------|
+| `host`   | required | RTB host | `'cpm.intellectscoop.com'` | `string` |
+| `zoneId` | required | RTB zone id           | `30164`                 | `integer` |

dev-docs/bidders/ogury.md

@@ -82,12 +82,13 @@ Use this example configuration for enabling Ogury ad server integration on a spe
 
 #### Inventory mapping
 
-_"Inventory mapping" is only available for request coming from **web**. For **in-app** request use the "bid param" integration method._
-
 _Note: If you choose inventory mapping, you can skip specifying assetKey and adUnitId per ad unit._
 
-With inventory mapping you don't need to setup `assetKey/adUnitId` for every ad unit that you want to integrate. You use a single `id` and provide Ogury with list of sites and `ad_unit_code`s that you want to integrate and the mapping will be done on our side.
-The example configuration for this type of integration looks like this:
+With inventory mapping you don't need to setup `assetKey/adUnitId` for every ad unit that you want to integrate. You use a single `id` and provide Ogury with list of sites or bundles and `ad_unit_code`s that you want to integrate and the mapping will be done on our side.
+
+The example configuration for this type of integration looks like bellow.
+
+Web example:
 
 ```javascript
 pbjs.que.push(function () {
@@ -107,6 +108,26 @@ pbjs.que.push(function () {
 })
 ````
 
+In-app example:
+
+```javascript
+pbjs.que.push(function () {
+            // setup publisherId for ogury
+            pbjs.setBidderConfig({
+                bidders: ['ogury'],
+                config: {
+                    ortb2: {
+                        app: {
+                            publisher: {
+                                id: '$OGURY_PUBLISHER_ID',
+                            },
+                        }
+                    }
+                }
+            })
+})
+````
+
 `$OGURY_PUBLISHER_ID` is a Ogury provided id. 
 
 ### Optional bid Params