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
Adding some detail here, a publisher should be able to define a pmp like this https://docs.prebid.org/dev-docs/adunit-reference.html#first-party-data ; not just via your adapter parameters. It is a requirement you support the standard openrtb way of forming a bid request when you provide a parameter. The most frequent publisher complaint about prebid is bidder parameters having redundant implementations of the same information
@patmmccann I am doing the changes based on your comment, but I do see the same json which I used is also being used by pubmatic adapter. Please check the link: pubmatic
Is prebid enforcing this change for all the adapters to standardize the adUnits?
@patmmccann we agree that All adapters must support standard locations in addition to their parameters. @kapil-tuptewar is looking into it, will respond soon.
Adding some detail here, a publisher should be able to define a pmp like this https://docs.prebid.org/dev-docs/adunit-reference.html#first-party-data ; not just via your adapter parameters. It is a requirement you support the standard openrtb way of forming a bid request when you provide a parameter. The most frequent publisher complaint about prebid is bidder parameters having redundant implementations of the same information
@patmmccann I am doing the changes based on your comment, but I do see the same json which I used is also being used by pubmatic adapter. Please check the link: pubmatic
Is prebid enforcing this change for all the adapters to standardize the adUnits?
Originally posted by @skapoorViant in #11864 (comment)
All adapters must support standard locations in addition to their parameters
The text was updated successfully, but these errors were encountered: