Web SDK

Most subscription apps run two monetization stacks without meaning to. The mobile app has remote paywalls, audiences, and experiments. The web app has a pricing page an engineer built once and nobody dares to touch. Every price test happens on mobile, every web change waits for a deploy, and the two never quite match. The Web SDK ends that split. Your web app shows the same paywalls, follows the same audience rules, and joins the same experiments as your iOS and Android apps.

One paywall, every platform

A paywall you build in the editor for mobile can show up in the browser without being rebuilt. Change the headline, the price, or the offer once and it updates on web and in the app together. Nothing to deploy, no ticket for the web team.

• One experiment, one result. Run the same pricing test on web and mobile and read a single answer in the dashboard, instead of two tests that disagree.

• The same audiences. A rule like "came from the annual deal campaign" or "trial expired last week" works on web the way it already works in the app, so each visitor sees the paywall built for them.

• Checkout is built in. Web purchases run through Stripe out of the box. Teams with their own billing can plug it in instead.

Web subscribers are app subscribers

Someone who subscribes on the web is a subscriber in the app, and the other way round. Access is decided by the same entitlements on both, so a customer never has to buy twice or email support to unlock what they paid for. A purchase made on your site can be redeemed in the app, and the Web Paywalls page covers that handoff.

Built to be trusted

Anything shown in a browser can be tampered with, so the SDK is designed for your engineers to check access on the server before handing over paid content. That check is part of the SDK, not something the team has to invent. The result is a web paywall a growth team can edit freely and a paid feature that stays paid.

See the Web SDK overview

What you can do with it

• Replace a hard-coded pricing page with a paywall you can change on a Tuesday afternoon.
• Test annual against monthly framing on web and mobile in the same week.
• Show a visitor from a paid campaign the offer their ad promised.
• Win back a lapsed mobile subscriber with a web offer that unlocks the app.

Get started

Your engineering team installs the SDK once, following the quickstart, and registers the places a paywall should appear. From then on, paywalls, pricing, and experiments on the web are managed from the same dashboard as the app.

Send the quickstart to your engineers