Slot position in pod

Slot Position in Pod says which slot of an ad pod a seller can guarantee, or which slot a bid is limited to: first, last, first or last, or any. Requests carry it in Video.slotinpod and Audio.slotinpod, and a bid can restrict itself with Bid.slotinpod. All three fields arrived in OpenRTB 2.6 and default to 0.

List: Slot Position in Pod4 valuesUsed by imp.audio.slotinpod, seatbid.bid.slotinpod, imp.video.slotinpod

Values

Value	Name	What it means
`-1`	Last ad in the pod	The last slot of the pod, just before the content resumes.
`0`	Any ad in the pod	Any slot: no position guarantee on a request and no restriction on a bid. This is the default.
`1`	First ad in the pod	The first slot of the pod, right after the content stops.
`2`	First or Last ad in the pod	Either the first or the last slot, without saying which.

Fields that use this list

How to use it

On a request the value is a seller guarantee: the impression will fill that slot. On a response it is a condition: the bid is only valid if placed in that slot. The fields replace the deprecated Video.sequence and Audio.sequence, which numbered impressions for coordinated delivery rather than naming an edge of the pod. Do not confuse this list with Pod Sequence, which reuses 1, 0, and -1 for the position of the whole pod in the content stream.

Common mistakes

Sending 1 when the seller cannot actually guarantee the first slot. Buyers pay for edge positions and check delivery logs.
Reading Bid.slotinpod 0 as anything other than no restriction. It is also the default when the field is absent.
Mixing up Video.slotinpod and Video.podseq, which share numbers but answer different questions.

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.