Native 分册导航
Asset Request§4.2 · Bid Request
交易平台（exchange）代表渲染客户端所请求或支持的每个资产的主容器对象。必需的对象须显式标记。每个对象中 {title,img,video,data} 只应存在其一，其余应为 null/absent。id 在 `Asset Request` 数组内须唯一，以便响应可以对齐。译稿校对中ENThe main container object for each asset requested or supported by Exchange on behalf of the rendering client. Any object that is required is to be flagged as such. Only one of the {title,img,video,data} objects should be present in each object. All others should be null/absent. The id is to be unique within the AssetObject array so that the response can be aligned.
| 属性 | 类型 | 必填性 | 默认值 | 描述 |
|---|---|---|---|---|
| id | integer | 必填 | — | 唯一资产 ID，由交易平台分配，通常为数组下标计数。译稿校对中ENUnique asset ID, assigned by exchange. Typically a counter for the array. |
| required | integer | 可选 | 0 | 若该资产为必需（缺少它交易平台将不接受出价）则置 1。译稿校对中ENSet to 1 if asset is required (exchange will not accept a bid without it) |
| title | object | 推荐 | — | 标题资产的 `Title Request` 对象；见 TitleObject 定义。译稿校对中ENTitle object for title assets. See TitleObject definition. |
| img | object | 推荐 | — | 图像资产的 `Image Request` 对象；见 ImageObject 定义。译稿校对中ENImage object for image assets. See ImageObject definition. |
| video | object | 可选 | — | 视频资产的 `Video Request` 对象；见 Video 请求对象定义。注意插播类（in-stream，如 preroll 等）视频广告不属于 Native；Native 广告可以将视频作为广告创意本身包含。译稿校对中ENVideo object for video assets. See the Video request object definition. Note that in-stream (ie preroll, etc) video ads are not part of Native. Native ads may contain a video as the ad creative itself. |
| data | object | 推荐 | — | 品牌名、描述、评分、价格等的 `Data Request` 对象；见 DataObject 定义。译稿校对中ENData object for brand name, description, ratings, prices etc. See DataObject definition. |
| 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 |
注记
To be more explicit, it is the ID of each asset object that maps the response to the request. So if a request for a title object is sent with id 1, then the response containing the title should have an id of 1.
New in version 1.1 of the spec, there are recommended sizes/lengths/etc with some of the asset types. The goal for asset requirements standardization is to facilitate adoption of native by DSPs by limiting the diverse types/sizes/requirements of assets they must have available to purchase a native ad impression. While great diversity may exist in publishers, advertisers/DSPs can not be expected to provide infinite headline lengths, thumbnail aspect ratios, etc. While we have not gone as far as creating a single standard, we've honed in on a few options that cover the most common cases. SSPs can deviate from these standards, but should understand they may limit applicable DSP demand by doing so. DSPs should feel confident that if they support these standards they'll be able to access most native inventory.
scope 'recommended 1'：1 为表下脚注（each asset object may contain only one of title, img, data or video）。
OCR 跨页断裂：img/video/data 三行位于续表，人工合并。