Skip to main content

Overview

Curation uses the same Permutive Prebid integration you already use for cohort activation. If the Permutive RTD module is set up as described in the Prebid integration guide, Curation only needs the checks below. Once your organization is onboarded into Curation, Permutive enables it on our side. The Permutive SDK then stores the cohorts for SSP curation marketplaces (including the cur cohort) in local storage, and the Permutive RTD module adds them to the bid requests for those SSPs, the same way it does for your other cohorts.
Prerequisites:
  • Signed Curation Order Form
  • The Permutive Prebid integration set up, with the Permutive RTD module (see Prebid setup)

What to check

1

The SSP bid adapters are in your Prebid.js build

Curated deals run on SSP curation marketplaces, so your Prebid.js build needs the bid adapter for each SSP you sell through:
  • Monetize: appnexus or msft
  • Index Exchange: ix
  • Pubmatic: pubmatic
2

Any custom bidder codes are known to Permutive

Permutive sends curation cohorts to the standard bidder codes above. If you call these SSPs through a bidder alias (a renamed adapter, or an alias in a Prebid Server setup), ask your Customer Success Manager to add the alias, otherwise bid requests to it won’t carry curation cohorts. Most setups don’t use aliases and need nothing here.
3

Curation cohorts reach the bid requests

Follow the Prebid verification steps and check the bid requests to the SSPs above: their ortb2.user.data should include the cur cohort from permutive.com. If it’s missing, see Prebid troubleshooting.

Next Steps

Managing Cohort Exclusions

Control which cohorts participate in curation

Prebid Integration

Set up and troubleshoot the Permutive Prebid modules

Back to Curation

Return to Curation overview