Video.plcmt

The video placement type under the updated IAB Digital Video Guidelines, from AdCOM List: Plcmt Subtypes - Video: 1 Instream, 2 Accompanying Content, 3 Interstitial, 4 No Content/Standalone, plus CTV values 5 to 9 added later. Added in 2.6-202303 to replace Video.placement.

CurrentintegerOptionalSince 2.6-202303

Field facts

Path
imp.video.plcmt
Object
Video
Type
integer
Requirement
Optional
Added
OpenRTB 2.6-202303
Values
AdCOM list Plcmt Subtypes - Video
Spec section
3.2.7

How it is used

This is the field video buyers segment on. Instream (1) requires sound on at player start or clear intent to watch, with the video as the focus of the visit; a muted autoplay player beside an article is Accompanying Content (2). Values 5 to 9 are Pause, Screensaver, Overlay, Squeezeback, and In-scene. Full-episode and live CTV streams are normally 1. The document tagged for 2.6-202303 omitted the field, so it first appears in the spec text at 2.6-202309, and a partner pinned to an older snapshot may call it unknown.

Allowed values

ValueMeaning
1Instream: Pre-, mid-, or post-roll inside video the viewer chose, with sound on at start or clear intent to watch.
2Accompanying Content: Pre-, mid-, or post-roll in a player that sits among text or images and starts when scrolled into view.
3Interstitial: A video ad with no content video that fills most of the screen and cannot be scrolled away.
4No Content/Standalone: A video ad with no content video, placed in a feed, slideshow, article body, or floating unit.
5Pause: Added in AdCOM 1.0-202607. Shown while the viewer has paused content they chose to watch.
6Screensaver: Added in AdCOM 1.0-202607. Shown when an operating system or app screensaver starts.
7Overlay: Added in AdCOM 1.0-202607. Placed over program content while it plays, outside the ad break.
8Squeezeback: Added in AdCOM 1.0-202607. The program shrinks to share the screen with the ad and is not covered.
9In-scene: Added in AdCOM 1.0-202607. Branded elements composited into the picture of the content itself.

Example

Where the field sits in a payload, with everything else left out:

{
  "id": "req-1",
  "imp": [
    {
      "video": {
        "plcmt": 1
      }
    }
  ]
}

Common mistakes

  • Treating it as a renamed Video.placement. The lists differ, and placement 1 does not imply plcmt 1.
  • Labeling muted outstream or in-article players as 1 to earn instream prices. The request validates, but the inventory is misdescribed, and buyers audit plcmt against measured player behavior.
  • Sending it on a 2.5 request, which the validator reports as openrtb.field.not_yet_available.
  • Quoting the value, as in "1", which is an openrtb.type.mismatch.

Version history

Added in OpenRTB 2.6-202303, and present in the latest snapshot. The table shows how each version's spec text types the field.

VersionsType in the specRequiredDeprecated
2.6-202303Listed in this release's notes; IAB's tagged spec file for it does not include the field yet.
2.6-202309 to 2.6-202606integerNoNo

Versioned rules that name this field

Related fields

Other Video fields

For a walkthrough of the whole object, read Video object guide.