Skip to content

How Common Are In-Flow Paywalls Across All App Flows, Not Just Onboarding?

  • By Ali Abouelatta
  • n = 2,467
  • Published
  • Updated
  • 2 min read
  • paywall · monetization · ux-patterns · saas · mobile

Short answer

Across all 2,467 canonical flows tracked by Lazyweb Research, 318 (13%) contain a paywall step, and those paywalls sit at an average relative position of 0.85 source[1]. The late-flow pattern holds corpus-wide, not just in onboarding. Separately, 193 flows are dedicated standalone paywall flows source[2].

The quotable stat
318 of 2,467 canonical flows (13%) contain a paywall, at avg relative position 0.85, Lazyweb Research, July 2026.

The finding

Looking beyond onboarding, 318 of 2,467 canonical flows with steps contain a paywall (13%), spanning 385 paywall steps of 10,811 total flow steps source[1]. The average relative position of those paywall steps is 0.849 — essentially the same late-flow placement observed inside onboarding (0.851) source[1]. The convention of placing paywalls near the end is not unique to onboarding.

Corpus-wide vs onboarding

ScopeFlowsWith paywallRateAvg paywall position
All canonical flows2,46731813%0.849
Onboarding flows1294031%0.851

Onboarding flows paywall at more than double the corpus rate, but both place the paywall at the same late position source[1]source[3].

Dedicated paywall flows

Separately from in-flow paywalls, 193 flows across 163 companies are dedicated paywall flows — flow names containing 'paywall' such as 'Paywall', 'Paywall 2', or 'Welcome back paywall' source[2]. Many apps ship the paywall both inside a flow and as its own standalone surface, so an app without an in-onboarding paywall may still monetize elsewhere.

Caveats

Rates are floors because the paywall flag is sparse (NULL on 21,824 of 23,407 screens) source[4]. Positions are computed with ROW_NUMBER, never raw step numbers source[1].

Real in-market screens

Screens from real, in-market apps, tracked by Lazyweb Research.

  • Rakuten Account Setup screen — real in-market example tracked by Lazyweb Research
    Rakuten1179 × 2556opens the full image
  • Gauthmath Account Setup screen — real in-market example tracked by Lazyweb Research
    Gauthmath1206 × 2622opens the full image
  • Reddit paywall screen — real in-market example tracked by Lazyweb Research
    Reddit1125 × 2436opens the full image
  • Allrecipes Account Setup screen — real in-market example tracked by Lazyweb Research
    Allrecipes1206 × 2622opens the full image

The numbers

#StatComputed from
[1]318 of 2,467 flows (13%); 385 paywall steps of 10,811; avg position 0.849all_flows_context
[2]193 dedicated paywall flows across 163 companiesdedicated_paywall_flows
[3]31% (40 of 129) onboarding; avg paywall position 0.851onboarding_flows_with_paywall / avg_relative_position_paywall_steps_onboarding
[4]is_paywall NULL on 21,824 of 23,407 screensuniverse

Methodology

Universe: 2,467 canonical flows with steps (10,811 steps) across ~800 tracked apps, July 2026; positions via ROW_NUMBER. Caveat: sparse paywall flag makes rates floors.

Sources

  1. [1]

    Lazyweb Research analysis of 2,467 canonical flows (~800 tracked apps), July 2026

    All flows with steps; paywall detections and avg relative position via ROW_NUMBER.

    Back to text

  2. [2]

    Lazyweb Research analysis of 193 dedicated paywall flows (~800 tracked apps), July 2026

    Flow names containing 'paywall' across 163 companies.

    Back to text

  3. [3]

    Lazyweb Research analysis of 129 onboarding flows (~800 tracked apps), July 2026

    Onboarding rate and paywall-step position for comparison.

    Back to text

  4. [4]

    Lazyweb Research analysis of 23,407 canonical screens (~800 tracked apps), July 2026

    Sparse is_paywall flag; all rates are floors.

    Back to text

Source: Lazyweb Research — proprietary analysis of real, in-market app screens. Cite as Lazyweb Research, 2026-07-07.

Explore the evidence