Appfunnel: What It Is and How to Build One
An appfunnel is the sequence of steps that takes a person from an ad or link to a paying subscriber of a mobile app. For subscription apps it usually runs: ad, landing page or quiz, personalized plan, paywall, payment, then app download and login. Each step has a conversion rate, and the product of those rates sets your cost per paying user.
The term is used two ways. Some teams mean the in-app funnel: install, onboarding, paywall inside the app. Others mean a funnel that runs on the web before the install, where the user answers questions and pays in a browser, then installs the app and logs in. This article covers both, but focuses on the web version, usually called a web2app funnel, because that is where most subscription apps in health, fitness, language learning, AI, and education are moving.
The stages of an appfunnel
Whatever the tooling, a subscription appfunnel has the same building blocks.
- Traffic source. Paid social (Meta, TikTok, Snapchat), search, creators, or email. The ad promises one specific outcome, such as a workout plan or a language level.
- Entry page or quiz. A short landing page or the first quiz question. Quizzes work well here because answering a question is a lower-friction first step than reading a pitch.
- Quiz or onboarding flow. Five to twenty screens that collect goals, level, and constraints. The answers are used later to personalize the offer.
- Personalized result. A plan, score, or summary built from the answers. This is the bridge between "I answered questions" and "I should pay".
- Paywall. Pricing, trial or no trial, plan comparison, and payment form.
- Payment. Card, wallet, or PayPal, processed by a payment provider.
- App handoff. The user installs the app and logs in, and the subscription is already attached to their account.
Drop-off at any of these stages is normal. The job of the funnel owner is to find the stage where the largest share of people leave and test changes there first.
Why subscription apps move the funnel to the web
There are three practical reasons.
Commission. Apple charges up to 30% on in-app purchases, or 15% under its Small Business Program. When a subscription is sold on the web, where the rules of the platform and the region allow it, the store commission does not apply to that purchase. You pay your payment provider instead. For an app with meaningful monthly revenue, that difference is large enough to change which ad channels are profitable.
Testing speed. Changing an in-app paywall usually means a code change, a build, and a store review. Changing a web page takes minutes. That makes it realistic to run many tests on question order, price points, and copy.
Data before the install. On the web you see every step, with the ad source attached. You can send server-side events to Meta or TikTok so the ad platforms optimize for purchases rather than installs. You also keep the user's email from the first screens, which supports follow-up sequences for people who did not pay.
There are trade-offs. The user must install the app and log in after paying, which adds a step, and rules about external payments differ by country and store policy. Check the current rules for each market you sell in before you scale spend.
Appfunnel options compared
Most teams choose between three approaches. Here is how they differ on the factors that matter day to day.
Store commission on subscriptions
- In-app onboarding with store billing: Apple takes up to 30% (15% under the Small Business Program).
- Custom-built web funnel: no store commission on web purchases; you pay your payment provider.
- No-code funnel builder: no store commission on web purchases; you pay the provider plus the builder's fee.
Speed of changing a screen
- In-app onboarding with store billing: needs a build and store review.
- Custom-built web funnel: depends on the developer queue.
- No-code funnel builder: marketer edits and publishes directly.
Engineering effort
- In-app onboarding with store billing: mobile developers for every change.
- Custom-built web funnel: web developers to build and maintain pages, payments, tracking, and A/B logic.
- No-code funnel builder: little to none for standard flows; some setup for the app login handoff.
A/B testing
- In-app onboarding with store billing: possible with a paywall or experimentation SDK, but each variant ships in the app or remote config.
- Custom-built web funnel: you build the split logic and reporting yourself.
- No-code funnel builder: usually built in, depending on plan.
Attribution and ad events
- In-app onboarding with store billing: mobile attribution tools, subject to platform privacy limits.
- Custom-built web funnel: you wire up UTMs, pixels, and server events.
- No-code funnel builder: UTM capture and pixel integrations are included.
A custom build makes sense if you have spare engineers and unusual requirements. For most growth teams, a builder gets a first funnel live sooner, and you can move to custom later if you outgrow it. For a broader look at the market, see this comparison of web2app funnel builders.
How to build an appfunnel step by step
- Pick one audience and one promise. A funnel for "lose weight after 40" will convert differently than one for "general fitness". Start narrow.
- Write the questions. Ask what you need to personalize the result: goal, current level, time available, one or two obstacles. Fewer questions with a clear purpose beat long surveys. A quiz builder lets you lay these out without code.
- Design the result screen. Reflect the user's answers back in plain words, then present the plan the app delivers.
- Set up the paywall. Decide on plans, trial length, and price display. Keep the paywall consistent with what the app shows after login so there are no surprises.
- Connect payments. Stripe is the common starting point. Add PayPal or other providers if your audience uses them.
- Connect the app. The paid user needs to unlock access after logging in. Most teams do this through a subscription platform such as RevenueCat, Adapty, Qonversion, Superwall, or Apphud, or through webhooks and an API.
- Add tracking. Capture UTM parameters, install the ad pixels, and send server events for purchases.
- Test the whole path. Pay with a real card, install the app on a clean device, log in, and confirm access. Do this on both iOS and Android before spending on ads.
What to measure in an appfunnel
Track conversion at every step, not only the final purchase. A useful minimum set:
- Quiz start rate: visitors who answer the first question.
- Quiz completion rate: starters who reach the result.
- Paywall view to purchase: the share of people who see prices and pay.
- Purchase to app login: paid users who actually install and sign in. A gap here means the handoff is broken or unclear.
- Cost per paying user by campaign and creative.
- Retention and refunds: how many subscribers stay active and how much revenue is refunded.
For reference, MyMental AI GURU generated over $100K in revenue with web2wave, with about 55% of subscribers still active, refunds under 5% of revenue, and paying users from 40+ countries. Those figures come from one app in one category, so treat them as an example of what to track, not a benchmark for your own funnel.
Localization is another lever once the base funnel works. Leya AI scaled its funnel roughly tenfold with localized flows, according to its case study.
Appfunnel tools and what they cost
Funnel builders price in different ways: a flat fee, a share of revenue, or a mix. It matters because a revenue share grows with your success, while a flat fee does not.
web2wave is a no-code builder for web2app funnels: quiz and onboarding flows, web paywalls, A/B experiments, UTM attribution, a user CRM, email sequences, and AI localization into 40+ languages. It is an official Meta Business Partner for web2app funnels. Its plans are:
- Basic, $199/month: up to 1,000 quiz starts.
- Starter, $590/month: up to $10k revenue per month.
- Pro, $990/month: up to $40k revenue per month, with A/B testing, a custom domain, PayPal, Paddle and Unlimit, and an assigned Growth Manager.
- Advanced, 2% of revenue with a $1,390/month minimum: ROAS and LTV analytics, AI localization, email sequences, and payment orchestration with Primer, Solidgate, Braintree, and Adyen.
So Basic, Starter, and Pro are flat monthly fees, and only Advanced uses a revenue share. Add-ons include Trends and AI Creatives at $199/month, a Growth Manager at $70/hour, and implementation help at $30/hour. Stripe is available on every plan. Check the billing page for current terms before you decide.
When you compare tools, ask about the payment providers supported, whether A/B testing is included on your plan, which subscription platforms and ad pixels connect natively, and how the handoff to the app works. You can see the supported connections in the integrations overview if you want to check them against your stack.
FAQ
What is an appfunnel?
It is the path from first ad click to paying subscriber for a mobile app. It covers the landing page or quiz, the personalized result, the paywall, the payment, and the app install and login.
Is an appfunnel the same as in-app onboarding?
No. In-app onboarding happens after install and usually ends in a store-billed paywall. A web appfunnel happens before install, in a browser, and the payment is taken on the web. Some teams run both: a web funnel for paid traffic and in-app onboarding for organic installs.
Do I need developers to build one?
Not for the pages themselves if you use a no-code builder. You may still need a developer for the app side, such as making sure a user who paid on the web is recognized when they log in. Subscription platforms and webhooks cover most of this.
Does a web appfunnel avoid Apple's commission?
Apple charges up to 30% on in-app purchases, or 15% under its Small Business Program. A subscription sold on the web, where allowed, is processed by your payment provider instead. Rules vary by country and change over time, so confirm the current policy for your markets.
How many questions should the quiz have?
There is no fixed number. Ask only what you use to personalize the result, then test shorter and longer versions with an A/B experiment and compare completion and purchase rates.
If you want to see how an appfunnel would look for your app, book a demo with the web2wave team, or start free and build your first funnel yourself.
.webp)
