Guide

The CTV ad ecosystem, for web advertisers.

How advertising is served on connected TV, who the actors are, how deals differ from web programmatic, what targeting on a television can and cannot use, and where the transparency gaps are that buyers check.

SSAI end to endThe actorsDeal typesACR and targeting reality

Break markers to stitched pods

01How CTV advertising is served

SSAI, end to end, for a reader who knows web advertising. On the web, the page calls an ad server, the response renders in a container, and measurement fires from the browser. A television stream cannot work that way: the content arrives as a continuous segmented stream, and interrupting it for a client-side ad call means buffering wheels in the living room. So the ad decision moves upstream. The content manifest carries markers for planned breaks. A stitching server takes each break marker, requests advertising for the pod from the SSP, and splices the winning creatives into the stream as if they were content segments. The viewer's player never knows an ad decision happened: playback is continuous, transitions are cuts, and measurement fires from the stream's timing rather than from a page.

The vocabulary, fixed once: CTV is video consumed on a TV screen delivered over an internet connection, on smart TVs, streaming devices (set-top boxes and dongles), game consoles or pay-TV boxes. OTT, over the top, is the umbrella for TV-like content delivered over the internet on any device. VOD is on-demand content, which splits into SVOD (subscription), BVOD (broadcaster) andAVOD (ad-supported), and FAST channels are linear-style streams monetized entirely by advertising. The terms overlap by design and are used loosely in the market; what matters operationally is where the breaks fall and who owns the listing.

02The actors

  • TV platforms and stores. Google TV, Android TV, Roku, Fire TV and the rest: they ship the devices and the app stores, and they control the metadata fields, such as the developer website, that transparency depends on.
  • FAST channel operators. They assemble linear, ad-supported channels, either their own or distributed through platform channel stores. They decide the content cadence the ad pods must fit.
  • Publishers. App developers with streaming applications, VOD libraries or both.
  • SSPs. Auction the pod slots to programmatic demand and stitch demand sources together with the operator's direct sales where both exist.
  • DSPs and agencies. Buy programmatically or assemble guaranteed packages for advertisers.
  • Measurement providers. Verify delivery, reach and frequency from stream beacons, where platform capability allows them to.

03Deal types on CTV

The same three structures exist as on the web: open auction, private marketplace, programmatic guaranteed. What changes is the weight. Guaranteed commitments and direct deals carry more of CTV budgets than of web budgets, because television buyers are used to booking audiences in advance, and premium placement rarely trades purely on the open exchange. For an operator this means the direct path, your sales team or your agency relationships, is not legacy; it is half the revenue model, and the platform must let direct and programmatic compete in one break rather than chain them.

04Targeting reality

ACR, automatic content recognition, is fingerprinting of what the screen is actually showing, collected by certain TV platforms for their own advertising products. It enables exposure-based targeting and measurement on devices that carry no cookies, and it arrives with real privacy constraints: it is device level data governed by platform terms and regional privacy law, and it is not uniformly available across platforms. Device-level targeting on CTV means household and device identifiers from the platform, IP-derived geography, and app-declared metadata such as content genre. A campaign plan that assumes web-style user-level targeting across every TV platform is planning against hardware that does not exist.

05Measurement and currency

CTV measurement is fragmented and described here neutrally: reach and frequency are measured across pods and platforms with different signal availability; verification partners support CTV to different degrees per platform; and there is no single cross-platform currency that every buyer and seller treats as final. In practice, delivery metrics come from server-side beacons, incremental verification is scoped per platform, and campaigns that need a single currency negotiate it per deal. Anyone selling you uniform CTV measurement across all platforms is ahead of the hardware.

06Transparency problems

The web solved supply path verification with ads.txt; CTV inherited the fix late and unevenly. The gaps: developer website fields are sometimes empty on TV platforms because nothing in the submission flow forces them; channel operators without a real website have nowhere obvious to publish a file; and per-store metadata can point at different domains for the same operator. What buyers check: that the app-ads.txt resolves from each platform's listing, that sellers.json names the account, and that the schain node matches. Operators who keep those three aligned per store are verifiable; the rest are where spoofing hides. Our ads.txt for CTV guide is the operational manual for staying on the right side of that check.

07Market data

Third-party figures on programmatic CTV spend, with named sources and years: IAB's advertising revenue reports have tracked CTV's share of the digital market year over year, and eMarketer/Insider Intelligence publishes yearly US programmatic CTV spend forecasts. Both publish figures at the market level; this guide does not restate them from memory. The benchmarks report carries the inventory-side ranges we can stand behind with methodology attached.

08Where it is heading

Two consolidations are visible without speculation dressed as fact. Ad serving and supply are consolidating: platforms ship their own ad managers, and SSPs integrate closer to the stitching layer, so the distance between content and auction shortens. Supply path transparency is consolidating: app-ads.txt coverage on TV stores improves each year as buyers demand it, and the operators who fixed their metadata early are the ones whose inventory verifies cleanly today. Both trends reward the same operator behavior: publish the artifacts, keep them current, and let demand verify you.

Because the ad is stitched into the stream before delivery. The player receives continuous video and never makes an ad call, which is why SSAI is the standard on television.

Cross-screen frequency requires a shared identifier between devices, which exists only where platforms and consent allow it. Within CTV, pod-level caps apply reliably; cross-screen caps are deal-specific.

It is verifiable when the app-ads.txt chain resolves from every store listing you operate on. The checker tests one listing at a time; account-level monitoring covers all of them.

Open auction for immediate demand density, with PMP or guaranteed lines layered as the audience stabilizes. Direct deals work best once delivery history exists to forecast against.

Operate the ecosystem

Understand the room before the buy.

The CTV monetization page covers the platform side; the ads.txt for CTV guide covers verification. Both are the practical companions to this overview.

SSAI · actors · deals · targeting reality