该对象表示原生(native)类型的展示。原生广告单元旨在与周围内容无缝融合(如 Twitter 或 Facebook 上的赞助帖子),因此响应必须结构良好,以便发布方对渲染实施细粒度控制。Native 小组委员会(Native Subcommittee)制定了一份名为 Dynamic Native Ads API 的 OpenRTB 伴生规范,定义原生广告单元的请求参数与响应标记结构;本对象提供了将请求参数以不透明字符串传输的手段,使具体参数可在该规范的管辖下独立演进,下发的广告标记同样遵循其结构。Native 作为 Imp 的子对象出现,即表示该展示以原生类型提供;经发布方许可,同一展示还可通过在 Imp 下并列包含 banner、video 和/或 audio 类型对象的方式同时以这些类型提供,但针对该展示的任一具体出价,只能符合所供类型中的一种。译稿校对中ENThis object represents a native type impression. Native ad units are intended to blend seamlessly into the surrounding content (e.g., a sponsored Twitter or Facebook post). As such, the response must be well-structured to afford the publisher fine-grained control over rendering. The Native Subcommittee has developed a companion specification to OpenRTB called the Dynamic Native Ads API. It defines the request parameters and response markup structure of native ad units. This object provides the means of transporting request parameters as an opaque string so that the specific parameters can evolve separately under the auspices of the Dynamic Native Ads API. Similarly, the ad markup served will be structured according to that specification. The presence of a Native as a subordinate of the Imp object indicates that this impression is offered as a native type impression. At the publisher's discretion, that same impression may also be offered as banner, video, and/or audio by also including as Imp subordinates objects of those types. However, any given bid for the impression must conform to one of the offered types.
| Attribute | Type | Description |
|---|---|---|
| request required | string | 符合原生广告规范(Native Ad Specification)的请求载荷。必填(required)。译稿校对中ENRequest payload complying with the Native Ad Specification. |
| ver | string | request 所遵循的 Dynamic Native Ads API 版本;强烈建议传递,以便高效解析。译稿校对中ENVersion of the Dynamic Native Ads API to which request complies; highly recommended for efficient parsing. |
| api | integer[] | 该展示所支持的 API 框架列表。参见列表 5.6(List 5.6)。未明确列出的 API 视为不支持。译稿校对中ENList of supported API frameworks for this impression. Refer to List 5.6. If an API is not explicitly listed, it is assumed not to be supported.枚举 API Frameworks · 10 个值1VPAID 1.0 2VPAID 2.0 3MRAID 1.0 4ORMMA 5MRAID 2.0 6MRAID 3.0 7OMID 1.0 8SIMID 1.0 9SIMID 1.1 500+Vendor-specific codes. |
| battr | integer[] | 被拦截的创意属性。参见列表 5.3(List 5.3)。译稿校对中ENBlocked creative attributes. Refer to List 5.3.枚举 Creative Attributes · 24 个值1Audio Ad (Autoplay) 2Audio Ad (User Initiated) 3Expandable (Automatic) 4Expandable (User Initiated - Click) 5Expandable (User Initiated - Rollover) 6In-Banner Video Ad (Autoplay) 7In-Banner Video Ad (User Initiated) 8Pop (e.g., Over, Under, or Upon Exit) 9Provocative or Suggestive Imagery 10Shaky, Flashing, Flickering, Extreme Animation, Smileys 11Surveys 12Text Only 其余 12 个值见枚举总览 → |
| ext | object | 供交易平台(exchange)对 OpenRTB 进行专属扩展(exchange-specific extensions)的占位对象。译稿校对中ENPlaceholder for exchange-specific extensions to OpenRTB. |
译注
译者注Native:Imp 的子对象,其出现即表示该展示以原生类型提供;业内文档一般保留英文对象名 Native。原生广告单元旨在与周围内容无缝融合(如 Twitter 或 Facebook 上的赞助帖子),因此响应必须结构良好,以便发布方对渲染实施细粒度控制。译稿校对中
Dynamic Native Ads API:Native 小组委员会(Native Subcommittee)制定的 OpenRTB 伴生规范,定义原生广告单元的请求参数与响应标记结构,业界惯称“Native 规范”(Native Ad Specification)。译稿校对中
request 的不透明字符串设计:请求参数以不透明字符串形式传输,使具体参数的演进独立于 OpenRTB 主体、由 Dynamic Native Ads API 另行管辖;解析时应按 ver 声明的版本对照 Native 规范解码,不应假设其内部结构。同理,下发的广告标记也遵循该规范的结构。译稿校对中
多类型同售:经发布方许可,同一 Imp 可同时以 banner、video 和/或 audio 提供(在 Imp 下并列包含对应类型对象);但针对该展示的任一具体出价,只能符合所供类型中的一种。译稿校对中
api / battr:支持的 API 框架与拦截的创意属性均为枚举数组(列表 5.6 / 5.3);未明确列出的 API 视为不支持,与 Banner 的同名字段语义一致,但此处针对原生创意的渲染框架与属性约束。译稿校对中
字段描述已与 2.6 官方 draft 对账;2.5 独有字段来自第三方 Go 实现源(Apache 2.0),官方 PDF 兜底校对 · 初稿校对中