For channels and TV app developers.
FAST channel operators, single-app TV publishers and broadcasters going over the top. Integration paths, store checklists and ad load standards for the big screen.
Ads stitched server-side · per platform
Wherever your channel starts, it ends up in the auction.
Existing channel
Your stream already exists. The stitcher attaches to your existing origin; your VMAP break cadence becomes the pod plan, and verification events flow back per platform. Your content pipeline stays untouched; the monetization attaches to it.
New channel
Channel built with us from day one: break planning, pod limits and platform packaging are set up together before the first stream ships. Ad load gets designed into the content instead of retrofitted onto it, which viewers notice even if they never say so.
Existing ad server
You already sell direct. Your ad server handles what it sells; Sky Boosts competes for the rest in the same break rather than chained after it. Direct keeps its relationships and its rate card; the auction has to outbid it to win the slot.
Your sales team and our auction decide every break together.
Direct deals your team sells enter the same break as programmatic demand. Separation rules apply to both, and the decision record shows the winning price for every slot. Programmatic guaranteed and PMP fill what direct does not, open auction competes for every remaining slot, and the whole break reports as one picture.
TV app developers on Android TV and Google TV can also integrate the SDK directly with SSAI as the delivery mode, the same auction, the same reporting, where that path fits the app better than a stitch-only integration. The CTV team scopes both routes against your platform list during onboarding.
Store requirements, including the one field everything depends on.
| Platform | Developer website field | Notes |
|---|---|---|
| Google TV | Play Console store listing | Website field feeds app-ads.txt discovery; empty field blocks verification |
| Android TV | Play Console store listing | Same listing rules as Google TV builds |
| Roku | Developer portal, channel listing | Website field and channel metadata must match |
| Fire TV | Amazon developer console | Developer website required for crawl resolution |
| Samsung / LG | Confirmed during onboarding | Per-store website fields differ; we verify each |
app-ads.txt for TV apps: the developer website field on each platform points to the domain carrying your file. The specific steps are covered in the ads.txt for CTV guide, and crawl monitoring verifies every platform after launch.
Ad load policy
Agreed per channel
Break frequency and pod duration are agreed with you per channel, against content length and genre. A clip channel and a film channel carry very different ad loads, and both should feel intentional.
Published limits
Pod ceilings and break spacing come from the publisher policy and are applied when each pod is assembled, so ad load cannot drift upward unnoticed. The limits are documented, which means changes are visible instead of gradual.
Viewer-first defaults
Frequency caps and competitive separation are on by default, from the first break. Retention is the metric that protects your revenue, and ours.
Media group or single channel?
Single-channel operators onboard with the standard path. Media groups running multiple channels and sales teams work through theenterprise arrangement, with direct sales tooling, deal-level forecasting and managed service options.
Your stream, monetized end to end.
Send your channel list and content cadence. You get an SSAI path per channel and the store checklist per platform.
SSAI paths · platform checklists · Net 60