Native 分册导航
Native Markup Request§4.1 · Bid Request
`Native Markup Request` 对象定义本次竞价请求中可供出价的原生广告机会。依交易平台（exchange）的选择，它以 JSON 编码字符串形式包含在竞价请求的 imp.native 字段中，或作为直接 JSON 对象包含。OpenRTB 2.3/2.4 官方仅支持 JSON 编码字符串形式，但许多交易平台已实现正式对象；请查阅各平台集成文档。Default 列规定未提供显式取值时可选参数应如何解释。译稿校对中ENThe Native Object defines the native advertising opportunity available for bid via this bid request. It will be included as a JSON-encoded string in the bid request's imp.native field or as a direct JSON object, depending on the choice of the exchange. While OpenRTB 2.3/2.4 supports only JSON-encoded strings, many exchanges have implemented a formal object. Check with your integration docs. The Default column dictates how optional parameters should be interpreted if explicit values are not provided.
| 属性 | 类型 | 必填性 | 默认值 | 描述 |
|---|---|---|---|---|
| ver | string | 可选 | 1.1 | 正在使用的 Native Markup 版本号。译稿校对中ENVersion of the Native Markup version in use. |
| layout已废弃 | integer | 推荐 | — | 原生广告位的 Layout ID。见下方 Layout IDs 表。译稿校对中ENThe Layout ID of the native ad unit. See the Table of Layout IDs below. |
| adunit已废弃 | integer | 推荐 | — | 原生广告位的 Ad unit ID。支持的核心广告位清单见下方 Ad Unit IDs 表。译稿校对中ENThe Ad unit ID of the native ad unit. See Table of Ad Unit IDs below for a list of supported core ad units. |
| context | integer | 推荐 | — | 广告出现所在的上下文。支持的上下文类型见下方 Context IDs 表。译稿校对中ENThe context in which the ad appears. See Table of Context IDs below for a list of supported context types.取值表 §7.3 Context Type IDs |
| contextsubtype | integer | 可选 | — | 广告出现所在的更详细上下文。支持的上下文子类型见下方 Context SubType IDs 表。译稿校对中ENA more detailed context in which the ad appears. See Table of Context SubType IDs below for a list of supported context subtypes.取值表 §7.4 Context Sub Type IDs |
| plcmttype | integer | 推荐 | — | 所提供广告位的设计/格式/布局。支持的广告位类型见下方 Placement Type IDs 表。译稿校对中ENThe design/format/layout of the ad unit being offered. See Table of Placement Type IDs below for a list of supported placement types.取值表 §7.5 Placement Type IDs |
| plcmtcnt | integer | 可选 | 1 | 本 Layout 中相同广告位的数量。详见 8.1 节 Multiplacement Bid Requests。译稿校对中ENThe number of identical placements in this Layout. Refer Section 8.1 Multiplacement Bid Requests for further detail. |
| seq | integer | 可选 | 0 | 第一个广告为 0，第二个为 1，依此类推。注意该字段通常不与 plcmtcnt 组合使用：要么拍卖多个相同广告位（此时 plcmtcnt>1、seq=0），要么对 feed 中不同条目分别拍卖（此时 plcmtcnt=1、seq>=1）。译稿校对中EN0 for the first ad, 1 for the second ad, and so on. Note this would generally NOT be used in combination with plcmtcnt - either you are auctioning multiple identical placements (in which case plcmtcnt>1, seq=0) or you are holding separate auctions for distinct items in the feed (in which case plcmtcnt=1, seq=>=1) |
| assets | object[] | 必填 | — | `Asset Request` 对象数组。任何竞价响应都必须符合竞价请求中所表达的元素数组。译稿校对中ENAn array of Asset Objects. Any bid response must comply with the array of elements expressed in the bid request. |
| ext | object | 可选 | — | 占位对象，可包含双方约定的自定义 JSON，以支持超出本规范所定标准的灵活性。译稿校对中ENThis object is a placeholder that may contain custom JSON agreed to by the parties to support flexibility beyond the standard defined in this specification |
注记
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.
OCR 跨页断裂：assets 描述被续表行 'the array of elements expressed in the bid request.' 截断，人工合并。
译注
译者注1.1 为分类体系过渡期：layout/adunit 已预告废弃但仍可用，context 三件套为新体系；新集成应只使用 context 三件套，接收存量流量时需兼容两套分类的并存与缺失。译稿校对中
承载形态同 1.2（imp.native JSON 串或直接对象），但本版本官方表述以 OpenRTB 2.3/2.4 为参照；对接 2.5+ 链路时以 1.2 页注为准。译稿校对中