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
The DSA OpenRTB extension has been merged and prebid along with bidders start implementing support for it.
Like consent support (tcfeu_supported, gpp_sids,...) bidders should be able to indicate if DSA support is available. There are two options to do this.
dsa_supported: true / false. Very basic, just saying that a bidder pipes through the dsa objects. Any additional information has to be requested
dsa_support: none / list of adrender:1, adrender:2, pubrender:0, pubrender:1, pubrender:2 . Giving additional context what rendering support can be offered. The field and values is just a sketch of the idea.
Both cases can't be vetted by the documentation team, but if bidders claim it, then publisher / ad tech partners can call them out on their docs.
The DSA OpenRTB extension has been merged and prebid along with bidders start implementing support for it.
Like consent support (
tcfeu_supported
,gpp_sids
,...) bidders should be able to indicate if DSA support is available. There are two options to do this.dsa_supported
:true
/false
. Very basic, just saying that a bidder pipes through the dsa objects. Any additional information has to be requesteddsa_support
:none
/ list ofadrender:1
,adrender:2
,pubrender:0
,pubrender:1
,pubrender:2
. Giving additional context what rendering support can be offered. The field and values is just a sketch of the idea.Both cases can't be vetted by the documentation team, but if bidders claim it, then publisher / ad tech partners can call them out on their docs.
Related issues and PRs
Bidder support
The text was updated successfully, but these errors were encountered: