Tips
Practical advice for building effective flows.
After purchase behavior
By default, when a user makes a purchase, the paywall or flow will close. But in Flows, you might want to continue. For example, you could show a thank-you message or collect feedback.
To set something like this up:
- Select the purchase action on your button.
- Look for the After Purchase setting.
- Choose None to proceed to the next page, or Close to dismiss the flow.
Use cases for continuing after purchase:
- Showing a personalized welcome or thank-you message.
- Collecting feedback about why they subscribed.
- Presenting an upsell for an add-on product.
- Guiding users through initial setup.
- Using a paywall in the middle of a flow if it's a natural slot to present it.
Start simple, add complexity later
When building a new flow, build linear first so all your pages are created and connected in a straight line, then test the basics to make sure navigation works and content looks right, and finally add branching once the foundation is solid. It's much easier to debug a simple flow than a complex one, so get the basics working before adding sophistication.
Keep flows focused
Flows work best when they have a clear, single purpose:
- Onboarding: Gathering preferences and introducing the app.
- Cancellation: Understanding why users are leaving and offering alternatives.
- Upsell: Guiding users to a higher tier or add-on.
If a flow is getting too long or trying to do too many things, consider splitting it into multiple flows. A focused 5-page flow is better than a sprawling 15-page one.
Use indicators for longer flows
If your flow has more than 3-4 pages, add an Indicator element. Users are more likely to complete a flow when they can see:
- How far they've come.
- How much is left.
Progress visibility reduces abandonment, especially in onboarding flows where users might otherwise wonder "how much longer is this?"
How is this guide?
Edit on GitHub