Founder Playbook · Sub Club by RevenueCat
11 tactics from Thomas Petit
Understanding When to Use Web2App and How to Do It Well — Thomas Petit, Independent App Consultant
Watch the full episode“Everyone comes to web2app thinking they'll save 30% on fees or get better attribution. Those are rarely the reasons it actually works. The real value — different audiences, owned data, new retention levers — only becomes visible after you've run it for six months.”
Developers go web2app for the wrong reasons — and discover the real value on the way
Petit has observed a consistent pattern: apps adopt web2app expecting fee savings or attribution improvements, only to find those benefits are modest or offset by lower web conversion rates. The durable advantages — reaching audiences unreachable via App Store ads, owning the payment relationship, unlocking win-back flows — only become legible through experience. The implication: commit to web2app as a long-term channel, not a quick financial optimisation.
“When you run web campaigns and app install campaigns on Meta at the same time, you're not reaching the same pool of users twice. Meta's algorithm finds different user profiles for web objectives versus app install objectives. It's genuinely additive inventory.”
Running web and app install campaigns on Meta simultaneously reaches different people, not just more of the same
Petit's most counter-intuitive finding: web and app campaigns on Meta do not cannibalise each other. Meta optimises each campaign type differently — web conversion campaigns find users who respond to landing page CTAs, while app install campaigns find users comfortable tapping directly to the store. Running both simultaneously expands total reachable audience rather than just splitting budget against the same people. This is why ROAS on web often holds even after scaling app campaigns.
“Ladder's web2app isn't primarily about fees. It's about getting purchase signal back to TikTok and Instagram fast enough to train the algorithm. On iOS you're waiting 3, 7, 14 days for SKAdNetwork windows. On web you get the signal in hours. That changes what the algorithm can do for you.”
Early signal feedback to TikTok/Instagram — not fee saving — is what makes Ladder's web2app work
Petit cites Ladder (the strength training app) as the clearest example of web2app as a paid acquisition infrastructure play. iOS attribution delays prevent the ad algorithms from learning which creatives and audiences convert to buyers — web payments collapse that window from days to hours. Faster signal enables the algorithm to optimise spend more accurately, improving ROAS independent of any fee savings.
“When you own the billing relationship, you can do things Apple will never let you do. One of the most powerful is a partial refund offer at cancellation — 'keep your subscription, get 3 months free.' That's a retention lever that doesn't exist if Apple owns the transaction.”
Owning the transaction enables a partial-refund counter-offer at cancellation — impossible inside the App Store
Petit identifies payment ownership as the underrated web2app benefit. Apple's terms prohibit offering promotional pricing as a cancellation counter-offer inside the native flow. Web billing removes that constraint entirely: when a subscriber initiates cancellation, the developer can offer a partial refund, a pause, a discount, or a downgrade — anything that might retain them. The value compounds over a large subscriber base.
“The biggest mistake in web2app is treating it as a binary. Web2app versus app install is not the question. The question is: where is this user coming from and what context are they in? Match the journey to that context. Sometimes that means web. Sometimes that means the App Store.”
Context of the ad placement matters more than web vs app choice — match the journey to traffic source
Petit's framework is traffic-source-first: Facebook and Google search users may convert fine through direct app install because they're in high-intent, familiar territory. TikTok users, Outbrain users, or cold display traffic are in lower-intent, lower-trust contexts where a landing page warms them before asking for an app install. The web landing page's job is context bridging, not fee avoidance.
“Try sending Taboola traffic straight to the App Store — you'll see a 90% drop-off before anyone taps install. These channels require a landing page. Not because web2app is better, but because the user expects to land on a page, not get redirected to a store.”
Taboola, Outbrain, and Reddit can't work sending users straight to the App Store — web landing page is mandatory
Petit tested traffic from native advertising networks (Taboola, Outbrain) and Reddit ads going directly to App Store product pages — conversion collapsed. Users from these placements have content-browsing intent, not shopping intent; the App Store redirect breaks their expectations. A matching landing page serves as the expectation bridge, and only once intent is established does the app install conversion hold.
“The 30% fee saving sounds compelling. But if your web conversion rate is 40% lower than your App Store conversion rate, you've given back the saving and more. Fee avoidance as a primary motivation is usually a mistake.”
Avoiding App Store fees is not a good reason for web2app — lower conversion often offsets the saving
Petit runs the math that most teams don't: web funnels introduce additional drop-off points (landing page to email capture to onboarding to paywall) that native app funnels don't have. For apps with strong App Store listing conversion and a motivated search-intent audience, the fee saving rarely compensates for web conversion loss. Web2app makes economic sense when the incremental revenue from new audiences or retention levers exceeds the conversion penalty.
“If your product is complex, emotionally sensitive, or expensive, you need a warming journey before the App Store. A $99/year couples therapy app cannot close in the 30 seconds a product page gives you. You need a web flow that builds trust, addresses objections, and gets commitment before the install.”
High-friction products — finance, couple therapy, premium-priced apps — need web warming before the App Store
Petit segments web2app candidates by product friction: low-friction utility apps (weather, unit converter, simple tracker) can go straight to the App Store from any traffic source. High-friction products — anything requiring trust, emotional investment, or significant financial commitment — need a longer selling journey than an App Store page allows. The web landing experience becomes the sales conversation the product page cannot have.
“If your users need to expense the subscription, or their company needs an invoice, or they want to pay annually via bank transfer — none of that works through the App Store. That's a B2B billing reality that makes web2app mandatory regardless of what you think about fees.”
B2B billing needs are a compelling web2app reason that has nothing to do with fees
Petit highlights enterprise and prosumer use cases where App Store billing is functionally broken: corporate purchasers need VAT invoices, IT procurement needs bank transfer options, expensing requires receipts with business details. None of this is available through Apple or Google billing. For apps with any B2B or prosumer segment, web billing isn't a strategic option — it's a prerequisite for serving that audience at all.
“People say 'web attribution is broken.' It's better than iOS. Yes it's imperfect — but you can see in hours what took weeks on iOS. For creative testing, for audience testing, for algorithm optimisation — the speed of web feedback has no equivalent on the App Store side.”
Web attribution isn't perfect either — but it enables faster feedback loops than iOS ever could
Petit rebuts the attribution-quality objection to web2app: iOS post-ATT attribution is not a high bar. Web attribution (server-side events, first-party cookies, probabilistic matching) is imperfect but delivers purchase signals in hours versus the 14-day SKAdNetwork windows on iOS. For teams running continuous creative and audience experiments, this speed difference is compounding — more learning cycles per unit time means faster improvement.
“The question is never 'should I do web2app or app install.' It's always both. Your audience is not a monolith. Some users will convert better through the App Store. Some through web. The job is to have both paths and let each user take the one that fits.”
Web2app is never 100% one or the other — always both, because audiences behave differently at different moments
Petit's closing framework: web2app is an additive channel, not a replacement. The same user who ignores a Facebook app install ad might convert on a web landing page after seeing a TikTok; or they might install directly from an App Store search a week later. Constraining to one path means abandoning the other path's addressable audience. Portfolio thinking — maintaining both channels and optimising each — consistently outperforms either/or strategies.