Enumerations

Layout ID is to be deprecated in a future version and is not suggested for new implementations. Below is a list of the core layouts described in the introduction above. An implementing exchange may not support all asset variants or introduce new ones unique to that system.

Ad Unit ID is to be deprecated in a future version and is not suggested for new implementations. Below is a list of the core ad unit ids described by IAB here http://www.iab.net/media/file/IABNativeAdvertisingPlaybook120413.pdf. In feed unit is essentially a layout, it has been removed from the list. The in feed units can be identified via the layout parameter on the request. An implementing exchange may not support all asset variants or introduce new ones unique to that system.

The context in which the ad appears - what type of content is surrounding the ad on the page at a high level. This maps directly to the new Deep Dive on In-Feed Ad Units. This denotes the primary context, but does not imply other content may not exist on the page - for example it's expected that most content platforms have some social components, etc.

Next-level context in which the ad appears. Again this reflects the primary context, and does not imply no presence of other elements. For example, an article is likely to contain images but is still first and foremost an article. SubType should only be combined with the primary context type as indicated (ie for a context type of 1, only context subtypes that start with 1 are valid).

The FORMAT of the ad you are purchasing, separate from the surrounding context

Below is a list of common asset element types of native advertising at the time of writing this spec. This list is non-exhaustive and intended to be extended by the buyers and sellers as the format evolves. An implementing exchange may not support all asset variants or introduce new ones unique to that system.

Below is a list of common image asset element types of native advertising at the time of writing this spec. This list is non-exhaustive and intended to be extended by the buyers and sellers as the format evolves. An implementing exchange may not support all asset variants or may introduce new ones unique to that system. In order to facilitate adoption, recommendations are made for both minimum sizes and aspect ratios. We speak here of 'minimum maximum height' or 'max height of at least', which means the SSP should support a max height of at least this value. They are free to support larger, but the DSP knows that if they have an image of this size it will be accepted. Note that SSPs will be responsible for sizing image to exact size if min-maxheight framework is used; exact size may not be available at bid request time. Width is calculated from the 3 supported aspect ratios. Note we are merging the prior overlapping type 1 and type 2 as just type 1 - to be used for app icon, brand logo, or similar.