October release roundup: web paywalls, paywall video, Unity, and support integrations
This release cycle moves paywalls off the app-store-only path and into the browser, adds creative controls that make a paywall feel more like the product it sells, brings paywalls and Customer Center to Unity, and puts live subscription context inside the two support desks most teams already run. Below is what changed, who each piece is for, and how to decide where to start.
What shipped in this cycle
Six changes are worth tracking. Paywalls now render in the browser as well as in mobile apps. Paywall design gained three tools: video, a “View all plans” sheet, and gradient text. Unity apps can present paywalls and Customer Center. Zendesk and Intercom now surface subscription data in the agent sidebar. A dedicated web hub collects web billing, purchase links, paywall performance, and revenue tracking. Two smaller items round it out: Paddle transaction events flow into AppsFlyer, and Customer Center color changes can be previewed before publishing on iOS.
Paywalls that run in the browser
The core change is that a paywall no longer has to live inside an iOS or Android build. The same paywall design can be placed on landing pages, in ads, in newsletters, or in any link-based flow, delivered through web purchase links or the Web SDK. Because the paywall is served rather than compiled, edits go live without a new app release.
That changes the iteration loop. A team that already sells through web purchase links gets a customizable, testable page in place of a fixed checkout, and targeting and experiments stay in the same place as the mobile work. A useful way to think about it: the link click and the subscription decision now happen in one continuous surface you control.
Video, plan sheets, and gradient text
Three additions target the look and information density of a paywall.
- Video. A product demo, a short walkthrough, or a customer testimonial can sit directly on the paywall, answering “what do I get?” without extra copy.
- “View all plans” sheet. Extra pricing options can be tucked behind a button that opens a sheet, so the main paywall stays focused while power users still reach the full menu.
- Gradient text. Headlines can carry emphasis on key value propositions without a full redesign.
Used together, they let a paywall read as custom-built rather than templated, and none of them require engineering work to apply.
Unity: paywalls and Customer Center in-engine
Unity teams previously had to treat monetization and subscription management as a separate concern from the rest of the app experience. With the current SDK, paywalls and Customer Center work inside Unity builds: native paywalls can be presented, users can manage their subscriptions in-app, and offers and entitlements are controlled from the same dashboard used for other platforms.
If you ship on Unity and already use the dashboard elsewhere, this closes the gap between the two surfaces rather than adding a new one.
Subscription context inside Zendesk and Intercom
Support agents often end up reconstructing a billing picture from several tools before they can answer a question. The Zendesk and Intercom integrations put subscription data into the support sidebar so the agent sees it in the same window as the conversation.
The sidebar covers four things: customer history, revenue contribution, active entitlements, and subscription status. Agents can let the integration match a customer automatically, or search for the customer manually when automatic matching does not apply. Both paths lead to the same view, and neither requires leaving the support tool.
A single home for web monetization
The new web hub gathers the web-side surfaces in one place: web billing, purchase links, paywall performance insights, and real-time revenue tracking. The intent is to remove the page-hopping between setup and optimization. Teams whose web revenue is growing as a share of the mix will likely spend most of their time here; teams still app-only can treat it as the place to start when they add a web funnel.
Two smaller upgrades that still matter
Paddle transaction events can now be tracked in AppsFlyer, which keeps attribution consistent across web and mobile purchases. Separately, Customer Center color changes can be previewed before publishing on iOS, so design adjustments can be judged on screen instead of guessed at.
Where to follow future releases
A changelog collects new features, improvements, and fixes in one running list, which makes it easier to keep a team aligned on what has actually shipped. It is the natural starting point for anyone who wants to track releases week to week.
Which change applies to you?
Use this checklist to pick a starting point rather than trying everything at once.
- You already sell through web purchase links. Start with web paywalls. The upgrade is immediate and opens up testing and iteration on the page itself.
- Your paywall converts but feels generic. Try video first, then a “View all plans” sheet if pricing tiers are the sticking point, and gradient text if the headline needs emphasis.
- You ship on Unity. Move paywalls and Customer Center into the build so subscription management matches the rest of the app.
- Your support queue includes billing questions. Enable the Zendesk or Intercom integration so agents see customer history, revenue contribution, active entitlements, and subscription status without switching tools.
- Attribution is split between web and mobile. Confirm Paddle transaction events are flowing into AppsFlyer.
- You are tuning Customer Center visuals on iOS. Preview colors before publishing.
A worked example: a team running a newsletter campaign sends readers to a web purchase link. Before web paywalls, that destination was a fixed checkout. After, the same link opens a paywall the team can edit, test, and target without shipping code, and the results sit alongside the mobile paywall data in the same dashboard.
Frequently asked questions
Does a web paywall replace the mobile paywall?
No. Paywalls now work in the browser in addition to iOS, Android, and other mobile apps. The same design can be used in both places, and targeting and experiments stay centralized.
How does a web paywall get onto a page?
Through web purchase links or the Web SDK. It can be placed in landing pages, ads, newsletters, or any link-based flow, and updates go live without a new app release.
What happens if the support integration cannot match a customer automatically?
The agent can search for the customer manually. Either path produces the same sidebar view: customer history, revenue contribution, active entitlements, and subscription status.
What exactly works in Unity now?
With the current SDK, paywalls and Customer Center work in Unity apps. Native paywalls can be presented, users can manage subscriptions in-app, and offers and entitlements are controlled from the same dashboard used on other platforms.
Where should a team start if it is already using web purchase links?
With web paywalls. The upgrade is immediate and adds customization, testing, and iteration to the existing web purchase flow.