search

openrtb / OpenRTB

Documentation and issue tracking for the OpenRTB Project
BSD 2-Clause "Simplified" License
854 stars 143 forks source link

Clarification for native obj in bid request. #20

Open stelios313 opened 9 years ago

stelios313 commented 9 years ago

Hello, in the OpenRTB-Native-Ads-Specification-1_0-Final document, page 21, the 6.1.1 bid request example has the native string NOT at the top level of the JSON, but inside the request payload which should be compliant with the Native Ad Specification.

So accessing, lets say, assets, would be "native.request.native.assets."

However in the OpenRTB_API_Specification_Version_2_3_1 document, (Section 3.2.5) in the native obj, it makes no mention of the second level native obj. Should i assume is just a mistake in the first example i referenced?

ibelianka commented 8 years ago

As I know and as we use in our system it is "native.request.assets". I think that it is a mistake in the examples there. The confusion is coming from the name of the 4.1 which is "Native Markup Request Object". So I think that it is really "request" there.

giorgosera commented 8 years ago

How can we fix the examples so people won't get confused?

dynamix commented 8 years ago

I had the same question - afaik there is going to be some clarification in 1.0.3 regarding the root object (https://docs.google.com/spreadsheets/d/1_ZDxJW5g0FgHdDOucsH8XCRGAsGPDKZoHDOEoGlbMH8/edit#gid=0). Right now it seems some guys went with native.request.assets (like TripLift) and others with native.request.native.assets (like MoPub).

giorgosera commented 8 years ago

This issue is addressed in Native Ads Extension 1.1 (page 14)

Note:​Prior to VERSION 1.1, the specification could be interpreted as requiring the native request to have a root node with a single field “native” that would contain the object above as its value. The Native Markup Request Object specified above is now the root object.