Skip to content

TCF restrictions for bidders called server-side #14812

@lmatha

Description

@lmatha

Resurfacing #12084, as it's still an ongoing issue.

Moving a PBJS bidder server-side can result in TCF2 fetchBids errors in PBJS -- those bidders are removed from the auction.

The issue is that PBJS doesn't know the GVL ID when there's no client-side adapter. The way to solve it is to add a gvlMapping, but this is kind of a pain -- when the pub wants to push a bidder server-side, they have to remember to look up each GVL ID and add it to the gvlMapping.

In the above mentioned issue, the following fix was proposed: adding a deferS2Sbidders flag to the TCF Control module for basicAds” (Purpose 2). We discussed doing this for other purposes, but decided that the only known problem is when PBJS completely suppresses the auction. The proposal is that we start with the known problem and enhance to refine when those use cases are defined.

Proposed config:

 pbjs.setConfig({
   consentManagement: {
     gdpr: {
       cmpApi: 'iab',   // activates the enforcement module
       defaultGdprScope: true,
       rules: [{
         purpose: "basicAds",
         enforcePurpose: true,
         enforceVendor: true,
         deferS2Sbidders: true         // default is false
       },{
         purpose: "personalizedAds",
         enforcePurpose: true,
         enforceVendor: true
       },{
         purpose: "transmitPreciseGeo",
         enforcePurpose: true,
         enforceVendor: true
       },{

Then before the module rejects the auction for server-side bidders, it would check this flag.

It was hinted that this would be fixed with prebid.js 10,x, but that was not the case.
Is there any chance this could be added to a future prebid.js 11.x release?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions