Blog post
The Paywall Experiment Velocity Gap: Blame the Release Cycle
Most subscription teams know what to test. The bottleneck is the release window. Here's how A/B testing paywalls without an app release changes the math.
Campaigns
Run targeted cross-platform subscription campaigns.
Product and marketing build the campaign in Nami, target the audience, pick the placement, and publish. Updates ship live across CTV, web, and mobile through the SDK already running in your product. No code to write, no engineering release to schedule.
- CTV
- Web
- Mobile
Q3 Winback · CTV
Publishing Audience
Placement
Win-back screen Lapsed flow
A/B split · 2 segments
Subscriber experiences don't have a creative problem. They have an assignment problem.
When the engineering backlog keeps you from running cross-platform campaigns, subscribers get a default experience and revenue stalls.
Campaigns runs the assignment without code. Product and marketing pick the audience, placement, and schedule, then publish live through the SDK. No app release, no engineering ticket.
Audience, placement, schedule. Every assignment your app needs, configured in one place.
01
Assign the right experience to the right moment
Placements are the named trigger points in your app where subscriber experiences appear: onboarding, paywall, upgrade prompt, win-back. Assign a page or flow to a placement, set the targeting rules, and the right experience surfaces to the right subscriber. The SDK handles delivery, so no code change is required after the initial integration.
Onboarding
Welcome flow
Paywall
Annual offer page
Upgrade prompt
Tier comparison
Win-back
Lapsed flow
02
Reach the exact subscriber segment, on the exact surface
Define audience rules with AND/OR logic across platform, OS version, device form factor, language, country, GeoIP, and CDP audience segments. Run a campaign to free-trial subscribers on Roku, new subscribers in Brazil, or any combination your business needs. Audiences is built into Campaigns, so there's no separate integration and no separate tool to learn.
PlatformRoku OR PlatformFire TV
AND StatusFree trial AND CountryBrazil
AND CDP segmentHigh intent Add rule
03
Every campaign becomes a structured way to learn what converts
Each campaign supports up to 10 audience segments, each pointed at a different page or flow. Set the traffic allocation to match the test plan, and every campaign that ships becomes a learning opportunity for that audience at that moment. Experiments runs on this same primitive, so campaigns are how experimentation moves from a one-off ticket to a continuous practice.
Annual offer page 40%
Monthly + trial 30%
Lifetime flow 20%
Control 10%
04
Reach subscribers before they log in
Anonymous Mode runs campaigns on pre-authentication surfaces: landing pages, initial onboarding, top-of-funnel offers. Conversion decisions happen early in the subscriber journey, and the campaign shouldn't wait for authentication to start working.
Landing page
Pre-auth
Initial onboarding
Pre-auth
Top-of-funnel offer
Pre-auth
Subscriber logs in — campaign keeps running
Cross-platform
One campaign on every screen, from the connected TV paywall to mobile.
Campaigns run on iOS, Android, Apple TV, Roku, Fire TV, Samsung, LG, Vizio, Xbox, Google TV, Chrome, Safari, and Edge.
Targeting, segments, and scheduling work the same across CTV, web, and mobile. No platform-specific workaround, no separate team per surface.
One source · 13 destinations
- iOS
- Android
- Apple TV
- Roku
- Fire TV
- LG
- Samsung
- Vizio
- Xbox
- Google TV
- Chrome
- Safari
- Edge
Designed, not assembled.
Every campaign that ships is a subscriber experience delivered by intention.
Millions in revenue uplift across our customer base. Not from whatever was hardcoded last sprint, but from a system that lets product and marketing decide which experience a subscriber sees in the same place they design it.
Campaigns is the routing layer in subscription orchestration.
Pages and Flows are where your team designs subscriber experiences. Experiments tests variants of them. Insights reads what happened. Campaigns is the layer that decides which subscriber sees which experience and where it shows up. Because every campaign supports up to 10 audience segments, Campaigns is also the surface where Experiments operates at scale.
You are here
Campaigns
The routing layer that puts the right subscriber experience in front of the right audience. Audiences and A/B segmentation built in.
Pages
Builds the screens inside each campaign.
Flows
Connects pages into multi-step subscriber journeys.
Experiments
Optimizes variants within every campaign segment.
Insights
Connects campaign outcomes back to revenue.
Questions teams ask before they buy.
What's the difference between Campaigns and Experiments?
Campaigns assigns the pages and flows your team built to specific moments in the app and to the audiences who should see them. Experiments compares variants of those assignments to find what converts. Both are part of subscription orchestration: the practice of designing, testing, and optimizing the complete subscriber journey across every platform, from one system, without code.
Does updating a campaign require an app store release?
No. The Nami SDK runs inside your app and reads campaign configuration from Nami. Once the SDK is integrated, campaign changes ship to subscribers without an engineering release or an app store update. That includes audience rules, schedules, A/B splits, and the page or flow assigned to a placement.
How does audience targeting work?
Define rules with AND/OR logic across platform, OS version, device form factor, language, country, GeoIP, and CDP audience segments. Rules combine to reach narrow segments or stay broad. Saved audiences carry across multiple campaigns, so the same logic doesn't get rebuilt every time.
Can we use our existing CDP audiences for targeting?
Nami supports Custom Audience targeting today, with Amplitude integration on the roadmap and Adobe Experience Cloud available by arrangement. Segments already defined in your CDP feed directly into Campaigns targeting, so the audiences your team built don't get rebuilt inside Nami.
When should we use Anonymous Mode?
Anonymous Mode is for campaigns that need to surface before a subscriber logs in: landing pages, initial onboarding, top-of-funnel offers. Conversion decisions happen early in the subscriber journey, and the campaign shouldn't wait for authentication to start working.
The right subscriber experience, in front of the right audience, on the right screen.
Book a demo to see how product and marketing teams ship coordinated subscriber experiences across CTV, web, and mobile without filing an engineering ticket.