Skip to content

Document skipPbsAliasing #5781

@bretg

Description

@bretg

There was a workaround added a while back in prebid/Prebid.js#6150 that dealt with an odd scenario where a bidder (MediaFuse) was an alias of one adapter in Prebid.js, but a different adapter in Prebid Server.

So a PBJS bid adapter spec addition was made where aliases can be flagged with 'skipPbsAliasing:true'. This causes PBJS to not add the ext.prebid.aliases entry for this bidder. The original scenario has been removed, but there are several additional aliases that have this flag, though it's not clear why:

  {code: 'adport', skipPbsAliasing: true},
  {code: 'bidsmind', skipPbsAliasing: true},
  {code: 'mobupps', skipPbsAliasing: true}
modules/adverxoBidAdapter.js
  {code: 'attekmi', skipPbsAliasing: true},
  {code: 'markapp', skipPbsAliasing: true},
  {code: 'jdpmedia', skipPbsAliasing: true},
  {code: 'tredio', skipPbsAliasing: true},
  {code: 'felixads', skipPbsAliasing: true},
  {code: 'vimayx', skipPbsAliasing: true},
modules/smarthubBidAdapter.js
  aliases: ['playwire', 'adlivetech', 'gridNM', { code: 'trustx', skipPbsAliasing: true }],
modules/gridBidAdapter.js

I would like to understand why the skipPbsAliasing flag is needed for these aliases. @TheMediaGrid - seems to me that allowing Prebid.js to alias trustx->grid would be fine nowadays. (?)

@SmartHubSolutions - similar question - none of these aliases exist in Prebid Server, so there should be no harm in having PBJS define the alias.

I think the only reason that skipPbsAliasing should be necessary is for odd scenarios like the original mediafuse issue where there's a transition happening between the alias and base adapter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions