Native Markup Response§5.1 · Bid Response
The native object is the top level JSON object which identifies a native response. The native object has following attributes:
| Attribute | Type | Requirement | Default | Description |
|---|---|---|---|---|
| ver | string | recommended | "1.2" | Version of the Native Markup version in use. |
| assets | object[] | recommended | — | List of native ad’s assets. Required if no assetsurl. Recommended as fallback even if assetsurl is provided. |
| assetsurl | string | optional | — | URL of an alternate source for the assets object. Where present, overrides the asset object in the response. |
| dcourl | string | optional | — | URL where a dynamic creative specification may be found for populating this ad. Beta option, where present, overrides the asset object in the response. |
| link | object | required | — | Destination Link. This is the default link object for the ad. Individual assets can also have a link object. |
| imptrackers | string[] | optional | — | Array of impression tracking URLs. To be deprecated - replaced with eventtrackers. |
| jstracker | string | optional | — | Optional JavaScript impression tracker. To be deprecated - replaced with eventtrackers. |
| eventtrackers | object[] | optional | — | Array of tracking objects to run with the ad, replacing imptrackers and jstracker. |
| privacy | string | optional | — | If support was indicated in the request, URL of a page informing the user about the buyer’s targeting activity. |
| ext | object | optional | — | This object is a placeholder for custom JSON to support flexibility beyond the standard specification. |
Notes
1 The provided “assetsurl” or “dcourl” should be expected to provide a valid response when called in any context, including importantly the brand name and example thumbnails and headlines (to use for reporting, blacklisting, etc), but it is understood the final actual call should come from the client device from which the ad will be rendered to give the buyer the benefit of the cookies and header data available in that context.
Note: Prior to VERSION 1.1, the native response’s root node was an object with a single field “native” that would contain the object above as its value. The Native Object specified above is now the root object.
Note re: assetsurl format responses: In the case of assetsurl or dcourl (beta) bidding, since the ultimate buyer/creative engine cannot alter the assets response based on the details inside the assets request (as it does not receive said request), it is critical that all required assets are provided, and such communications will need to be handled offline for recommended/optional elements.
In the normal embedded response, certain attributes of the response are assumed based on matching the ID of the asset object in the response to the ID of the asset object in the request. Since the asset response will not be reading the asset request directly in this implementation, that information is added as option in the below object definitions and marked for that use case.
It is also recommended that where the standard specifies multiple options for an element, that all options be provided. IE all 4 supported thumbnail aspect ratios and all 3 supported title lengths.
The ID component of the asset responses can be omitted.
Note that this change to provide the metadata description of the asset in the response, rather than using the asset ID to implicitly specify that, may be reflected into the inline version of responses in a future version to align the two methods of replying. Making that change now would break backwards compatibility of the inline response mechanism.
Content faithfully follows the IAB Tech Lab OpenRTB Native Ads 1.2 official spec (CC-BY 3.0).