Support ext.prebid.bidderconfig[].config.ortb2.bcat

[gwhigs]

Untested POC.

[bsardo]

@gwhigs discussed in the backlog meeting. There is already an openrtb2blocking module available that will allow you to configure blocked categories for a particular bidder. Would that suffice? We would rather not add this as a first party data config option. Let us know if the module suffices. If not, in which case you need a request-based option, we can discuss further.

See the module docs: https://docs.prebid.org/prebid-server/pbs-modules/ortb2-blocking.html

[patmmccann]

@bsardo that's a revenue negative alternative, the goal is to communicate the correct bcats to each bidder so it can unlock additional bids

[gwhigs]

We're trying to configure bcats per-bidder from the page, so I believe we are looking for a request-based option here.

[mmenetto]

Hi @bsardo, This change allows each client request to define the bcat list for a specific bidder rather than globally. Because bcat support is inconsistent across bidders, applying it globally can negatively impact publisher revenue.

My understanding is that the existing module sources bcat from the PBS account configuration. That works for relatively static blocking rules, but any change to a publisher’s bcat settings would require an account configuration update rather than being supplied with the auction request.

The proposed model allows the client to set bidder-specific bcat values dynamically based on criteria such as:

• Publisher settings
• Page content
• User preferences or geo
• Experiment treatment

PBJS already manages bcat settings for the client. Propagating those values to PBS keeps the client as the single source of truth and can avoid maintaining the same configuration in multiple places.

[patmmccann]

@mmenetto does a binary to suppress the bcat array from a list of named bidders meet your requirement?