Paywalls matched to user context: +50% conversion rate
Commentary byLiftArchiveOur analysis, not theirsJourneyStamp lifted paywall conversion rate 50%, to 7.3% overall, by replacing one generic paywall with paywalls matched to where the user was in the app.
The GPS photo-stamp camera app also tested timed discounts, prices, bundles and copy along the way.
The result was published as a Superwall case study.
- Conversion rate: +50% after personalizing paywalls to the user journey.
- Overall conversion rate reached 7.3%.
- Trial starts went up, but no figure was shared.
- Many variants and changes ran together, so no single change explains the lift.
Control
A single generic paywall shown in every situation.
Variant
Different paywalls by context: single-step and multi-step paywalls in onboarding, and in-app paywalls with copy tied to the feature used, discounts shown after premium feature use, and new prices and bundles.
Why it likely won
Our reading of the result, not the practitioner's claim.
- A user who has just tried a premium feature has fresh proof of value, so a paywall shown right then may convert better.
- Copy tied to the feature someone used speaks to their actual reason for upgrading.
- Better prices and bundles found in the same program likely added to the gain.
Caveats: Context targeting, discounts, prices, bundles, copy and paywall formats all changed, so this is a bundled result, not one clean test. No sample size, duration or significance was shared. Superwall sells the paywall and testing tool used here, and its published case studies can lean positive.
Who ran it
JourneyStamp ran this test. Source: Superwall case study. The numbers are theirs; the summary and commentary on this page are ours.
How to run this test on your app
- Hypothesis
- If we show a paywall that refers to the premium feature a user just tried, then conversion rate will rise because the value is fresh and the message fits their intent.
- Primary metric
- Paywall conversion rate by placement
- Guardrails
- Proceeds per user
- Trial-to-paid conversion
- Discount usage share
- Who should test it
- Apps with several distinct premium features and paywalls that appear in more than one place. It matters less if your app has one paywall in onboarding and nothing else.
Questions
Where should a context-specific paywall appear?
JourneyStamp used onboarding and the moment after a premium feature was used.
Start with the placements that already drive the most paywall views.
Do timed discounts train users to wait for a deal?
They can. Track how many purchases use the discount and whether full-price conversion drops over time.
Should we test all these changes at once?
Bundling can find a winner fast, but you won't know which part worked.
Test placements, copy and discounts separately if you need to learn.
Similar tests
Kovalee