[KonstantinMirin]

Draft. Do not merge until the working group confirms the disposition of #89.

What this changes

A line item can now state what every impression is: rewarded, interstitial, video placement subtype, skippability, playback, API frameworks, and refresh. placement (§ 5.2, § 5.2.1) is a seller-set object keyed to AdCOM 1.0 Placement and OpenRTB 2.6 Imp. A present key holds for every impression, and an absent key doesn't constrain. The seller MUST NOT deliver the line item to an impression that doesn't match a present key, and the text says what a match is for each key. plcmt is REQUIRED for video ads. In app_mobile and ctv, a line item that commits viewable_rate SHOULD NOT offer a third-party measurement_source unless api[] includes OMID 1.0 (7). The Summary Representation (§ 2.1) carries reward, instl, plcmt, and skip when present.

Related issue

Refs #89, a change request from Postindustria (IAB Tech Lab member).

Type

• Editorial — no normative effect
• Normative — changes what the spec requires
• Breaking — would break an implementation already built to this draft
• Examples / schema / docs only

Checklist

• The body section is updated — § 2.1, § 5.2 and new § 5.2.1, new § 6.5
• Appendix A (field index) matches the body — one row, placement seller-set; scripts/check_appendix.py passes
• Appendix B (fields by marker, and the counts) matches the body — seller-set 29 → 30; 71 → 72 fields
• Any affected example in examples/ is updated and still parses — the CTV example gains placement: { plcmt: 1 } (Instream (1)), which REQUIRED plcmt needs; new line-item-rewarded-video.yaml (§ 6.5)
• RFC 2119 keywords used deliberately — MUST / SHOULD / MAY are not synonyms
• The no-inheritance rule (§ 2) still holds — placement sits on the line item; nothing comes from the proposal or a property
• Anything selectable declares available[] and included[]; anything settable declares bounds (§ 3.1, § 3.2) — no new selectable or settable fields
• No confidential or commercially sensitive content

Knock-on effects

• Breaking. A video line item without placement.plcmt no longer conforms.
• Answered on [Change] § 5.2 — Say what each impression is: rewarded, interstitial, video placement, skippability, API frameworks, refresh #89 (questions 1, 3, and 5). @fgranata (#89) says reward, instl, plcmt, and skip match what they hold per placement, and that they can declare OMID 1.0 (7), MRAID, and, for banners, refresh.min_interval_s. They also note that rewarded and interstitial of the same duration clear at very different rates (first raised on OQ-4 — The format registry has no entries for audio/*, ctv/* or dooh/* #5). Per the reply, placement sits on the line item, and a multi-app line item omits the keys its apps don't share (question 3). The text states that an absent reward or instl means either value (question 5). @fgranata maps such a line item to one OpenDirect 2.1 Placement per value, so the reply adds no "either" marker. The OM SDK rule stays a SHOULD, which @fgranata supports because some vendors still measure in-app with their own SDKs (question 1).
• plcmt on ctv. This PR follows [Change] § 5.2 — Say what each impression is: rewarded, interstitial, video placement, skippability, API frameworks, refresh #89's proposed text: plcmt is REQUIRED for video on ctv. The supporting material is corrected to match.
• Matching. The text says what a match is, following the downstream mapping in the supporting material. An impression matches api[] when it supports every listed framework, playmethod[] when its method is listed, refresh when it renders each creative for at least min_interval_s seconds, and any other key when the value is equal. Keys take integers or integer arrays, and plcmt, playmethod[], and api[] take any code in their AdCOM list.
• One plcmt per line item. plcmt is one value and REQUIRED for video, so a video line item whose impressions differ in plcmt splits into one line item per value. That's how @fgranata handles apps that disagree (question 8 below).
• feed. [Change] § 5.2 — Say what each impression is: rewarded, interstitial, video placement, skippability, API frameworks, refresh #89's row names feed as REQUIRED for audio, but [Change] § 5.2, § 5.9 — Audio: name the feed, and say when an ad is recorded into the content #101 defines the key. This PR leaves feed out; [Change] § 5.2, § 5.9 — Audio: name the feed, and say when an ad is recorded into the content #101 adds it to § 5.2.1.
• connected_device. [Change] § 5.2 — Say what each impression is: rewarded, interstitial, video placement, skippability, API frameworks, refresh #89's question 2 named the connected_device environment from [Change] § 5.1, § 5.2 — Define channel and environments in AdCOM terms, so one impression gets one label #90. [Change] § 5.1, § 5.2 — Define channel and environments in AdCOM terms, so one impression gets one label #90's revision removes that value and puts Connected Device (6) in ctv, so the rule's ctv covers those devices once [Change] § 5.1, § 5.2 — Define channel and environments in AdCOM terms, so one impression gets one label #90 lands. Under [Change] § 5.1, § 5.2 — Define channel and environments in AdCOM terms, so one impression gets one label #90, placement type doesn't change the channel: rewarded in-app video stays channel video with placement.reward: 1.
• OQ-4 — The format registry has no entries for audio/*, ctv/* or dooh/* #5. Answers @fgranata's either/or without a placement_type enum or placement in format ids. App-open stays a format id with instl: 1.
• [Change] § 5.4 — Validate assets[].format_ref against the resolved formats selection at submission, not at creative review #32 and [Change] § 5.7: Bind each committed metric to the measurement source that settles it #38. placement.api[] gives creative review a list to check MRAID and SIMID creatives against; whether review does so is question 3 below. [Change] § 5.7: Bind each committed metric to the measurement source that settles it #38's counts[].tracking says how a vendor counts; api[] says whether it can run. [Change] § 5.7: Bind each committed metric to the measurement source that settles it #38's vendor: seller would give the OM SDK rule's "vendor other than the seller" a value to check. This PR leaves the § 5.7 measurement_source row unchanged, because [Change] § 5.7: Bind each committed metric to the measurement source that settles it #38 rewrites it.
• Downstream. Keys map to OpenRTB 2.6 imp.rwdd, imp.instl, video.plcmt, video.skip, video.skipafter, video.playbackmethod, banner.api, video.api, audio.api, and imp.refresh.refsettings[].minint. All but refresh are in AdCOM Placement, which OpenDirect 2.1 AdUnit.spec and Placement.spec carry. AdCOM names plcmt VideoPlacement.ptype.
• Example and PR § 5.2 — App identity on properties (#15) #17. The rewarded example uses the properties shape on main. PR § 5.2 — App identity on properties (#15) #17 makes each property carry domains or apps, so whichever merges later gives puzzle-pack an apps[] entry (platform, bundle, storeurl, domain). The two merge without a textual conflict, but § 5.2 — App identity on properties (#15) #17's App identity paragraph then lands inside § 5.2.1 and needs to move above it.
• Other PRs. The PR for [Change] § 5.1, § 5.2 — Define channel and environments in AdCOM terms, so one impression gets one label #90 also adds a § 5.2.1. Because the environments row comes before the placement row, environments keeps § 5.2.1 and placement becomes § 5.2.2, whichever merges first; the See 5.2.1 reference in the placement row changes with it. PRs § 2, § 4.1, § 5.6 — Line-item dependencies and bonus lines (#23) #70 and § 2.3 — Static manifest at a well-known URL for standard proposals (#29) #76 each add a § 6.5, so the rewarded-video example is renumbered after them, with its (spec § 6.5) header. The PR for [Change] § 5.1, § 5.2 — Define channel and environments in AdCOM terms, so one impression gets one label #90 also edits the § 5.2 table next to the new row. PR § 2, § 4.1, § 5.6 — Line-item dependencies and bonus lines (#23) #70's line-item-ctv-bonus.yaml is CTV in-stream video without placement, so whichever merges later adds placement: { plcmt: 1 } (Instream (1)) to it. PR § 2.3 — Static manifest at a well-known URL for standard proposals (#29) #76's manifest.json carries the Summary Representation, so whichever merges later adds "placement": { "plcmt": 1 } to its weather-app-ctv entry. Other open change requests also change the Appendix B counts.

For the working group

Open on #89 and its supporting material:

1. Should the OM SDK rule also cover a non-seller counter in controlling_measurement (#95), or stay limited to measurement_source? (#89, question 2, without the removed connected_device value)
2. When @unreconciled's interactive and verification format spec keys on #5 and placement.api[] disagree, which governs, or should the spec carry only one? (#89, question 4)
3. Should creative review check MRAID and SIMID creatives against placement.api[], although #32 limits review to content and policy? (#89 supporting material, question 1)
4. Should app-open ads get a value in AdCOM, or stay a registry format id with instl: 1? (#89 supporting material, question 2)
5. Should plcmt be REQUIRED on dooh video line items, and on native line items with video assets, which #90 assigns to those channels? The OpenRTB 2.6 implementation guide's DOOH video example sends no plcmt. (#89 supporting material, question 3)
6. Should refresh stay one minimum interval, or also name the triggers in AdCOM List: Auto Refresh Triggers? (#89 supporting material, question 4)
7. No field says whether a ctv line item sells video, which the REQUIRED condition on plcmt depends on. Should the condition key on the format ids in formats.available[], or should plcmt be RECOMMENDED on ctv? (#89, question 6)
8. Should plcmt stay one value, so that a video line item whose impressions differ in plcmt splits, or become plcmt[], like playmethod[]? (#89, question 7)

---

By opening this pull request I agree my contribution may be published under this
repository's licence, as set out in CONTRIBUTING.md.

Analyzed and generated with the help of Claude, fully reviewed by me.