In-stream ad breaks
Pre-roll and mid-roll slots in structured, dynamic or hybrid pods.
Vectravia buys CTV ad breaks with OpenRTB 2.6 pod bidding, reads how ads are stitched into the stream, and checks app-ads.txt before every bid.
Connected TV (CTV) advertising places video ads in TV programs and movies streamed through apps on smart TVs, streaming sticks and game consoles. The ads run in ad breaks, much like broadcast TV, but each break is sold programmatically.
A CTV ad break is usually sold as a pod: a set of slots with a total duration. OpenRTB 2.6 added the fields that describe pods, so a buyer can bid on one slot or several, and know whether the ad will be stitched into the stream on the server.
Pod fields such as podid, podseq, poddur and slotinpod tell Omni Buy how long the break is and where each slot sits.
Path Check matches the app against its app-ads.txt file, including INVENTORYPARTNERDOMAIN for shared CTV inventory.
The imp.ssai field says whether ads and tracking are stitched server-side, client-side or a mix.
Frequency caps count CTV exposures together with your other channels, so the same home is not over-served.
Pre-roll and mid-roll slots in structured, dynamic or hybrid pods.
Ads shown when a viewer pauses, where the seller signals the format.
Placements on device or app menus, when the request carries the format signal.
Ads that share the screen with the program, signaled through format metadata.
IAB Tech Lab has added CTV-specific structure to the bid request over the last few years.
7
areas of standards in the IAB Tech Lab CTV Programmatic Guide, from ad delivery to brand suitability
Source: IAB Tech Lab, CTV Programmatic Guide,
3
kinds of ad pod in OpenRTB 2.6: structured, dynamic and hybrid
6
emerging CTV formats in IAB Tech Lab format signaling, including pause ads and overlays
CTV is measured mainly by completed views, reach and frequency. Signal Reports counts completions from VAST tracking events and labels reach and household overlap as modeled, because they are estimated rather than counted.
When ads are stitched server-side, tracking may also fire from the server. The imp.ssai value is kept with each impression so you can see which counts came from the device and which from the server.
| Standard | What it does here |
|---|---|
| OpenRTB 2.6 IAB Tech Lab | Pod bidding fields on the Video object and the imp.ssai signal for server-side ad insertion. |
| CTV Programmatic Guide IAB Tech Lab | Covers podded bidding, VAST, app-ads.txt validation and device attestation for CTV. |
| app-ads.txt IAB Tech Lab | Authorizes sellers for apps in CTV app stores; INVENTORYPARTNERDOMAIN covers shared inventory. |
Each product has its own page with the capabilities, standards and questions behind it.
One budget, pacing and frequency view across seven channels.
Supply-path checks against ads.txt and sellers.json before every bid.
Contextual targeting and brand suitability, no user ID needed.
Measured and modeled numbers, labeled apart.
In-stream and out-stream video
Streaming audio and podcasts
Screens in the real world
An ad pod is a group of ad slots played back to back in one break, like a commercial break on broadcast TV. OpenRTB 2.6 describes structured pods (fixed slots), dynamic pods (a total duration to fill) and hybrid pods (a mix).
Server-side ad insertion stitches the ad into the video stream before it reaches the TV. The imp.ssai field tells the buyer whether that happened, which affects how impressions and tracking are counted.
Path Check reads the app-ads.txt file of the app selling the slot and compares it with the SupplyChain object in the request before a bid is placed.
See how connected TV sits beside your other channels in one budget, with the supply path shown for every placement.