Display placement types

Display placement types describe where a native or display ad appears relative to the surrounding content: inside a feed, inside a single piece of content, outside the content, or in a recommendation widget. In AdCOM the list feeds the display placement's ptype, an OpenRTB 3.0 signal. OpenRTB 2.x uses the same values in the Native 1.2 request JSON field plcmttype, inside imp.native.request.

List: Display Placement Types5 values

Values

Value	Name	What it means
`1`	In-feed	Inside a feed of content, as an item in a list, grid or carousel.
`2`	In the content unit	Inside a single piece of content, such as an article page or a single image page.
`3`	Outside the core content	Outside the main content, such as in a right rail ad section or a banner-style slot near it.
`4`	Recommendation widget	A recommendation widget, usually shown below an article.
`500+`	Vendor-specific codes	Vendor-specific placement types agreed between the parties.

How to use it

Pair the placement type with a display context type so the buyer knows both where the ad sits and what surrounds it. For Native 1.2 requests on OpenRTB 2.x, send plcmttype and context inside the request string. Native 1.1 replaced the 1.0 layout and adunit fields with those two, and 1.2 deprecated the old fields. Do not confuse this list with the video placement lists behind Video.plcmt and Video.placement, which use different numbers for different things.

Common mistakes

Sending Native 1.0 layout or adunit instead of plcmttype in a 1.1 or 1.2 request. rtblint reports layout as openrtb.native.layout_removed.
Using 3 for a native unit placed in a feed because it is visually distinct. If it sits among the feed items, it is 1.

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

All lists are on the enumerated lists index.