It is possible to specify conflicting info on ad units and ortb2imp

[patmmccann]

It is possible to do this:

pbjs.requestBids({ adUnits: [{ code: 'test-div', mediaTypes: { banner: { sizes: [[300,250]], battr = [3] } }, ortb2Imp: { banner: { battr = [4] } } }] });

And many publishers specify params for imp.video.* in the mediatype.video object, not the ortb2Imp.video object.

Some adapters look for battr in the latter (ttd), some in the former (pubmatic) and most just use params (we need to clean that up).

Proposal: the ortb2Imp object in the bid request contains the full banner and video objects from the mediatype, and vice versa, but conflicts always resolve to the media type.

This has some impacts on PAAPI bidders, which are reliant on ortb2Imp being detailed

[dgirardi]

the ortb2Imp object in the bid request contains the full banner and video objects from the mediatype,

in general mediaTypes are not valid ortb. mediaTypes.video is almost like imp.video but not quite. banner and especially native are very different.

We can do this only for specific fields that we decide should be mirrored. Or we could move parts of ortbConverter into core to do the translation for everyone.

[pm-harshad-mane]

And many publishers specify params for imp.video.* in the mediatype.video object, not the ortb2Imp.video object.

We, Prebid, can keep only one way of defining these params ( a major version change ), preferably through ortb2Imp.

[patmmccann]

the ortb2Imp object in the bid request contains the full banner and video objects from the mediatype,

We can do this only for specific fields that we decide should be mirrored.

Doh, let's scope this down to just battr and these ones https://github.com/prebid/Prebid.js/pull/11970/files#diff-a4386e7142e703699b5a905fc06783725a5eccecb33fa0b1f6b5ab4466fb8286 ?

[patmmccann]

outcome: ortb2Imp should win in the case of conflict