Blog post
Priming-Based Onboarding: Convert Subscribers Before the Paywall
Most onboarding flows educate. The best ones prime subscribers to buy. Here's the psychology-backed framework for onboarding that converts.
Nami vs. Purchasely
The complete connected TV Purchasely alternative.
Purchasely covers paywalls and flows on iOS, Android, tvOS, and Android TV. Nami covers the same surfaces plus Roku, Fire TV, Samsung Tizen, LG webOS, Google TV, and Vizio, with the full subscriber journey designed once across every screen.
When each platform fits
Purchasely
For teams who want a paywall builder, journey flows, and bring-your-own-paywall architecture across iOS, Android, tvOS, and Android TV, with a smaller engineering footprint.
Nami
For enterprise teams running paywalls, pages, and subscriber journeys across every connected TV platform alongside web and mobile, with a dedicated Professional Services partnership.
Feature comparison
What each platform does, side by side.
Source for Purchasely details: purchasely.com/product and docs.purchasely.com (May 2026).
Platform coverage
 | Purchasely | |
|---|---|---|
| Web | Coming soon† | |
| iOS app | ||
| Android app | ||
| Apple TV (tvOS) | ||
| Android TV | ||
| Roku | — | |
| Fire TV | — | |
| Samsung Tizen | — | |
| LG webOS | — | |
| Google TV | — | |
| Vizio | — |
Subscriber journey scope
| | Purchasely | |
|---|---|---|
| Paywalls | ||
| Onboarding flows with conditional logic | ||
| Landing pages | — | |
| Upgrade & cross-sell screens | ||
| Win-back screens | ||
| Modals, half sheets, popovers | ||
| Conditional routing across platforms (mobile + connected TV + web) | Mobile + tvOS + Android TV only |
Experimentation
| | Purchasely | |
|---|---|---|
| A/B testing on paywalls | ||
| Multivariate testing | ||
| Experiments on landing pages, onboarding flows, and offers | Mobile and tvOS surfaces only | |
| Experiments across every connected TV platform | Apple TV and Android TV only | |
| Subscription-aware experiment results |
Architecture: bring-your-own-billing
| | Purchasely | |
|---|---|---|
| Commerce engine | Integrates: App Store IAP, Google Play IAP, Stripe, Recurly, Roku Pay, in-house | Integrates: App Store, Google Play, Huawei AppGallery, Amazon Appstore, Stripe Billing (coming soon) |
| Bring your own paywall / screen | Component-level reuse via Asset Library | Bring Your Own Paywall (BYOP), Bring Your Own Screen (BYOS) |
| Customer data platform / segmentation | Integrates: Amplitude, Adobe Experience Cloud, custom CDPs | Integrates: Adjust, AppsFlyer, Branch, Braze, Iterable, Customer.io |
| Behavioral analytics platform | Integrates: Amplitude, mParticle, Segment, Adobe | Integrates: Amplitude, Mixpanel, Google Analytics, Piano Analytics |
| Native mobile in-app purchases (App Store, Google Play) | ✓ | ✓ |
Service & pricing
| | Purchasely | |
|---|---|---|
| Engagement model | Enterprise sales-led; dedicated Professional Services partnership | Sales-led with platform support; service depth scales with plan tier |
| Pricing model | Custom enterprise pricing based on subscriber volume, platform scope, and service tier | Custom enterprise pricing; not publicly listed |
† Purchasely's product page lists JavaScript as “coming soon.” Web coverage today is delivered through the existing mobile SDKs and a web checkout pattern, not a native web paywall builder. Source: purchasely.com/product (May 2026).
Why Nami wins for enterprise teams
Why enterprise teams choose Nami over Purchasely.
Nami is built for enterprise teams from the ground up: every customer, custom-quoted pricing, a dedicated Professional Services partnership, and a no-code paywall builder that runs natively on every connected TV platform alongside web and mobile. Purchasely covers paywalls and flows on iOS, Android, tvOS, and Android TV with bring-your-own-paywall architecture and a smaller engineering footprint. For teams whose roadmap includes Roku, Fire TV, Samsung Tizen, LG webOS, Google TV, or Vizio, that's a meaningful gap.
Connected TV coverage on every platform, not just two
Purchasely supports tvOS and Android TV. Nami supports tvOS and Android TV plus Roku, Fire TV, Samsung Tizen, LG webOS, Google TV, and Vizio from the same dashboard used for iOS, Android, and the web. For streaming services and OTT platforms, the decision usually depends on which connected TV surfaces matter for the audience. Roku alone reaches more U.S. streaming households than tvOS and Android TV combined.
Enterprise scale with a Professional Services partnership
Purchasely is a focused product team shipping a capable platform. Nami is enterprise-built: every customer is paired with a Professional Services team that handles onboarding, template configuration, the first round of experiments, and ongoing optimization across mobile, web, and every connected TV platform. The depth of partnership matches the depth of platform. Some platforms try to work with the most. Nami works with the best.
The full subscriber journey designed once across every screen
Both platforms ship a no-code paywall and onboarding builder, with conditional flow logic. The Nami advantage is that the same canvas extends to every connected TV platform at first-class fidelity, not just the two surfaces with native SDKs. Landing pages, onboarding, paywalls, upgrades, and win-back, designed in one place and shipped to every screen a subscriber uses.
Switching from Purchasely
Most teams arrive here when the connected TV roadmap expands. The mobile app and tvOS app work. The Android TV app works. The Roku, Fire TV, Samsung Tizen, LG webOS, Google TV, and Vizio launches need the same caliber of paywall and journey product, on the same publish-without-an-app-release schedule. The team is ready for one platform that orchestrates every connected TV surface from the dashboard already running mobile.
Comparison FAQ
Common questions before a Nami vs. Purchasely decision.
Why do enterprise teams choose Nami over Purchasely?
Three reasons drive most decisions: connected TV breadth (Nami ships native paywall and journey support across Apple TV, Android TV, Roku, Fire TV, Samsung Tizen, LG webOS, Google TV, and Vizio; Purchasely supports tvOS and Android TV), enterprise scale with a dedicated Professional Services partnership, and the full subscriber journey designed once across every screen including the six connected TV surfaces Purchasely does not cover.
How is Nami's connected TV paywall support different from Purchasely's?
Both platforms cover tvOS and Android TV. Nami adds Roku, Fire TV, Samsung Tizen, LG webOS, Google TV, and Vizio from the same dashboard. For streaming and OTT teams, the Roku and Fire TV gap is usually the decision driver, because those two platforms reach the majority of U.S. connected TV households.
We already use Purchasely's Screen Composer and Flows. What does Nami add?
Purchasely's Screen Composer and Flows cover paywalls, onboarding, and journey logic on iOS, Android, tvOS, and Android TV. Nami covers the same scope plus the six additional connected TV platforms, plus a native web paywall builder rather than a coming-soon JavaScript SDK, plus a Professional Services partnership through rollout and ongoing optimization.
Proof at scale
Millions of subscribers served across our customer base. 99.99% uptime. SOC 2, GDPR, and CCPA compliant.