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
Client-side analytics adapters don't have access to what actually happened with PBS bids unless those bids are successful.
PBS will gain the ability to start responding with an ext.seatnonbid array to detail for client-side analytics adapters what exactly happened server-side with each imp+bidder combination.
ext.seatnonbid: [{
seat: "bidderB"
nonbid: [{
impid is set to $.imp[].id
ext.status.code is set to "nobid", "error", "reqrm", "resprm"
ext.status.details[].code is set to a code // optional
ext.status.details[].message is set to a string version of the code // optional
}]
}]
The types of nonbid response reasons have been defined as:
nobid
bidder error
request removed (reqrm)
"gdpr": GDPR removed the bidder
"moduleA": a module removed the bid request before being sent out
response removed (resprm)
"floor": bid removed due to pricefloor
"currency": bid removed because it was in a currency PBS couldn't convert
"moduleB": a module removed the bid response after the request. e.g. "ortb2block", "creativevalidation"
This may be our chance to expand the Prebid.js bid status options. @robertrmartinez has offered to flesh out what would need to happen to support this in PBJS so analytics adapters can process the extra data.
The text was updated successfully, but these errors were encountered:
Related: #9013; client side, bids removed at the currency or floor stage are rejected, with that PR introducing a new event for them. It may make sense to extend that to server-side gdpr or other modules.
Type of issue
Enhancement
Description
This is the JS-side of prebid/prebid-server#2367
Client-side analytics adapters don't have access to what actually happened with PBS bids unless those bids are successful.
PBS will gain the ability to start responding with an
ext.seatnonbid
array to detail for client-side analytics adapters what exactly happened server-side with each imp+bidder combination.The types of nonbid response reasons have been defined as:
This may be our chance to expand the Prebid.js bid status options. @robertrmartinez has offered to flesh out what would need to happen to support this in PBJS so analytics adapters can process the extra data.
The text was updated successfully, but these errors were encountered: