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
@@ -2195,6 +2196,37 @@ If you don't see that message, you can assume the config object is valid.
2195
2196
2196
2197
<hrclass="full-rule" />
2197
2198
2199
+
<aname="module_pbjs.setBidderConfig"></a>
2200
+
2201
+
### pbjs.setBidderConfig(options)
2202
+
2203
+
This function is similar to [`setConfig`](#module_pbjs.setConfig), but is designed to support certain bidder-specific scenarios.
2204
+
2205
+
Configuration provided through the [`setConfig`](#module_pbjs.setConfig) function is
2206
+
globally available to all bidder adapters. This makes sense because
2207
+
most of these settings are global in nature. However, there are use cases where different bidders require different data, or where certain parameters apply only to a given
2208
+
bidder. Use `setBidderConfig` when you need to support these cases.
2209
+
2210
+
The page usage is:
2211
+
2212
+
{% highlight js %}
2213
+
pbjs.setBidderConfig({
2214
+
bidders: ["bidderA"], // one or more bidders
2215
+
config: { // the bidder-specific config
2216
+
bidderA: {
2217
+
customArg: 'value'
2218
+
}
2219
+
}
2220
+
});
2221
+
{% endhighlight %}
2222
+
2223
+
When 'bidderA' calls `getConfig('bidderA')`, it will receive the object that contains 'customArg'.
2224
+
If any other bidder calls `getConfig('bidderA')`, it will receive nothing.
2225
+
2226
+
{: .alert.alert-info :}
2227
+
The `setBidderConfig` function will soon be used by the `schain` and
0 commit comments