Product update
Flow Builder Error States
Catch broken Flow Builder steps before subscribers do.
Nami for Connected TV
CTV is where your next subscriber lives. And where most subscription tools stop.
The screens where subscribers actually watch are also the ones a typical subscription stack ignores. Nami brings the full subscriber experience layer to every CTV platform, from the same dashboard you use for mobile and web. Design pages, run experiments, coordinate campaigns, and measure outcomes without filing an engineering ticket.
Every TV, one dashboard
Built for the screens where subscribers actually watch.
Every major CTV operating system, managed alongside iOS, Android, and the web.
The problem
You launched on CTV. Then the experience layer stalled.
You launched on CTV because the audience moved there. Growth made the case, engineering shipped the apps, the subscriber base started showing up on the big screen. Then the experience layer stalled.
Every change to a CTV paywall — a new headline, a different price layout, a holiday promotion — turns into a sprint and a store submission. The mobile team tested four paywall variants this week; the CTV team is still waiting on a build for one. The marketing team running a winter campaign on iOS can't reach the same subscribers on Apple TV, because the platforms are managed in different tools, by different people, on different timelines.
The numbers tell the story. CTV subscribers convert at lower rates, churn earlier, and never see the offers being tested elsewhere — not because TV viewers behave differently, but because the experience built for them was the last priority. Most subscription tools were built mobile-first. They added web later. CTV is still a roadmap promise.
Subscription orchestration — the practice of designing, testing, and optimizing the complete subscriber journey across every platform from a single system, without code — is what closes the gap. It's the difference between owning the experience layer on every screen and renting it from your engineering team.
See how subscription orchestration works How Nami solves it
The full subscriber experience layer, on every TV.
Six things teams using Nami for CTV stop waiting on engineering for.
Design subscriber experiences on every TV without engineering
Pages, paywalls, and onboarding screens render natively on each platform — Apple TV's focus engine, Roku's grid navigation, Samsung's remote-control patterns, the way Fire TV handles overlays. A visual editor and a component-based system handle the layout, typography, imagery, and interaction patterns. Update once, deploy across the whole CTV footprint.
Connect CTV pages into complete subscriber journeys
Onboarding, conversion, upgrade, win-back — every screen connects through a no-code flow builder that branches on the data you already have. A trialist on Roku gets a different upgrade path than a churned subscriber on Fire TV. Test new flows without code, ship them in hours, and measure the result before the week is out.
Run experiments at the same velocity as the mobile team
A/B and multivariate testing on pages, prices, and flows — built for the way subscribers actually convert on TV. Configurable traffic splits and subscription-aware results so the team can read each test honestly. The experimentation engine running on iOS and web runs the same way on every major CTV platform.
Coordinate one campaign across every screen
A holiday promotion, a price test, a lapsed-subscriber win-back — campaigns are defined once and assigned to placements across CTV, web, and mobile. Audience targeting, scheduling, segment allocation, and priority ordering are unified. Marketing finally gets to run cross-platform without rebuilding the campaign for every device.
See subscription performance across the full TV footprint
Subscription-aware analytics surface conversion rates, revenue, and experiment outcomes by platform, country, and campaign. Apple TV against Roku, paid traffic against organic, Q3 against Q4 — the comparisons that matter are one filter away. Nami integrates with the analytics tools you already use; the Insights layer fills the subscription-specific gap.
Launch with a partner, not just a platform
Professional Services configures templates for each CTV platform, sets up your first campaigns, and partners on the experimentation roadmap. CTV is its own kind of complex — store policies, certification cycles, focus design, remote-friendly interaction patterns. Nami's team has shipped on every platform and knows where the friction is.
Proof points
Teams running subscription orchestration on Nami ship new experiences in hours, not sprints, and run high-velocity experimentation across the whole subscriber journey. Millions in revenue uplift across our customer base, with up to 99.999% uptime. The result across customer deployments: a 12% average conversion lift.
Integrations
Your stack stays.
Your stack stays.
Nami fits in.
Nami works alongside your existing billing, analytics, and engagement tools.
Plus CDP, ESP, app store, and CTV partners.
See all integrations
Connected TV FAQ
What CTV teams ask before the first call.
Which CTV platforms does Nami support?
Nami runs on Apple TV, Roku, Fire TV, LG, Samsung, Vizio, Xbox, and Google TV — every major CTV operating system. The same dashboard manages CTV alongside iOS, Android, and the web (Chrome, Safari, Edge). Subscription orchestration — the practice of designing, testing, and optimizing the complete subscriber journey across every platform from a single system, without code — runs the same way on each.
How does Nami fit alongside our existing CTV billing setup?
Nami sits at the experience layer, not the billing layer. Apple App Store, Google Play, and Roku Pay continue to handle store-side commerce. Stripe and Recurly continue to handle web subscriptions. Nami orchestrates the subscriber-facing pages, flows, experiments, and campaigns above that infrastructure, integrating with the systems already in place.
Do CTV experience changes still require store submissions?
No. The pages, flows, and campaigns running on Nami publish from the dashboard — no app store submission, no engineering build, no certification cycle for content changes. The SDK ships once with your CTV app; everything that renders inside it updates remotely.
We already use a paywall tool for mobile. Why add CTV through a different system?
Paywall tools cover one moment, on the platforms they were built for. Most are mobile-first or mobile-only. Nami covers landing pages, onboarding, paywalls, upgrade screens, and campaigns across CTV, web, and mobile from one system. Teams consolidating onto Nami typically replace three to five tools with one.
How much engineering lift does the CTV SDK take?
One SDK integration per CTV platform, completed once during onboarding. After that, every page, flow, experiment, and campaign updates remotely from the Nami dashboard — no app store submissions for content changes. Most teams reach productive use in weeks, with Professional Services partnering on integration and template configuration.
Subscription teams across streaming, media, news, education, and lifestyle ship the full CTV experience on Nami.
Bring every TV into the same dashboard you already use for mobile and web — and stop waiting on a build to test the next paywall.