Native 分册导航
Native Markup Request§4.1 · Bid Request
`Native Markup Request` 对象定义本次竞价请求中可供出价的原生广告机会。依交易平台（exchange）的选择，它以 JSON 编码字符串形式包含在竞价请求的 imp.native 字段中，或作为直接 JSON 对象包含。OpenRTB 2.x 官方仅支持 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.x officially 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.2 | 正在使用的 Native Markup 版本号。译稿校对中ENVersion of the Native Markup version in use. |
| context | integer | 推荐 | — | 广告出现所在的上下文。支持的上下文类型见下方 Context Types 表。译稿校对中ENThe context in which the ad appears. See Table of Context IDs below for a list of supported context types.取值表 §7.1 Context Type IDs |
| contextsubtype | integer | 可选 | — | 广告出现所在的更详细上下文。支持的上下文子类型见下方 Context SubTypes 表。译稿校对中ENA more detailed context in which the ad appears. See Table of Context SubType IDs below for a list of supported context subtypes.取值表 §7.2 Context Sub Type IDs |
| plcmttype | integer | 推荐 | — | 所提供广告位的设计/格式/布局。支持的广告位类型见下方 Placement Types 表。译稿校对中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.3 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. |
| aurlsupport | integer | 可选 | 0 | 供应源/广告展示是否支持返回 assetsurl 而非资产对象。0 或缺失该字段表示不支持。译稿校对中ENWhether the supply source / impression supports returning an assetsurl instead of an asset object. 0 or the absence of the field indicates no such support. |
| durlsupport | integer | 可选 | 0 | 供应源/广告展示是否支持返回动态创意优化（DCO, Dynamic Creative Optimization）URL 而非资产对象。0 或缺失该字段表示不支持。Beta 特性。译稿校对中ENWhether the supply source / impression supports returning a dco url instead of an asset object. 0 or the absence of the field indicates no such support. Beta feature. |
| eventtrackers | object[] | 可选 | — | 声明支持的事件追踪类型——见 `Event Trackers Request` 对象。译稿校对中ENSpecifies what type of event tracking is supported - see Event Trackers Request Object. |
| privacy | integer | 推荐 | 0 | 当原生广告支持买方专属隐私声明时置 1；当不支持自定义隐私链接或支持情况未知时置 0（或缺失该字段）。译稿校对中ENSet to 1 when the native ad supports buyer-specific privacy notice. Set to 0 (or field absent) when the native ad doesn’t support custom privacy links or if support is unknown. |
| 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.
译注
译者注承载形态：OpenRTB 2.x 官方口径为 JSON 编码字符串（需转义后放入 imp.native），但实践中不少 Exchange 同时接受直接对象。对接前应以 Exchange 集成文档确认接收侧解析能力；字符串转义问题可用站内 Escape/Unicode 工具排查。译稿校对中
assets 数组是「菜单」而非「清单」：响应必须按其中的 id 逐一应答，请求未声明的资产不应出现在响应里；反之请求声明 required 的资产缺失时，Exchange 通常直接弃标。译稿校对中
eventtrackers 与 privacy 都是能力声明字段：前者声明可用的追踪事件/方式，后者声明是否支持买方隐私声明页。请求未声明支持时，响应不得携带对应内容，否则可能被判定不合规。译稿校对中