Home/CTV

The same one-hop model, on the biggest screen in the home.

Connected TV has the same problem in-app had: long reseller chains, undisclosed sellers and server-side insertion that buyers cannot verify. We apply the model that fixed it for apps. Direct publishers, curated deals, a public supply chain, and signals that do not depend on an identifier.

01Why CTV needs direct

Premium screens, opaque paths.

CTV budgets grew faster than CTV standards. Most supply chain tooling was designed for web and app, and the gaps show up exactly where the money is.

A

Invalid or missing supply chains

A large share of CTV requests arrive with incomplete schain objects or sellers that no sellers.json names. Buyers cannot tell a publisher from a reseller from a spoofed app.

B

Server-side insertion without visibility

SSAI stitches ads into the stream, which is good for playback and bad for verification. Without the publisher's cooperation, buyers see what the stitcher tells them.

C

Supply surplus, concentrated spend

Buyers retreat to a handful of large apps because they cannot evaluate the rest. FAST channels and mid-tier publishers with real audiences go under-monetized.

02Supply

Direct CTV publishers and FAST channels, nothing resold.

We work with CTV app publishers and FAST channel operators under the same terms as our in-app publishers: a direct agreement, DIRECT in app-ads.txt, a named entry in sellers.json, and a single hop to the buyer.

For publishers, this is brand demand planned for their channel rather than remnant fill. For buyers, it is CTV inventory they can audit in the same files they already check.

  • CTV appsPublisher-owned apps on Roku, Fire TV, Apple TV, Android TV / Google TV, Samsung and LG, sold directly
  • FASTFree ad-supported streaming channels and their operators, with pod and slot control exposed at the deal
  • SSAIServer-side insertion with publisher-provided transparency: verified device signals, pod positions and measurement beacons
  • AuthorizationDIRECT in app-ads.txt, named in sellers.json, complete schain on every request

03CTV deals

Curated the way agencies plan television.

CTV is planned by genre, daypart, pod position and household reach, not by placement ID. Our deals are built on those terms.

StructureBest forPricingWhat's inside
Genre PMP
Private marketplace
Always-on brand campaigns with content control Fixed floor Named CTV apps and FAST channels by genre: sports, news, entertainment, kids-safe, lifestyle. Daypart and frequency constraints at the deal.
Pod-position deal
First-in-pod · mid-roll
Campaigns where attention and recall matter most Fixed price Reserved pod positions with publisher-confirmed placement. Attention-qualified by our scoring.
Programmatic guaranteed
PG
Tentpole content, live events, launches Fixed price, guaranteed impressions Reserved volume in specific channels or apps with agreed pacing, delivered through the buyer's DSP.
Cross-screen deal
CTV + in-app
Reach and frequency managed across TV and mobile Fixed floor per screen One deal structure spanning our CTV and in-app supply, with household-level frequency control where consented signals allow it.

04Cross-screen

TV and mobile, planned together.

Agencies increasingly plan CTV and mobile as one budget. Because our in-app and CTV supply are sold by the same company under the same terms, a buyer can run both in a single deal structure with shared frequency and one line of reporting.

This is the cross-screen case that resellers cannot offer honestly: they do not own either side.

05Attention & context

Signals for a screen with no identifier and no cursor.

Our data platform applies the same supply-side approach to CTV: describe the impression, not the viewer. On television, that means content, pod position, time and the likelihood someone is actually watching.

Content context

Genre, programme category, live versus on-demand, kids-safe status, expressed in standard content taxonomies.

Pod & position

Pod length, slot position, ad count, time since last break. Known on the supply side, invisible from the DSP.

Predicted attention

Likelihood the ad plays to a present viewer, modelled from daypart, content, pod position and completion history per channel.

Quality

Device verification, SSAI consistency checks, authorization status and invalid-traffic filtering before the request is offered.

06Audio for CTV

The television is also the biggest speaker in the house.

A growing share of TV time is audio-first: music and radio apps on the TV OS, ambient and visualizer channels, screensaver and idle states. That inventory is sold like TV and heard like radio, and almost nobody packages it well.

Audio apps on TV platforms

Music, radio and podcast apps running on the TV OS. Audio spots with a companion display unit on screen, served in the app's natural breaks.

Ambient & visualizer channels

FAST channels built around music and ambient content, where the screen is secondary and the audio carries the message.

Idle & screensaver moments

Audio-led placements in idle states and screensavers, with a companion visual, planned as reach at low frequency.

Why it belongs in the same deal

Audio on the TV reaches the same household as the video pod, through the same publisher relationship and the same supply chain files. We package it as a line inside a CTV deal or as a stand-alone audio deal, with the same DIRECT authorization and the same reporting.

  • Formats15s and 30s audio spots, companion display (static or lightweight animated), audio-led pause and idle placements
  • DeliveryVAST 4.x audio with companion ads, DAAST-compatible where the publisher requires it
  • TargetingContent and mood context, daypart, device class; no listener-level identifiers
  • MeasurementListen-through and companion render rates, reported with the rest of the CTV deal

07Specs

Built on the standards buyers already verify.

For buyers

Activate CTV deals in the DSP and through the SSPs you already use. Nothing new to integrate.

Protocol
OpenRTB 2.6 with CTV extensions (pod, slot, content)
Video
VAST 4.x, server-side and client-side
Measurement
OMID for CTV where supported; standard verification vendors
Supply chain
Complete schain, one node, Inception as seller of record
Identity
Context and household-safe signals only; consent and platform rules honoured
Reporting
Daily per deal, channel or app, pod position and outcome

For CTV publishers

A direct publisher agreement, one authorization line, and brand demand planned for your channel.

Integration
OpenRTB endpoint from your SSAI or ad server; Prebid-compatible
Platforms
Roku, Fire TV, Apple TV, Android TV / Google TV, Samsung, LG
Authorization
DIRECT in your app-ads.txt; named in our sellers.json
Control
Your floors, your pod rules, your category blocks, applied per deal
Audio
VAST audio with companions for audio-first apps and channels
Payout
Single transparent revenue share, reported per deal and buyer

Bring the one-hop model to your TV plan.

Buyers get a CTV deal list. Publishers get an onboarding plan. Both get the same supply chain.