Suppot of adm_native field in Bid Response about openrtb HOT 2 CLOSED

Hi Michael -- Thanks for the report and the proposed fix, but we can't have this change in the library. The field adm_native is not part of the JSON specification, and this library tries to be strict with that, the goal is supporting extensions only via the specified mechanism of ext.* nodes. The support for embedded native object inside adm is a big exception, and we only do that because it's really critical, since the doubly-encoded JSON is both very inefficient and very unreadable. In the Protobuf wire format (itself a big extension) we use an alternate name adm_native because Protobuf is statically typed so it's not possible to put either a string or a child object in the same field.

However, the library doesn't support non-standard extensions just because some platform needs it (not even AdX; our own many, many custom fields are all mapped to ext.* fields). So if BidSwitch is doing this... ideally they should fix it, they could just use the regular field name adm with the nested native object inside. Or you can fork the library to support this BidSwitch-specific field.

from openrtb.

Hi Osvaldo
Thanks for your answer, I wasn't sure either if this was intended or not, so thanks for confirming!

from openrtb.