Quick answer
A paywall is a barrier that asks people to pay or subscribe before they can read content or use a feature. A hard paywall blocks everything, a soft one leaves some content free and a metered one allows a set number of free uses first. Judge it by reach, tap rate and completion rate.
Formula: Paywall conversion rate = purchases ÷ paywall views; purchases ÷ new users = reach × tap rate × completion rate
What is a paywall?
A paywall is a barrier that asks people to pay or subscribe before they can read content or use a feature. The term began with news sites that put articles behind a subscription, and it now covers any screen in a website or app where access stops until a payment is made: a locked article, a premium filter in a mobile app, an export button, a higher usage limit. A page described as paywalled is one that sits behind such a barrier.
Two things are worth separating from the start. The paywall is the moment and place where payment is asked, not the pricing, the free tier or the trial that surround it. And a paywall can be judged only by what happens at that moment: how many people reach it, how many show interest, and how many complete the purchase. Everything below turns on those three counts.
Hard, soft and metered paywalls
The three common types differ in how much a visitor can see before the wall appears.
| Type | What a visitor can use before paying | When the wall appears | Usually fits | What to watch |
|---|---|---|---|---|
| Hard paywall | Nothing, or only a title and a short preview | Immediately | Content or software people already come for by name | A large share of visitors never see the product, so reach is 100% but traffic quality matters most |
| Soft paywall | Part of the content or a limited set of features is free | At a premium item or feature | Products where free use proves value | Free users who never reach the wall; reach is below 100% |
| Metered paywall | A fixed number of free uses, articles or actions in a period | After the allowance is used up | Content or tools with repeat visits | Counting rules (per month, per device) and whether the count resets |
Some sources add a dynamic paywall, where the wall or its offer changes by visitor behavior, and a registration wall, which asks for an account instead of a payment. Both can be measured with the same three counts.
For news, the share of people who pay is modest: the Reuters Institute's Digital News Report 2026 puts it at 17% across a basket of 20 countries and describes 10–20% as a ceiling in most markets, with Norway at 40% and Sweden at 32% as outliers. That figure is for news subscriptions, not for software paywalls, so do not use it as a target for an app.
Paywall vs freemium vs free trial
These three are often confused because a product can use all of them at once.
- Freemium is a business model: a free tier stays free indefinitely and a paid tier adds features or removes limits. The paywall is where the free tier meets the paid one. See the freemium model for how it works as a model.
- Free trial gives full or partial access for a limited time. A paywall appears when the trial ends, or at the start to collect payment details. See free trial conversion rate for how to measure the trial itself.
- Paywall is the screen or gate where payment is requested. It exists in a freemium product (at the upgrade point), in a trial (at its end) and in a purely paid product (at the start).
The practical difference for measurement: a trial start is not a purchase, and a paywall view is not a trial start. Keep each as its own step so the rates are not mixed up.
The three rates and the number that matters
Take the cohort of new users in a fixed window and follow it through the wall:
| Stage | Rate | Question it answers |
|---|---|---|
| Reach | Paywall views ÷ new users | Do people get to the wall at all? |
| Tap | Taps on the purchase button ÷ paywall views | Is the offer interesting enough to consider? |
| Completion | Purchases ÷ taps | Does the purchase go through once someone has decided? |
Multiplying them gives the number that decides: purchases ÷ new users = reach × tap × completion. The usual headline, paywall conversion rate = purchases ÷ paywall views, drops the first factor. That is useful for comparing two designs shown to the same kind of audience, and misleading when the two designs are shown at different points in the journey, as the example next shows. For the general idea of a conversion rate and of ordered steps, see conversion rate and funnel.
Worked example: two walls, two different winners
Sample data: two cohorts of 10,000 new users each, followed for the same 14 days. Cohort A meets a hard paywall at first launch. Cohort B gets three free uses and then a metered paywall; only 40% of the cohort reaches a third use.
| Stage | Hard wall at first launch | Metered wall after 3 free uses |
|---|---|---|
| New users | 10,000 | 10,000 |
| Saw the wall (reach) | 10,000 (100%) | 4,000 (40%) |
| Tapped purchase | 700 (7.0% of views) | 720 (18.0% of views) |
| Paid | 280 (40.0% of taps) | 216 (30.0% of taps) |
| Paid ÷ paywall views | 2.8% | 5.4% |
| Paid ÷ new users | 2.8% | 2.16% |
Check the arithmetic: hard wall 100% × 7.0% × 40.0% = 2.8%; metered wall 40% × 18.0% × 30.0% = 2.16%.
Per paywall view the metered wall looks almost twice as good (5.4% against 2.8%). Per new user the hard wall wins (2.8% against 2.16%), because every new user hits it while only 40% of the other cohort ever reaches its wall. Neither number is wrong; they answer different questions. The first compares how persuasive each screen is. The second compares how much revenue each approach takes from the same incoming traffic.
Two cautions apply. The 6,000 users in cohort B who never saw the wall may still reach it later, so compare after a fixed window, not at the end of week one. And this sample says nothing about which approach is better in general: it shows that the two readings can disagree and that you need both.
The three rates also tell you what to fix:
- If reach is low, the wall sits too deep or the free allowance is too generous. Look at where it is placed.
- If tap is low, the offer is not persuasive. Look at the value message and the price shown.
- If completion is low, something goes wrong after the tap, such as a payment failure, an unclear price or a confusing purchase sheet.
Rules the platforms set
Paywalls on stores and on the web are bounded by platform rules, so check these before designing one:
- Apple. The App Review Guidelines say features or content unlocked inside an app, such as subscriptions, premium content and full-version unlocks, must use in-app purchase (3.1.1). Subscriptions must provide ongoing value, with a period of at least seven days (3.1.2(a)), and before asking someone to subscribe the app must clearly describe what they get for the price (3.1.2(c)).
- Google Search. If you want paywalled web content indexed, Google asks you to mark it with structured data (
isAccessibleForFreeset to false on the paywalled part) so it is not mistaken for cloaking. If content must not reach the browser at all, use a paywall that withholds it on the server.
The rules above concern what a paywall may do. They do not decide how well it converts; the three rates do.
Common mistakes
- Judging by the total paying rate. A single number blends reach, interest and completion, and cannot say which stage to fix.
- Dividing by the wrong group. Paid ÷ paywall views and paid ÷ new users differ by the reach factor; pick one for each question and say which.
- Comparing walls across different audiences. Compare versions within the same channel and platform, not a paid-traffic cohort against an organic one.
- Treating a drop after the tap as a pricing problem. It may be a payment error or a missing payment method.
- Reading an unfinished cohort. Purchases that happen after the window closes are missing, so compare cohorts with the same follow-up time.
- Mixing paywall metrics with subscription metrics. Renewals, churn and monthly recurring revenue come after the first payment and are covered in subscription analytics; this term covers only the step of asking.
How to measure a paywall in TapCub
Take the two walls above and set up the three rates in TapCub.
- Send three events. Send
paywall_viewwith properties such as the placement and the paywall version,purchase_tapwhen the purchase button is tapped, andpurchasefrom your server when payment succeeds, with the order ID, amount and currency.purchaseis the default name in All-platform analytics › Business › Commerce & revenue. TapCub does not build the paywall or take payments. - Build the funnel. In All-platform analytics › Behavior › Behavior analysis, make a funnel of
paywall_view→purchase_tap→purchasewith a window that matches your cohort, and break it down by the paywall version or channel property. Each step shows its count, the rate against the previous step and the drop-off; the largest drop is marked (build a funnel). - Add the reach factor. Read new users for the same dates in App analytics › Users › Users and divide the
paywall_viewcount by it. This is the number the funnel alone does not give you. - Check revenue and refunds. All-platform analytics › Business › Commerce & revenue shows orders, revenue, buyers and paying rate; refunds in the same period are reported separately and are not subtracted.
- Mark every paywall change. Add a dated annotation in Configuration › Annotations so a change in the funnel can be matched to a change in the wall.
TapCub measures the wall; it does not run subscription billing, take payments or split users for A/B tests. Use your store's or payment provider's tools for those, and come back to the funnel to read the result.
Sources
- Apple, App Review Guidelines (3.1.1 In-App Purchase, 3.1.2 Subscriptions). Checked 2026-11-17.
- Google Search Central, Paywalled content structured data. Checked 2026-11-17.
- Reuters Institute, Digital News Report 2026: overview and key findings (share paying for online news). Checked 2026-11-17.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Adoption Consultant
Explores customer onboarding, live conversations, and self-service, turning common usage questions into practical guidance and improvements.