Custom Components for Paywalls and Funnels: Animation and Expandable Content
Built-in blocks cover the essentials, but they can limit visual expression. A self-contained custom component lets you bring your own HTML, CSS, and JavaScript into a paywall or web-to-app funnel for motion, icons, and layered detail — while native purchase controls keep handling checkout.
What a custom component is — and what it is not
Custom components are self-contained pieces of HTML, CSS, and JavaScript that sit inside the paywall or funnel area you assign to them. That separation is the point: you gain freedom over presentation — branded motion, custom visuals, expandable sections — while the platform's native components continue to manage packages, purchase buttons, and checkout.
Use this decision check before building:
- Is the element decorative or supplementary, such as an animated background, icon, illustration, or FAQ accordion? A custom component fits.
- Is it required to complete a purchase, such as a package selector or purchase button? Keep it native.
- Does it need to stay inside its own area rather than control the whole screen? A self-contained component fits.
- Will it be bundled as a ZIP that meets security, file-structure, and size requirements? Confirm before publishing.
Add motion that supports the offer
Movement can reinforce branding and steer attention toward the value proposition without overwhelming the offer. Because the component carries its own code, you can write animation in CSS or JavaScript, or bundle a library such as Lottie or Rive inside the component.
Practical examples:
- A gentle animated backdrop behind the main value proposition.
- Benefit icons that come alive as someone explores the offer.
- A looping illustration that previews the premium experience.
- Consistent branded motion linking the steps of a web-to-app funnel.
Subtlety works best here. A small, well-placed moment of movement can make the whole purchase experience feel polished and connected to the rest of the brand, without competing with the offer itself.
Let people open detail on demand
Showing every answer at once can make a purchase screen hard to scan. Accordions and expandable sections built with HTML and JavaScript solve that by keeping the first view focused and letting people open detail on demand.
Good candidates for expandable content include frequently asked questions, deeper benefit explanations, how a feature works, what an upgrade includes, and supporting detail inside an onboarding step. The result is layered: the primary proposition is understood quickly, and reassurance is available for anyone who wants it.
Build it with an agent or write it yourself
Start in the paywall or funnel editor by adding a custom component and downloading the starter bundle. The bundle includes an index.html entry point, a local preview, packaging tools, a getting-started guide, and instructions a coding agent can follow.
Two build paths:
- Agent-assisted: give the folder to your coding agent of choice, describe the experience you want, and let it build within the stated requirements.
- Direct: edit the HTML, CSS, and JavaScript yourself.
Either way, the workflow is the same: preview the component, package the files, upload the resulting ZIP, then place the component where you want it in the paywall or funnel.
Creativity, with guardrails
Because each component is confined to its assigned slot, it is suited to decoration and support rather than transaction-critical UI. Anything a shopper must use to buy — package choices and purchase buttons on a paywall, or the purchase controls and checkout steps in a funnel — has to stay with the built-in native elements, with the custom piece working alongside them.
Before publishing, check three things: the bundle follows security, file-structure, and size requirements; in-app paywalls use a supported SDK version; and the component still works when placed in its intended slot. From a single animated icon to an expandable section that explains why an upgrade is worthwhile, the creative range is wide — as long as checkout stays native.
Frequently asked questions
Can a custom component replace the purchase button?
No. Packages, purchase buttons, and checkout controls remain native. A custom component is confined to its own area and is meant for decorative or supplementary content, not for elements required to complete a purchase.
How do I build and upload one?
Start from the starter bundle downloaded in the editor. It provides an index.html entry point, local preview, packaging tools, a getting-started guide, and agent instructions. You can hand the folder to a coding agent or edit the HTML, CSS, and JavaScript directly, then preview, package, and upload the resulting ZIP.
Can I use Lottie or Rive animations?
Yes, if you include the library in the component bundle. Animations can also be built directly with CSS or JavaScript.
What must I check before publishing?
Uploaded bundles must meet security, file-structure, and size requirements. For in-app paywalls, the app also needs a supported SDK version. Check the requirements and minimum SDK versions before publishing.