How LG webOS apps work
webOS TV apps are built with standard web technology — HTML, CSS and JavaScript — packaged for the platform and submitted through LG's seller portal, where they pass content and technical review before distribution. Video playback uses the platform's media APIs. As with all TV platforms, hardware capability varies by model year, so test on the generations your audience actually owns.
Ad formats on the platform
In-stream video is the primary ad unit: pre-roll and mid-roll breaks with 15 or 30 second non-skippable creatives, played through the app's media layer. Client-side VAST playback and SSAI are both used; for linear and FAST content SSAI is the practical standard. UI-level placements such as pause screens belong to your app interface and are governed by current platform policy on advertising content.
How advertising is integrated
Integration follows the same three routes as other CTV platforms: a compatible third-party ad SDK; direct VAST-tag calls from the player with client-side measurement; or SSAI with device-side beacon reporting. Because webOS apps are web apps, browser-like debugging applies — use remote debugging on a real TV to confirm that all measurement events fire and that ad playback does not stutter on older hardware.
What a publisher should verify
Before connecting demand: pass LG's current app review, including its advertising policies; publish app-ads.txt and reference it from your store listing; validate VAST or SSAI playback and measurement on real webOS hardware across model years; and set ad frequency from your own retention data within platform policy. Platform terms change — check LG's current seller documentation before release.
Platform rules change
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.
FAQ
Q.Do I need a separate app for LG webOS?
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.
Q.What ad format earns the most on CTV?
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.
Q.SDK, VAST or SSAI — which should I choose?
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.
Q.Is app-ads.txt required?
Practically yes: serious demand sources filter out inventory without it. Publish app-ads.txt and reference it in your store listing before connecting monetization.
Q.Can I run the same ad server across platforms?
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.
Q.How long does store review take?
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.
Q.What measurement should I test before launch?
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.
Q.What commercial terms apply?
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.
Become a publisher