Skip to content
AppDues
Log in
Contact salesSign up

Paywall AI Editor v3 and Seven More Paywall Updates

The paywall builder now ships with a third-generation AI editor, custom components that read live paywall data, per-locale images, foldable device previews, and new measurement hooks. This guide explains what each update does, where to find it, and how to sequence adoption without reworking a paywall that already converts.

Paywall AI Editor v3

The AI editor is now available to every user. Three changes matter most. First, starter screens and onboarding shorten the path from a blank project to a working design. Second, image generation produces visuals that fit the layout, including transparent-background images that can be refined during the session. Third, you can ask the editor to create a custom variable inside the conversation; your app still supplies the runtime value, such as customer-specific information.

Multi-step awareness is the structural change. When you edit one screen of a multi-step paywall, the editor can see the remaining screens, so suggestions keep layouts and messaging consistent across the flow instead of treating each step in isolation.

Custom components that react to paywall data

Custom components let you write your own HTML, CSS, and JavaScript for comparison tables, animations, and visuals that match your app. The update is about data access and reactivity: a component can read the paywall's Offering, Packages, custom variables, and device context, and it can change its content or appearance when a customer selects a different Package.

A useful example is a comparison table generated from the Packages actually available in the Offering, paired with an animation that highlights the selected plan. Because the component reads the live Package selection, the highlight follows the customer's choice rather than a hard-coded default.

Localized images, including light and dark variants

Translation alone leaves a gap when the screenshot beside a translated headline is still in the original language. You can now assign a different image to each locale within a single paywall, including light and dark variants, instead of maintaining a separate design per language.

There are three ways to attach a locale-specific image: from the Paywall Editor, from the 'Paywall Localization' page, or by asking the Paywall AI Editor to do it for you.

Folded and unfolded previews for foldable devices

A design that holds up while the device is closed can break apart when the panel expands. To check both states, the editor offers folded and unfolded previews for the upcoming iPhone Duo, along with previews for the Galaxy Z Fold7, letting you spot layout problems during editing rather than after release.

Paywall interaction callbacks across native and hybrid SDKs

A purchase result confirms conversion, but not the steps that led there. Paywall interaction callbacks now ship across native and hybrid SDKs, letting your app capture interaction events and pass them along to whatever analytics stack you already use. React Native and Flutter also gain real-time listeners for the presentPaywall and presentPaywallIfNeeded APIs.

With those events in hand, you can examine paywall engagement next to the rest of the customer journey and choose your next experiment with better evidence.

Custom-paywall views in Conversion, LTV, and Abandonment charts

If you build your own purchase screens, the Paywall Conversion, LTV, and Abandonment charts now include inferred views of your custom paywalls. That adds context on conversion, customer value, and abandonment without leaving the dashboard.

One distinction matters when reading these numbers: inferred views are inferred, not directly recorded impressions. Treat them as directional context rather than a substitute for impression logging.

Duplication and batch deletion

Two modest changes trim the manual work between one paywall version and the next. Duplication now covers published paywalls, so when you want to try a fresh headline, layout, or offer, you can branch from a design with a proven track record. And in the paywall media gallery, selecting several assets lets you delete them together, which makes tidying up after a design exploration round much quicker.

Which update should you adopt first?

Use this checklist to sequence adoption against the state of your current paywall:

  • If you are starting from scratch or rebuilding a flow: begin with Paywall AI Editor v3 and its starter screens, then use multi-step awareness to keep the flow consistent.
  • If your paywall already converts but feels generic: add localized images per locale, including light and dark variants, before changing layout.
  • If you support or plan to support foldable devices: run folded and unfolded previews for the iPhone Duo and Galaxy Z Fold7 to catch layout issues.
  • If you need richer visuals or plan comparison: build a custom component that reads Offering, Packages, custom variables, and device context, and reacts to Package selection.
  • If you cannot explain drop-off: wire interaction callbacks into your analytics, and read custom-paywall views in the Conversion, LTV, and Abandonment charts as inferred context.
  • If version management is slow: duplicate a published paywall as the starting point for the next test, and batch-delete unused media.

Getting started

Open your project's 'Paywalls' page to try the new tools. A reasonable first step is to duplicate a paywall you already have, pick one improvement (a localized screenshot or a custom component built on your Packages), and test that version. For the SDK features, update your SDK and follow the platform-specific instructions in the paywall integration documentation.

Frequently asked questions

Is the Paywall AI Editor available to all users?

Yes. The third version of the Paywall AI Editor is available to everyone, with new starter screens and onboarding.

Can custom components react when a customer picks a different plan?

Yes. Custom components can read the paywall's Offering, Packages, custom variables, and device context, and they can change content or appearance when a customer selects a different Package.

Where can I set localized images?

In the Paywall Editor, on the 'Paywall Localization' page, or by asking the Paywall AI Editor.

Are custom-paywall views in charts the same as recorded impressions?

No. The views shown for custom paywalls in the Conversion, LTV, and Abandonment charts are inferred, not directly recorded impressions.

Which SDKs support paywall interaction callbacks?

Interaction callbacks are available across native and hybrid SDKs. Real-time listeners are available in React Native and Flutter for the presentPaywall and presentPaywallIfNeeded APIs.