You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Permutive RTD: document msft bidder custom cohort support (#6522)
* docs: update permutiveRtdProvider.md for msft bidder custom cohorts
Add msft to supported custom cohort bidders list, document the new
params.bidders configuration, and note the appnexus-to-msft migration path.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: align markdown table columns to pass MD060 lint rule
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* remove hardcoded msft default from docs, add publisher config example
Mirrors the code change in Prebid.js PR #14655. The params.bidders
default is now {} and publishers must explicitly configure msft
custom cohort sources.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
| name | String | This should always be `permutive`| - |
67
+
| waitForIt | Boolean | Should be `true` if there's an `auctionDelay` defined (optional) |`false`|
68
+
| params | Object || - |
69
+
| params.acBidders | String[]| An array of bidder codes to share cohorts with in certain versions of Prebid, see below |`[]`|
70
+
| params.maxSegs | Integer | Maximum number of cohorts to be included in either the `permutive` or `p_standard` key-value. |`500`|
71
+
| params.bidders | Object | Per-bidder configuration for custom cohort sources. Keys are bidder codes. |`{}`|
72
+
| params.bidders.\<bidder\>.customCohorts | Object | Custom cohorts source configuration for a specific bidder. | - |
73
+
| params.bidders.\<bidder\>.customCohorts.source | String | Storage type to read custom cohorts from. Currently only `'ls'` (localStorage) is supported. | - |
74
+
| params.bidders.\<bidder\>.customCohorts.key | String | The localStorage key to read custom cohorts from. | - |
71
75
72
76
### Context
73
77
@@ -132,11 +136,25 @@ Currently, bidders with known support for custom cohort targeting are:
132
136
133
137
* Xandr
134
138
* Magnite
139
+
* Microsoft (msft)
135
140
136
141
When enabling the respective Activation for a cohort in Permutive, this module will automatically attach that cohort ID to the bid request.
137
142
There is no need to enable individual bidders in the module configuration, it will automatically reflect which SSP integrations you have enabled in your Permutive dashboard.
138
143
Permutive cohorts will be sent in the permutive key-value.
139
144
145
+
**Note:** Publishers migrating from the `appnexus` bidder to `msft` need to configure the `params.bidders` object so the module knows where to read custom cohorts from. The Permutive SDK writes `msft` custom cohorts to the same localStorage key used by `appnexus` (`_papns`), so publishers should add the following to their Permutive RTD config:
146
+
147
+
```javascript
148
+
params: {
149
+
acBidders: ['msft'],
150
+
bidders: {
151
+
msft: {
152
+
customCohorts: { source:'ls', key:'_papns' }
153
+
}
154
+
}
155
+
}
156
+
```
157
+
140
158
### _Enabling Advertiser Cohorts_
141
159
142
160
If you are connecting to an Advertiser seat within Permutive to share Advertiser Cohorts, populate the acbidders config in the Permutive RTD with an array of bidder codes with whom you wish to share Advertiser Cohorts with.
0 commit comments