9 paywall placements to test before you change pricing
Nine paywall placement hypotheses to test before changing price. Rheo controls when users reach paywall; integration owns paywall UI.
Teams reach for pricing changes when growth stalls. Price is visible, finance cares, and boards understand it. Often the cheaper win is paywall placement: when you ask, after how much value, and with what context. Placement tests frequently beat five percent price cuts on trial rate, without touching App Store product configuration.
Rheo does not manage, design, or optimize paywall UI. Your RevenueCat, Superwall, or custom integration owns the paywall surface and billing. Rheo orchestrates native journeys and controls when users reach the paywall step. This listicle gives nine placement hypotheses to run before you change price.
How to read this list
Each item is a placement experiment, not a paywall template test. Keep offerings and paywall UI stable. Change journey structure and timing in Rheo. Measure paywall step reach, trial start (from billing events), and downstream retention.
| Signal placement helped | Signal you still need a price test |
|---|---|
| Paywall reach up, trial rate flat | Reach stable, trial rate down |
| Qualified users arrive with intent | Users dismiss immediately on all paths |
| Step funnel improves before paywall | Competitors undercut on price |
Run one placement test at a time when traffic is under 10k installs per week.
1. End of onboarding vs gate before core value
Hypothesis: Users convert better after they see one concrete outcome, not before account creation.
| Control | Variant |
|---|---|
| Paywall immediately after signup | Paywall after first "aha" action |
Measure: paywall reach, trial start rate, D1 retention.
Why before pricing: If users never understood value, lower price will not fix dismiss rate.
2. After stories / sequential value beats vs before
Hypothesis: Three short value screens increase willingness to pay more than a single long pitch.
| Control | Variant |
|---|---|
| One feature screen then paywall | Three story beats then paywall |
Measure: completion per beat, paywall reach, trial start.
Native note: Rheo renders stories-style sequences as native steps, not a WebView carousel bolted on late.
3. Soft paywall vs hard gate
Hypothesis: Letting users skip once increases eventual conversion vs blocking all access.
| Control | Variant |
|---|---|
| Must subscribe to continue | Skip with limited free tier |
Measure: skip rate, delayed trial start within 7 days, paid conversion at D30.
Caution: Soft paywall affects product analytics definitions. Align trial_started and activated_free in your tracking plan.
4. Post-permission vs pre-permission
Hypothesis: Asking for ATT or push after paywall improves permission grant without hurting trial.
| Control | Variant |
|---|---|
| ATT before paywall | ATT after trial start |
| Push before paywall | Push after activation |
Measure: permission grant rate, paywall reach, trial start.
Common win: deferring ATT until after value often lifts both grant rate and paywall quality.
5. Trial-start paywall vs feature-triggered paywall
Hypothesis: Contextual paywall when user hits a limit converts better than upfront trial.
| Control | Variant |
|---|---|
| Paywall on first launch channel | Paywall on third export / save / session |
Measure: trigger rate, trial start per active user, revenue per DAU.
Placement insight: feature-triggered paths delay revenue but can lift LTV. Test before cutting price for top-of-funnel volume.
6. Paywall on return visit vs session one only
Hypothesis: Users who return on day one are warmer than session-zero installs.
| Control | Variant |
|---|---|
| Paywall on first open | Paywall on second open if no trial |
Measure: session-two reach, trial start, cannibalization of organic exploration.
Low-traffic apps: this test needs enough day-one returners. Check cohort size before committing.
7. Onboarding paywall vs settings paywall
Hypothesis: Some segments prefer discovering paywall when they intentionally upgrade.
| Control | Variant |
|---|---|
| Mandatory onboarding paywall step | Onboarding ends free; prominent settings upgrade |
Measure: onboarding completion, settings paywall views, total trial starts within 14 days.
Segment tip: paid acquisition cohorts often need onboarding placement; organic power users may convert from settings.
8. Win-back placement after lapse vs only at cancel
Hypothesis: Showing save offer at cancel plus on return after lapse recovers more subs than cancel-only.
| Control | Variant |
|---|---|
| Offer only in cancel flow | Cancel offer plus day-3 lapse channel |
Measure: save rate, resubscribe rate, support tickets.
Rheo role: lifecycle channels for cancel and win-back are journey placement, not paywall UI redesign.
9. Paywall before vs after account linking
Hypothesis: Social sign-in before paywall reduces friction; paywall before sign-in filters serious users.
| Control | Variant |
|---|---|
| Signup then paywall | Paywall preview then signup on purchase |
Measure: signup completion, paywall reach, trial start, account quality proxy (D7 actions).
Compliance: store rules and regional laws affect account-before-purchase requirements. Legal review before variant B.
Placement test setup checklist
| Step | Action |
|---|---|
| 1 | Freeze paywall UI and offerings in billing tool |
| 2 | Document control journey screenshot by step |
| 3 | Create variant in Rheo with one placement change |
| 4 | Assign 50/50 on target channel |
| 5 | Fire billing events with placement property |
| 6 | Pre-register 2-4 week runtime |
| 7 | Read step funnel before purchase metrics |
Metrics that matter for placement tests
| Metric | Owner |
|---|---|
| Paywall step reach | Rheo step funnel |
| Time from install to paywall | Rheo + analytics |
| Trial start | RevenueCat / billing |
| Paywall dismiss rate | Billing integration events |
| D7 / D30 retention | PostHog or Amplitude |
| Revenue per install | Analytics + billing |
Do not optimize placement for paywall views alone. A earlier paywall can inflate views and hurt trial quality.
When placement tests justify a pricing test
After placement wins plateau:
| Observation | Next test |
|---|---|
| High reach, high dismiss | Paywall UI template in RC / Superwall |
| High trial, low renewal | Product value or pricing, not placement |
| Segment diverges | Targeted placement rules by attribution trait |
| Competitor price gap | Pricing or packaging in billing config |
Pricing tests belong in RevenueCat offerings and store configuration. Placement tests belong in Rheo journey graph.
What not to conflate
| Paywall placement (Rheo) | Paywall UI (integration) |
|---|---|
| When user sees purchase step | How packages are laid out |
| Journey steps before purchase | Headline and CTA on sheet |
| Branch on dismiss | Intro offer badge |
| Channel entry rules | A/B on template |
Changing both in one experiment confounds results. Serialize placement first, UI second.
Summary
Before you change pricing, test paywall placement across nine hypotheses: timing relative to value, permissions, triggers, return visits, lifecycle moments, and signup order. Rheo controls when users reach the paywall step in native journeys. Your billing integration owns paywall UI and purchase. Win placement first, then decide if price still needs to move.
Start for free and run your first placement experiment before the next pricing meeting.