Type of issue

using incorrect data

Description

A number of bid adapters are setting the 'GPID' with the value of 'pbAdSlot'. This isn't correct. The background material on this highlights that pbAdSlot pre-dated the TradeDesk's efforts to standardize the GPID.

It's true that the values may be the same, but publishers currently have to set both because the following bid adapters use them interchangeably.

Prebid would like to see all of these bid adapters change their logic so that GPID is set first from GPID, then from pbadslot as a backup. The plan is to eventually drop pbAdSlot entirely.

i.e. instead of

  let gpid = deepAccess(bid, 'ortb2Imp.ext.data.pbadslot');

The adapters should do something like

   let gpid = deepAccess(bid, 'ortb2Imp.ext.gpid') || deepAccess(bid, 'ortb2Imp.ext.data.pbadslot');

Bidders

• appnexus
• cadentApertureMX
• colossusssp
• goldbach
• grid
• gumgum
• kueezRtb
• mediafuse
• minutemediaplus
• onetag
• pixfuture
• richaudience
• sharethrough
• smartadserver
• sonobi
• vidazoo
• winr
• yieldmo

Separately -

• luponmedia is referring to fpd.context.pbAdSlot. fpd.context has been discontinued.