What an SSP actually does for app and CTV publishers
A plain-English walk through a single ad request, from the moment an app asks for an ad to the moment one appears, and what a supply-side platform does at every step.
Blog CTV
OpenRTB 2.6 gave connected TV the vocabulary it was missing: ad pods, exact creative durations, prices per second and better content signals. A field-by-field guide for sellers and buyers.

For years, connected TV was sold through a protocol designed around single display slots. A CTV ad break, with several ads of different lengths competing for a fixed amount of time, had to be squeezed into it through custom extensions that every partner implemented differently. OpenRTB 2.6, from IAB Tech Lab, made the TV break a first-class concept. If you sell or buy CTV programmatically, these are the parts worth knowing.
An ad pod is a group of ads shown together in one break. In OpenRTB 2.6, a pod is described with ordinary impression objects that share a pod identifier on the Video object:
| Field | What it describes |
|---|---|
podid | Identifies the pod. Impressions with the same podid belong to the same break. |
podseq | Where the pod sits in the content stream, such as the first, last or a middle break. |
slotinpod | Which slot in the pod the seller can guarantee: first, last or any. |
poddur | For dynamic pods, the total number of seconds buyers may fill. |
maxseq | For dynamic pods, the maximum number of ads that may be served into the pod. |
rqddurs | The exact creative durations the seller can accept, in seconds. Useful for live TV, where breaks have fixed lengths. |
mincpmpersec | A floor for the dynamic part of a pod, expressed per second of creative. |
The spec distinguishes three kinds of pod. A structured pod has a fixed number of slots, each described as its own impression. A dynamic pod only says how much time is available (poddur) and how many ads may fill it (maxseq), and buyers return bids to fill it. A hybrid pod combines structured slots with a dynamic portion.
On the response side, a bid can say which slot it is targeting with slotinpod, and give the creative’s duration in seconds with dur, so the seller can assemble a break that fits. rqddurs cannot be combined with minduration and maxduration: a request either lists exact acceptable durations or a range.
Fifteen-second and thirty-second ads do not have the same value, and a single CPM floor treats them as if they did. OpenRTB 2.6 lets a seller express value per second:
mincpmpersec sets a floor per second of creative, on a video or audio impression or on a deal.durfloors, a list of floors for duration ranges, for example one floor for ads up to 15 seconds and another for longer ones.For sellers, per-second floors protect long breaks from being filled cheaply. For buyers, they make it clear what a slot costs before bidding.
CTV buyers care what the ad runs next to. OpenRTB 2.6 gave the Content object room to describe the program better, including two new objects: network (the network the content is on) and channel (the channel within it). A buyer can now tell the difference between two FAST channels from the same network, or between a channel and the app that distributes it, without relying on custom extensions.
Related to this, the Site and App objects gained inventorypartnerdomain, which ties a request to the inventory-sharing declarations publishers make in their app-ads.txt files. When a distributor sells breaks that belong to a content owner, buyers can match the request to the owner’s authorization.
Two things that used to live in extensions are now standard fields:
source.schain, listing every advertising system that handled the impression. (Here is how buyers use it.)Regs and User objects: regs.gdpr and user.consent for the TCF consent string, regs.us_privacy for the older US privacy string, regs.gpp and regs.gpp_sid for the Global Privacy Platform, and regs.coppa for child-directed inventory.Standard locations matter more than they sound. A signal in a standard field is a signal every partner can find and honor; a signal hidden in a custom extension is one that can be dropped along the way.
For sellers:
slotinpod. If a break has fixed lengths, use rqddurs.content, network and channel where you can. Better context is better pricing.For buyers:
dur and slotinpod so your ad can be placed.network and channel for brand safety and planning instead of guessing from the app name.schain against app-ads.txt and sellers.json.ManaForge supports OpenRTB 2.6 for server-to-server connections, including CTV ad pods. If you want to walk through a request together, get in touch.
Share your inventory and what you want to achieve. Let’s find where Arcaneflow fits.