Wiring CTV inventory into a programmatic auction breaks in one out of three cases — not because of bad code, but because of a single missing second in the podidseq field. Ads on smart TVs start playing in random order, one creative repeats, another disappears. The DSP counts the impressions, the publisher loses fill, and engineers spend a week hunting the problem in the logs.
OpenRTB 2.6 is the first version of the IAB specification where the Ad Pod became a native object instead of an informal extension. That solved the problem of ordering creatives inside a CTV ad break, but created a new one: SSPs and DSPs treat the required pod fields differently. Below is how to build a correct bid request and where a real integration actually breaks.
What changed in OpenRTB 2.6 for CTV
In short, three things:
- The
AdPodobject moved out ofextinto the core specification (section 3.2.7).imp[].video.adpodis now an array of slots inside a single video impression. podid,podidseq,poddurandrqddursappeared — fields that describe a pod identity and the order of the slots within it.device.devicetype = 3(Connected TV) became effectively mandatory for CTV inventory, because without it DSPs do not apply CTV targeting and bids fall to display levels.
Without adpod you can still sell CTV as ordinary video inventory. But pod auctions — the primary monetization for long ad breaks on CTV — will not work.
Structure of a correct bid request for a CTV pod
The minimal working bid request for a single ad pod of three slots:
{
"id": "req-ctv-001",
"imp": [{
"id": "imp1",
"video": {
"mimes": ["video/mp4", "application/javascript"],
"linearity": 1,
"minduration": 15,
"maxduration": 30,
"protocols": [2, 7],
"startdelay": 0,
"placement": 5,
"api": [1, 2],
"adpod": [
{ "podid": 1, "podidseq": 1, "rqddurs": 30 },
{ "podid": 1, "podidseq": 2, "rqddurs": 30 },
{ "podid": 1, "podidseq": 3, "rqddurs": 15 }
]
}
}],
"app": {
"id": "app-ctv-42",
"name": "StreamFast CTV",
"cat": ["IAB1-1"],
"content": { "len": 1800, "livestream": 1 }
},
"device": {
"devicetype": 3,
"make": "Samsung",
"os": "Tizen",
"ua": "Mozilla/5.0 (SmartTV)"
},
"at": 1,
"tmax": 200,
"test": 0
}
Breakdown of the key fields
linearity: 1 — linear insertion of the creative (in-stream). For CTV this is the only valid mode; non-linear overlays on CTV players work poorly and are barely monetizable.
placement: 5 — denotes in-stream video (a value from the spec). DSPs use it to apply CTV rates. Confusing it with placement: 1 (in-banner video) lands you a banner CPM instead of CTV.
protocols: [2, 7] — supported creative delivery protocols: 2 = VAST 2.0, 7 = VAST 4.x. For CTV it is important to signal at least VAST 4.x, because only it correctly describes Mezzanine files and verification.
adpod[].podidseq — the very field. It is the sequence number of a slot inside the pod. Without it DSPs do not know in what order to place the creatives.
Lessons from the field
In practice, in 2026, SSPs often send podid correctly but omit podidseq, or send it as the string "1" instead of the number 1. DSPs receive three slots with identical (or missing) ordering and bid at random. On a smart TV it looks like this: the first break plays a competing creative, the second repeats the first, the third is empty. The publisher loses 12–18% of pod revenue until the integration is fixed.
The fix we applied at one CTV publisher: validate the bid request on the SSP side before sending it to DSPs. If adpod exists but podidseq is missing or not an integer, the SSP generates it automatically from the array index before forcing the auction. Revenue loss dropped below 2% within two weeks.
Case: right vs wrong
| Field | Wrong | Right | Consequence of the error |
|------|-------|-------|--------------------------|
| device.devicetype | missing | 3 | DSP skips CTV targeting, the bid drops to display level |
| video.placement | 1 (in-banner) | 5 (in-stream) | A banner CPM is applied instead of CTV |
| adpod[].podid | string "1" | integer 1 | DSP discards the pod and returns no-bid |
| adpod[].podidseq | missing | 1, 2, 3 per slot | Creatives play out of order or repeat |
| video.protocols | only [2] (VAST 2.0) | at least [2, 7] | CTV creatives with Mezzanine are not served |
| app.content.livestream | missing | 1 for live, 0 for VOD | DSP picks the wrong bidding strategy |
Verdict: what to do right now
- Audit your bid-request logs from the last 7 days. Filter CTV traffic by
device.devicetype == 3and confirm everyimp[].video.adpodcontainspodid(integer) andpodidseq(integer). It takes 20 minutes and uncovers 80% of the problems. - Add validation on the SSP side before forcing the auction: if
adpodexists butpodidseqis invalid, generate it from the array index. It is one function, and it pays for itself in a week. - Bump supported protocols to at least VAST 4.x (include
7inprotocols). Without it, CTV creatives with Mezzanine and verification will not pass, and you lose premium demand.
Do these three things and your CTV pod auction will start producing predictable revenue instead of a lottery.