Plcmt subtypes (video)

Plcmt Subtypes - Video classifies a video placement by how it relates to content the viewer chose to watch: instream, accompanying content, interstitial, or no content at all, plus the CTV formats pause, screensaver, overlay, squeezeback, and in-scene added in AdCOM 1.0-202607. It is sent in Video.plcmt and replaces the list behind the deprecated Video.placement.

List: Plcmt Subtypes - Video9 valuesUsed by imp.video.plcmt

Values

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

Fields that use this list

How to use it

The list arrived with Video.plcmt. The 2.6-202303 release notes announced the field, but it first appears in the specification text at 2.6-202309, which is the first snapshot where RTBlint accepts it. Values 1 to 4 came with the field; 5 to 9 were added by AdCOM 1.0-202607 for the CTV Ad Portfolio formats. There is no vendor range, so anything outside 1 to 9 is invalid. The old Video.placement values do not map one to one onto these: classify each placement against the new definitions, and keep sending Video.placement only for buyers that have not migrated.

Common mistakes

  • Copying the old Video.placement value into Video.plcmt. Old 1 (In-Stream) is not new 1 (Instream): a muted autoplay player beside an article belongs in 2.
  • Sending 1 for a player that starts muted with no sign that the viewer asked for the video. Instream needs sound on at start or clear intent to watch.
  • Rejecting 5 to 9 on the buy side. They are valid since AdCOM 1.0-202607, and a rejection looks like a no-bid rather than an error.
  • Sending the value as a string such as "1", which RTBlint reports as openrtb.type.mismatch.

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.