Android TV and Google TV share one app ecosystem: Android apps distributed through Google Play with a TV-specific review track. It is the most technically open CTV environment — and the one with the widest device variety. This page gives the general picture — platform rules change, so confirm details in the current Android and Google Play documentation.
Register as a publisher and choose your inventory type: CTV app, FAST channel or web video.
We check verification files, audience quality and measurement hygiene before any commercial terms.
Revenue model, payment schedule and reporting granularity are agreed with you in writing.
Ad demand is connected through the integration route that fits your stack: SDK, VAST, SSAI or S2S.
Apps are standard Android packages with a TV interface layer: remote-control navigation, a leanback-style UI, and declaration of TV support in the manifest so the app appears in Google Play on televisions. The device range is enormous — from operator set-top boxes to built-in TV systems — so performance testing across chipsets matters more here than on any other CTV platform.
In-stream video dominates: pre-roll and mid-roll breaks with 15 or 30 second creatives. The Android media stack supports client-side ad insertion through standard ad libraries as well as VAST-tag playback, and SSAI for live and FAST content. Display formats inside the app UI — home-screen rails, pause-screen placements — are possible in your own interface, subject to Google Play policy on advertising content.
The most common stack is the platform's standard video player with a client-side ad library handling VAST responses, measurement and ad break scheduling; alternatively a VAST tag called by your own player logic, or SSAI where ads are stitched into the stream. Client-side insertion gives full beacon control; SSAI gives smoother playback and resilience. Many publishers run CSAI for on-demand content and SSAI for live channels in the same app.
Before connecting demand: pass the TV review track in Google Play, which applies specific requirements to TV apps; publish app-ads.txt and reference it in your store listing; test ad playback and measurement on both high-end and low-end devices — VAST timeouts that never appear on a flagship box are common on older hardware; and keep ad frequency within both store policy and your retention data. Platform rules change — check current Google Play and Android TV requirements before release.
Every CTV platform updates its store policies, certification requirements and advertising rules several times a year. Nothing on this page replaces the platform's own current documentation: before building or monetizing, confirm the requirements in the official developer and seller portals. If you want an experienced read on your setup, register as a publisher — inventory review comes before any commercial discussion, and terms are agreed individually.
Yes — each CTV platform has its own app format and store. Some code and all of your content pipeline can be shared across platforms, but the app package and store submission are platform-specific.
Non-skippable in-stream video — 15 and 30 second pre-roll and mid-roll — is the standard unit buyers pay for on every CTV platform. Additional UI formats depend on the platform and your app.
For on-demand apps, an SDK or client-side VAST is the simplest start. For live and FAST streams, SSAI is the practical standard. The VAST and SSAI page in this hub compares the options in detail.
Practically yes: serious demand sources filter out inventory without it. Publish app-ads.txt and reference it in your store listing before connecting monetization.
Yes — ad serving and SSAI are platform-independent; only the app-side player integration differs. Most multi-platform publishers run one ad stack behind all their apps.
It varies by platform and by submission. Plan release schedules with a buffer, and check the platform's current review documentation rather than relying on older experience.
Impression, start, quartile and completion events, plus error callbacks — on real hardware, across the device generations you target. Measurement that only works in an emulator will under-report or be rejected by buyers.
Revenue share, payout schedule and minimums are agreed individually with each publisher and confirmed in writing before the first campaign. No rates are promised before your inventory is reviewed.