From 37d8bff28c5d441655c795b992acf53b000dd405 Mon Sep 17 00:00:00 2001 From: rmartinez Date: Tue, 17 Feb 2026 14:57:34 -0800 Subject: [PATCH] magnite adapter --- dev-docs/bidders/magnite.md | 235 ++++++++++++++++++++++++++++++++++++ 1 file changed, 235 insertions(+) create mode 100644 dev-docs/bidders/magnite.md diff --git a/dev-docs/bidders/magnite.md b/dev-docs/bidders/magnite.md new file mode 100644 index 0000000000..603c0a89b2 --- /dev/null +++ b/dev-docs/bidders/magnite.md @@ -0,0 +1,235 @@ +--- +layout: bidder +title: Magnite +description: Prebid Magnite Bidder Adapter +biddercode: magnite +tcfeu_supported: true +dsa_supported: true +gpp_sids: tcfeu, usnat, usstate_all, usp +usp_supported: true +coppa_supported: true +schain_supported: true +floors_supported: true +media_types: banner, video, native +userIds: all +prebid_member: true +safeframes_ok: true +deals_supported: true +pbjs: true +pbs: false +fpd_supported: true +ortb_blocking_supported: true +gvl_id: 52 +multiformat_supported: will-bid-on-any +sidebarType: 1 +--- + +### Registration + +The Magnite adapter requires setup and approval from the Magnite team, even for existing accounts. Please reach out to your account manager or for more information. + +### Bid Params + +{: .table .table-bordered .table-striped } +| Name | Scope | Description | Example | Type | +|------|-------|-------------|---------|------| +| `accountId` | required | The publisher account ID | `14062` | `integer` | +| `siteId` | required | A unique ID for your site | `70608` | `integer` | +| `zoneId` | required | A unique ID for your site's ad placements | `498816` | `integer` | + +#### First Party Data + +Publishers should use the `ortb2` method of setting First Party Data. The following fields are supported: + +- ortb2.site.ext.data.* +- ortb2.site.keywords +- ortb2.site.content.data[] +- ortb2.user.ext.data.* +- ortb2.user.data[] + +The Magnite exchange supports IAB standard taxonomies for contextual and audience segments. + +Example first party data available to all bidders and all ad units: + +```javascript +pbjs.setConfig({ + ortb2: { + site: { + keywords: "kw1,kw2", + ext: { + data: { + prodtype: ["tech","mobile"] + } + } + }, + user: { + ext: { + data: { + ucat: ["new"] + } + } + } + } +}); +``` + +Example of first party data available only to the Magnite bidder across all ad units: + +```javascript +pbjs.setBidderConfig({ + bidders: ["magnite"], + config: { + ortb2: { + site: { + keywords: "kw1,kw2", + ext: { + data: { + prodtype: ["tech","mobile"] + } + } + }, + user: { + ext: { + data: { + ucat: ["new"] + } + } + } + } + } +}); +``` + +### Media Types + +#### Banner + +Banner ads are supported with standard IAB sizes. + +```javascript +var bannerAdUnit = { + code: 'test-div', + mediaTypes: { + banner: { + sizes: [[300, 250], [728, 90]] + } + }, + bids: [{ + bidder: 'magnite', + params: { + accountId: 14062, + siteId: 70608, + zoneId: 498816 + } + }] +}; +``` + +#### Video + +The Magnite adapter supports standard OpenRTB video parameters for both instream and outstream contexts. + +```javascript +var videoAdUnit = { + code: 'myVideoAdUnit', + mediaTypes: { + video: { + context: 'instream', + playerSize: [640, 480], + mimes: ['video/mp4', 'video/x-ms-wmv'], + protocols: [2, 5], + maxduration: 30, + linearity: 1, + api: [2] + } + }, + bids: [{ + bidder: 'magnite', + params: { + accountId: 14062, + siteId: 70608, + zoneId: 498816 + } + }] +}; +``` + +Outstream video is also supported. We recommend discussing video demand with your Magnite account representative. + +#### Native + +The Magnite adapter supports native ads using the ORTB Native spec. We recommend version 1.2, but versions 1.0 and 1.1 are also supported. + +{: .table .table-bordered .table-striped } +| Native Version | Required Fields | +|---|---| +| 1.0 and 1.1 | layout, adunit, assets | +| 1.2 | context, plcmttype, assets, eventtrackers. privacy is a recommended field. | + +Here's an example using ORTB Native 1.2: + +```javascript +var nativeAdUnit = { + code: 'myNativeAdUnit', + mediaTypes: { + native: { + ortb: { + ver: "1.2", + context: 2, + plcmttype: 11, + privacy: 1, + assets: [{ + id: 1, + required: 1, + img: { + type: 3, + w: 150, + h: 50 + } + }], + eventtrackers: [{ + event: 1, + methods: [1, 2] + }] + } + } + }, + bids: [{ + bidder: 'magnite', + params: { + accountId: 14062, + siteId: 70608, + zoneId: 498816 + } + }] +}; +``` + +### Configuration + +#### User Sync + +Add the following code to enable user syncing. By default, Prebid.js turns off user syncing through iframes. Magnite recommends enabling iframe-based user syncing to improve match rates and bid performance. + +```javascript +pbjs.setConfig({ + userSync: { + iframeEnabled: true + } +}); +``` + +### Migration from Rubicon + +{: .alert .alert-info :} +This section is under construction. Detailed migration guidance will be provided soon. + +The Magnite adapter (`bidder: "magnite"`) is designed as the next-generation replacement for the Rubicon adapter (`bidder: "rubicon"`). It uses a modern OpenRTB integration that is simpler and easier to maintain. + +Key points for migrating: + +- The bid params (`accountId`, `siteId`, `zoneId`) remain the same. +- The adapter accepts configuration from both `magnite` and `rubicon` config namespaces during the transition. +- Update `bidder: "rubicon"` to `bidder: "magnite"` in your ad unit configurations. + +