Flow Elements

Flows can be enhanced with interactive components designed for multi-page experiences. They capture user input, show progress, or request permissions. Use them to personalize the flow or gather information for branching.

Multiple Choice

The multiple choice element presents options for users to select. This is the key element for enabling branching. User selections can determine which page they see next.

// TODO: IMAGE

Configuration

• Single-select or multi-select: Choose whether users can pick one option or multiple.
• Randomize order: Shuffle the options each time (useful for surveys to reduce bias).
• Choice items: Each choice has a label and a value.

Labels and values

Each choice has two parts:

• Label: What users see (e.g., "Grow subscriptions").
• Value: What gets stored (e.g., goal_grow).

The value is used internally for routing conditions and user attributes. Keep values short and consistent (lowercase, underscores).

// TODO: IMAGE

Storing selections

When a user makes a selection, you can store it as a user attribute or trigger an event. This lets you use the selection in routing conditions to branch the flow, access the data later for analytics or personalization, or pass the value to your backend via webhooks.

Input

The input element lets users type a response, like their name, email, or feedback.

// TODO: IMAGE

Configuration

• Placeholder text: The hint shown before users type.
• Keyboard type: Choose the appropriate keyboard (default, email, number, etc.).

Storing responses

Like multiple choice, text entry values can be stored as user attributes. This is useful for personalizing later pages with the user's name, capturing email addresses for follow-up, or collecting feedback or custom responses.

Indicator

The indicator element shows progress through the flow, like "Step 2 of 5."

// TODO: IMAGE

Configuration

• Style: Choose from different visual styles (dots, bars, numbers).
• Current step: Which step to highlight.
• Total steps: How many steps to show.

Add an indicator when your flow has more than 3-4 pages. Users are more likely to complete a flow when they can see their progress and know how much is left. You can also use their properties in dynamic values such as progression:

Permissions Prompts

The permissions prompt element requests system permissions like notifications or app tracking.

// TODO: IMAGE

Prompt types

You can choose from the available these permission prompts:

• Notification: Ask for permission to send system notifications.
• Background Location: Request location access when the app isn’t in use.
• Location: Request location access while the app is in use.
• Read Images: Access the user’s photo library/camera roll.
• Contacts: Access the user’s contacts.
• Camera: Access the device camera.
• App Tracking Transparency: Ask to track the user across apps and websites.
• Microphone: Access the device microphone.

These are common iOS permission prompts to include during onboarding when you need access to device capabilities.

Configuration

• Permission type: Notifications, app tracking, location, etc.
• Messaging: Customize the prompt text to explain why you need the permission.

Prompt best practices

• Request permissions after providing value. Users are more likely to accept.
• Explain the benefit clearly (e.g., "Get notified about exclusive deals").
• Consider placing permission prompts after a purchase or key engagement moment.

For more guidance on iOS, view Apple's Human Interface Guidelines here.