Open RTB Native

Specs

https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf
https://www.iab.com/wp-content/uploads/2018/03/OpenRTB-Native-Ads-Specification-Final-1.2.pdf

Open RTB Native is supported as an advar template in the Adhese UI. It is crucial that the structure follows the specification. In Adhese backend, we check the ad body for {\"native\":{ string to determine if this is an openRTB native ad type to prevent escaping some characters which would break the JSON structure. In the preprocessor, we check for {"native":{ string to determine the ad native type. The body is string-encoded JSON, as mentioned in the spec, we have plans to support direct object representation. 

Example of the advar template body openrtb_native.json

{\"native\":{\"ver\":\"1.2\",\"assets\":[{\"id\":1,\"img\":{\"w\":\"<ADHESE_WIDTH_LARGE>\",\"h\":\"<ADHESE_HEIGHT_LARGE>\",\"url\":\"<ADHESE_SWF_SRC_2ND>\"}}],\"link\":{\"url\":\"<DESTINATION_LINK>\"}}}

Example of openrtb_native.json.descr

{ "files": [ { "default": "", "doc": "The background and visual, width: 714px. - height: 224px., used for Web", "label": "Banner image", "key": "2nd" } ], "fields": [ { "default": "", "doc": "Enter the destination link (click-through URL)", "label": "Destination Link", "type": "singleLineText", "key": "<DESTINATION_LINK>", "id": "DestinationLink" } ], "advar": "openrtb_native.json" }