Skip to content
AppDues
Log in
Contact salesSign up

When to Show a Paywall: Timing, the Aha Moment, and What to Measure

Showing a paywall too soon can push people away, while waiting too long can hide the price until users have already drifted off. The practical answer is not simply earlier or later. It is to place the offer where the product's value is already clear, make the price visible before frustration builds, and then test each placement against real behaviour.

Why showing the paywall sooner can work

Conventional advice often delays the paywall until a user has completed several actions. That caution made sense when people were unfamiliar with subscriptions, but expectations have changed. Many users now meet paywalls in several digital services and may prefer knowing the cost upfront rather than discovering it after investing time.

Early exposure does not have to mean an abrupt sales pitch. If onboarding explains what the app does, shows a useful result, and then presents the subscription as the next step, the paywall can feel like a continuation of the journey. The key distinction is between interrupting before value is understood and presenting the offer immediately after value becomes concrete.

Greg, a plant-care app, illustrates the change. It previously waited until a user added a sixth plant before showing the paywall. It then showed the paywall during onboarding for all users and shifted from usage-based to feature-based access, so even one plant's water reminders required a subscription. Trial sign-ups rose by approximately 400%, and sign-up-to-trial conversion increased from 3% to 15%. Those figures came from changing timing and the monetisation model together, so they should not be treated as proof that timing alone caused the full result.

Use the aha moment as the timing signal

The aha moment is the point at which a user understands what the app can do for them. Reaching it quickly matters because a large share of new users may leave before they ever experience the main benefit. If that is happening, describing the product and its price before the aha moment may be more honest and more effective than waiting for a moment many users never reach.

PhotoRoom provides a clear pattern. During onboarding, a user adds a photo and removes the background, experiencing the core result almost immediately. The paywall follows that successful action, while the value is still fresh. The sequence is: let the user do something meaningful, show the result, then offer continued access.

Citizen approaches the same problem through narrative. Its onboarding builds a story before the paywall appears, so the offer is connected to the user's reason for opening the app. Rootd, a mental-wellness app, moved its paywall earlier in onboarding despite concern that it might feel intrusive for people dealing with panic and anxiety. The reported outcome was a 5X increase in revenue. Together, these examples point to context rather than a universal rule: users respond better when the paywall explains why it is appearing now.

Placements worth testing

Start by mapping the moments where a paywall could plausibly appear. For new users, test before onboarding and after onboarding. For existing users, test before they use a locked core feature and after they have used that feature. Also consider showing it on app open and before a locked feature, both before and after onboarding. Beginning with several placements gives you evidence about which moments help and which create friction.

A useful placement checklist is:

  • Identify the first action that demonstrates the core benefit.
  • Place one test immediately after that action.
  • Place another test before the user attempts a locked feature.
  • Add a test during or just after onboarding for new users.
  • Keep the message tied to the action the user just took or is about to take.
  • Remove placements that consistently drive people away without producing subscribers.

Babbel's Sylvain Gauchet compares hiding a price to entering a shop with no prices on anything. Some users will leave when they see a paywall early, but those users may never have intended to pay. The more useful question is whether the placement reaches people who are ready to convert. That is why placement testing should be paired with exposure measurement rather than judged only by complaints or short-term churn.

Measure exposure, then keep testing

Do not judge a placement only by whether it appears in the flow. Measure what percentage of users actually encounter the paywall and how often they see it. Analytics tools such as Amplitude or Mixpanel can show whether users are reaching the screen at all. If very few people see it, the problem may be discoverability rather than the offer itself.

Use A/B testing to compare placements for your own audience. A placement that works for a plant-care app, a photo editor, or a mental-wellness app may not work for yours. Keep the winners, remove the losers, and repeat the process as behaviour and market expectations change. A placement that performed well last year may need to be retested this year.

Bottom line

Early paywalls can increase subscriptions when they arrive after the user understands the value. Greg and Rootd show the potential upside, PhotoRoom shows how to create value quickly, and Citizen shows how to make the offer feel contextual. The strongest process is to test several placements, measure how many users actually see each one, and keep refining the sequence as user behaviour changes.

Frequently asked questions

What happened when Rootd moved its paywall earlier?

Moving the paywall earlier in onboarding produced a 5X increase in revenue for Rootd, according to the example described.