Video.placement

The legacy video placement type, from the five-value list OpenRTB 2.5 introduced: 1 In-Stream, 2 In-Banner, 3 In-Article, 4 In-Feed, 5 Interstitial/Slider/Floating. Deprecated as of 2.6-202303 in favor of Video.plcmt, which uses a different list.

Deprecated since 2.6-202303integerOptionalSince 2.5

Field facts

Path
imp.video.placement
Object
Video
Type
integer
Requirement
Optional
Added
OpenRTB 2.5
Deprecated
OpenRTB 2.6-202303
Spec section
3.2.7

How it is used

The 2.6-202303 release deprecated it, and the current spec text says so, although the document tagged for that release still listed it without a marker; the spec text first shows it deprecated at 2.6-202309. Deprecated does not mean removed. Buyers that never migrated still read it, so sellers commonly send both fields during the transition, each value chosen from its own list. In 2.5 a full-screen interstitial was told apart from a floating unit with Imp.instl.

Example

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

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

Common mistakes

  • Mapping old values to new ones one to one. A muted autoplay player sold as placement 1 often qualifies only as Video.plcmt 2, Accompanying Content.
  • Sending only this field on current 2.6 traffic. It still parses, with an openrtb.field.deprecated warning, but buyers that filter on Video.plcmt see the inventory as unclassified.
  • Writing plcmt values here. 4 in this list means In-Feed, not No Content/Standalone.

Version history

Added in OpenRTB 2.5, deprecated in 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.5 to 2.6-202303integerNoNo
2.6-202309 to 2.6-202606integerNoYes

Versioned rules that name this field

Related fields

Other Video fields

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