Magnite

Magnite is a leading independent sell-side advertising platform that helps publishers maximize revenue through programmatic advertising.

Setup

Troubleshooting

Overview

Magnite (formerly Rubicon Project) is a leading independent sell-side advertising platform that enables publishers to maximize their advertising revenue through programmatic channels. Our integration with Magnite SSP allows you to activate Permutive cohorts for targeting on Magnite’s supply-side platform. This integration is a Destination:

Destination: Permutive cohorts can be activated and synced with Magnite SSP, enabling advertisers to target your audiences programmatically.

This integration supports two activation methods:

Real-time bidstream activation: Cohort IDs are attached to bid requests as first-party data via Prebid.js (Web), Prebid Mobile (iOS/Android), and other Prebid integrations.
Server-side identity-based activation: Can be an alternative path where client-side activation isn’t viable. Permutive uploads cohort memberships to Magnite’s Segment Management API keyed by identity values (cookie ID, IDFA, AAID, IP address, or hashed email). Cohorts appear as Magnite segments ready for targeting.

Use cases include:

Cookie-less audience activation at scale: Activate Permutive cohort signals programmatically via the bidstream without reliance on third-party cookies, enabling addressable reach across all users
Private Marketplace (PMP) deals: Use Permutive cohorts to create premium, curated inventory packages for direct buyer relationships
Maximize programmatic yield: Make Permutive cohorts available through Magnite’s ad exchange to increase competition and drive higher CPMs
Cross-environment activation: Activate audiences across Web, in-app (iOS/Android), and CTV inventory through real-time bidstream or server-side identity-based methods

Environment Compatibility

Environment	Activation
Web	Live — Permutive RTD module in Prebid.js
iOS	Available — via Prebid Mobile (customer implementation)
Android	Available — via Prebid Mobile (customer implementation)
CTV	Discuss with your CSM
API Direct	Discuss with your CSM (for SDK-less environments)

Server-side identity-based activation can be an alternative path for this integration, particularly where client-side activation isn’t viable. Permutive can support your team in setting this up — contact your Customer Success Manager to discuss.

Supported Cohort Types

Magnite SSP activation supports multiple Permutive cohort types. Custom Cohorts are enabled by default; other cohort types can be enabled on request. Availability also depends on your workspace participating in the relevant Permutive offering.

Cohort type	Availability for Magnite	Product required
Custom Cohorts	Live	Core Platform
Standard Cohorts	On request	Curation
Curation Cohorts	On request	Curation
Data Clean Room Cohorts	On request	Data Clean Room

Cohort type support beyond WebThe availability shown above reflects Web today. In mobile (iOS/Android) and CTV environments where this integration is available, cohort type support depends on the Permutive Mobile/CTV SDKs:

Custom Cohorts — supported across all environments where this integration is available.
Data Clean Room Cohorts — not currently exposed by the Permutive Mobile/CTV SDKs, but cohort signals can be retrieved with customer integration via an additional Permutive API call from your application code.
Standard and Curation Cohorts — not currently exposed by the Permutive Mobile/CTV SDKs. Support is coming — reach out to your Customer Success Manager if you’re interested.

Cohort type availability also depends on your workspace participating in the relevant Permutive offering. Contact your Customer Success Manager to enable additional cohort types or discuss your use case.

Prerequisites

Required for all activation methods:

Magnite SSP Account — an active Magnite SSP account
Magnite Publisher ID — your Magnite SSP Account ID

For Web (Prebid.js):

Permutive Web SDK — deployed on your site
Prebid.js with Permutive RTD module — configured to pass cohort data to Magnite
Rubicon bidder adapter — the rubicon bidder adapter configured in your Prebid.js setup (this is the bidder code for Magnite)

For iOS / Android (Prebid Mobile):

Permutive Mobile SDK — deployed in your iOS / Android app
Prebid Mobile SDK — configured in your app
Prebid Server — that Prebid Mobile communicates with, with the rubicon bidder configured (Prebid Mobile passes bid requests to Prebid Server, which handles bidder routing)
Customer implementation — to retrieve Permutive cohorts from the SDK and attach them to Prebid Mobile bid requests

For CTV and other environments:

Contact your Permutive Customer Success Manager to discuss the integration approach for your stack.

For server-side identity-based activation:

This connector is not built today. If your use case calls for it, identity collection would need to be configured in Permutive for the identity types you want to use (cookie ID, IDFA, AAID, IP address, hashed email).
Contact your Permutive Customer Success Manager to discuss.

Setup

Primary Setup Steps
Web
iOS
Android
CTV

Enable in Permutive Dashboard

You must enable the Magnite SSP integration in the Permutive Dashboard, if this has not already been done.In the Permutive dashboard, navigate to your workspace’s integrations page. Click Add Integration and select Magnite SSP. You will be prompted to enter your Magnite Publisher ID (your Magnite SSP Account ID).This Publisher ID is used to authenticate with the Magnite API and tells Permutive which Magnite account to create and manage segments in. When you activate cohorts, Permutive uses this ID to make server-side API calls to the Magnite Segment Management API on your behalf.

The integration may also be listed as “Rubicon SSP” in some areas of the dashboard, as Magnite was formerly known as Rubicon Project.

Configure Cohort Activations

Once the integration is enabled, you can configure individual cohorts for activation to Magnite SSP.Navigate to the cohort you wish to activate, and toggle the Magnite SSP activation to On. When you enable this activation, Permutive will automatically create the corresponding segment in your Magnite SSP account using the Magnite Segment Management API.

Verify Setup

After activating a cohort, verify that the segment has been created successfully in your Magnite SSP dashboard and that cohort data is being passed in bid requests.Verify segment creation: In your Magnite SSP account, navigate to your segment management section. You should see segments created by Permutive, typically with names corresponding to your cohort IDs or names.Verify bid request data: Use the Professor Prebid Chrome extension to inspect bid requests:

Check local storage for the _prubicons key (Custom Cohorts)
Find Magnite (rubicon) bidder requests in Professor Prebid
Verify that the ORTB2 object contains Permutive cohort data in ortb2.user.data and ortb2.user.keywords

It may take a few minutes for segments to appear in the Magnite UI and for cohort membership to populate after initial page load.

Integrate with Prebid.js

The Magnite SSP integration works through the Permutive Real-Time Data (RTD) module in Prebid.js. The module reads Custom Cohort data from local storage (set by the Permutive SDK) and attaches it to bid requests as first-party data following OpenRTB 2.x conventions.

Configuration

In your Prebid.js configuration, include the Permutive RTD module:

pbjs.setConfig({
  realTimeData: {
    dataProviders: [
      {
        name: "permutive",
        waitForIt: true,
        params: {
          maxSegs: 500,
        },
      },
    ],
  },
});

How it Works

The Magnite SSP integration operates through a two-step process:1. Segment Pre-Creation (Server-Side)When you activate a Custom Cohort in Permutive, segments are created in your Magnite account via the Segment Management API. This pre-creation step is necessary because Magnite needs to register each segment ID and map it to a meaningful segment name before it can be used for targeting. This ensures that when Magnite receives bid requests containing segment IDs, it can recognize them and make them available to buyers (DSPs) for targeting.2. Local Storage Cohort ExposureThe Permutive Web SDK exposes Custom Cohort signals via local storage:

Custom Cohorts: Stored in the _prubicons local storage key

3. Real-Time Bid Enrichment (Client-Side)The Permutive RTD module acts as a bridge between the Permutive Web SDK and Prebid.js:

The Permutive RTD module reads Custom Cohort IDs from local storage (_prubicons)
Cohort data is attached to the ORTB2 object in bid requests for Magnite
The module updates two locations:
- ortb2.user.data – adds a data provider entry for permutive with the list of cohort IDs in the segment field
- ortb2.user.keywords – adds a keyword group called permutive containing the list of cohort IDs
Magnite receives cohort targeting data in the bid request and makes it available to demand partners (DSPs) for real-time targeting

While Permutive is listed as a TCF vendor (ID: 361), Permutive does not typically obtain vendor consent from the TCF, but instead relies on publisher purpose consents. Publishers wishing to use TCF vendor consent instead can add 361 to their CMP and set params.enforceVendorConsent to true:

pbjs.setConfig({
  realTimeData: {
    dataProviders: [{
      name: 'permutive',
      params: {
        enforceVendorConsent: true  // Require TCF vendor consent for Permutive (ID: 361)
      }
    }]
  }
})

For more details on Prebid.js configuration, see the Prebid.js documentation.

Magnite supports in-app inventory via Prebid Mobile (Prebid SDK for iOS). Prebid Mobile passes bid requests to a Prebid Server instance, which routes them to Magnite via the rubicon bidder. Activation of Permutive cohorts on iOS in-app traffic requires customer implementation to retrieve cohort signals from the Permutive Mobile SDK and attach them to Prebid Mobile bid requests.High-level pattern:

Initialise the Permutive Mobile SDK in your iOS app.
Retrieve the user’s active cohort IDs from the SDK.
Attach the cohort IDs to your Prebid Mobile bid request configuration as first-party user data — typically via ortb2.user.data (with a permutive data provider entry) and ortb2.user.keywords. This mirrors the structure used by the Permutive RTD module on web.
Verify that bid requests reaching Magnite (via your Prebid Server) carry Permutive cohort data.

Contact your Permutive Customer Success Manager — our team will partner with you on the integration.

Magnite supports in-app inventory via Prebid Mobile (Prebid SDK for Android). Prebid Mobile passes bid requests to a Prebid Server instance, which routes them to Magnite via the rubicon bidder. Activation of Permutive cohorts on Android in-app traffic requires customer implementation to retrieve cohort signals from the Permutive Mobile SDK and attach them to Prebid Mobile bid requests.High-level pattern:

Initialise the Permutive Mobile SDK in your Android app.
Retrieve the user’s active cohort IDs from the SDK (e.g. via TriggersProvider).
Attach the cohort IDs to your Prebid Mobile bid request configuration as first-party user data — typically via ortb2.user.data (with a permutive data provider entry) and ortb2.user.keywords. This mirrors the structure used by the Permutive RTD module on web.
Verify that bid requests reaching Magnite (via your Prebid Server) carry Permutive cohort data.

Contact your Permutive Customer Success Manager — our team will partner with you on the integration.

Data Types

The Magnite SSP integration is a destination-only integration focused on cohort activation. Permutive does not collect event data from Magnite SSP. When Custom Cohorts are activated to Magnite, the following data is transmitted via the Prebid.js bidstream:

ORTB2 Signal Locations

Permutive passes Custom Cohort data to Magnite SSP via the ORTB2 object in Prebid.js bid requests:

ORTB2 Location	Cohort Types
`ortb2.user.data` (name: `permutive`)	Custom Cohorts
`ortb2.user.keywords` (`permutive`)	Custom Cohorts

By default, only Custom Cohorts appear in Magnite bid requests via the Web RTD module. Standard, Data Clean Room, and Curation cohort support is available on request — see Supported Cohort Types.

Local Storage Keys

The Permutive Web SDK exposes cohort data via local storage, which the Permutive RTD module reads to populate bid requests.

array

Local storage key containing Custom Cohort IDs for Magnite.

Segments (Server-Side)

Permutive creates and manages segments in your Magnite SSP account via the Magnite Segment Management API. Each activated Custom Cohort is represented as a segment in Magnite.

string

The unique identifier for the segment in Magnite, typically corresponding to the Permutive cohort ID.

string

The name of the segment as it appears in Magnite, typically matching the cohort name in Permutive.

Troubleshooting

Segments not appearing in Magnite UI

If you’ve activated a Custom Cohort in Permutive but don’t see the corresponding segment in your Magnite SSP account:

Verify that the Magnite SSP integration is properly enabled in your Permutive Dashboard with the correct Magnite Publisher ID
Check that you have the correct permissions in your Magnite account to view segments
Ensure there are no special characters in your cohort names, as these can cause issues with segment creation
Wait a few minutes, as there may be a delay between activation in Permutive and segment creation in Magnite

If the issue persists, contact Permutive Support with your cohort ID and workspace details.

Cohort data not appearing in bid requests

If Permutive Custom Cohorts aren’t being passed to Magnite in your bid requests:

Verify that the Permutive RTD module is properly configured in your Prebid.js setup
Confirm that the Permutive SDK is loading correctly on your pages
Use browser developer tools to inspect local storage and verify that the _prubicons key contains cohort data
Check your Prebid.js console logs for any errors related to the Permutive RTD module
Use the Professor Prebid Chrome extension to inspect ORTB2 data being sent to Magnite bid requests

If you see cohort data in local storage but not in bid requests, verify that your Prebid.js configuration includes waitForIt: true for the Permutive RTD module.

Empty _prubicons local storage key

If the _prubicons local storage key is empty or missing:

Verify that Custom Cohorts have been activated in the Permutive dashboard with Magnite SSP enabled
Check that users actually qualify for the activated cohorts based on cohort definitions
Ensure the Permutive SDK is loading before Prebid.js attempts to read cohort data
Verify that third-party cookies and local storage are not blocked by browser settings or extensions
Check the browser console for any Permutive SDK errors during page load

Unable to enable Magnite SSP integration

If you see an error when trying to enable the Magnite SSP integration in the Permutive Dashboard:

Verify that you have the necessary permissions in your Permutive workspace
Ensure your workspace has the correct product entitlements to use SSP activations
Verify that your Magnite Publisher ID is correct
Contact Permutive Support if you believe you should have access but are unable to enable the integration

Changelog

For detailed changelog information, visit our Changelog.

Integrations

Identity

Contextual

Advertising

Marketing

Data Collaboration

Video

Social Media

Survey

Magnite

Magnite

Setup

Troubleshooting

Overview

Environment Compatibility

Supported Cohort Types

Prerequisites

Setup

Integrate with Prebid.js

Configuration

How it Works

Data Types

Troubleshooting

Changelog

​Magnite

Setup

Troubleshooting

​Overview

​Environment Compatibility

​Supported Cohort Types

​Prerequisites

​Setup

​Integrate with Prebid.js

​Configuration

​How it Works

​Consent

​Data Types

​Troubleshooting

​Changelog

Magnite

Overview

Environment Compatibility

Supported Cohort Types

Prerequisites

Setup

Integrate with Prebid.js

Configuration

How it Works

Consent

Data Types

Troubleshooting

Changelog