Native image asset types
Native image asset types name the images a native ad can carry: a small square icon or a large main image. AdCOM uses the list in its image asset objects, which makes it an OpenRTB 3.0 signal. OpenRTB 2.x uses the same values in the Native 1.2 request JSON inside imp.native.request, as assets[].img.type.
Values
| Value | Name | What it means |
|---|---|---|
1 | Icon | A square icon image, typically the brand or app icon. |
3 | Main | The large main image or preview for the ad. |
500+ | Vendor-specific codes | Vendor-specific image types agreed between the parties. |
How to use it
The list skips 2. Earlier native specifications used 2 for a logo image, which was later folded into the icon type, so AdCOM carries only 1 and 3. For the main image, sellers should accept at least one of two size classes at aspect ratios of 1:1, 4:3 or 1.91:1: a small class that supports heights of at least 200 device independent pixels and a large class that supports at least 627. Declare the minimum sizes your template needs with wmin and hmin rather than exact sizes, so more creatives qualify. Values 500 and above are vendor-specific.
Common mistakes
- Requesting type 2 for a brand logo in a new integration. Ask for an icon (1); AdCOM does not define 2.
- Requesting exact
wandhfor the main image when the template can scale. Most native creatives will not match exactly and the asset goes unfilled.
Validation
On OpenRTB 2.6 snapshots, RTBlint reports a value outside this list as openrtb.value.invalid. Paste a request into the tester to check the values you send.
Related lists
- Display context types
- Display placement types
- Creative subtypes for display
- Native data asset types
- Event types
- Event tracking methods
- Click types
- Audit status codes
- Size units
All lists are on the enumerated lists index.