Candu's form component lets you collect information directly from users inside your product. You can build complete multi-question forms, or use individual form inputs like a single text box or checkbox wherever you need to gather user input. This gives you tremendous flexibility since you're not limited to traditional "full form" layouts.
Unlike external form tools, Candu forms look like they're part of your product. Responses are captured in Candu where you can analyze them directly, and you can send data to other tools if needed.
Common use cases:
Onboarding surveys to learn about new users
Feature feedback requests (even just a single text area for comments)
User research sign-ups
Lead capture or contact forms
Product satisfaction surveys
Quick polls or single-question prompts
The data you collect automatically becomes available in Segments (unless you turn this off), so you can personalize other Candu content based on what users tell you.
How Forms Work
Forms have three parts that work together:
Form container: The wrapper that holds everything and controls what happens when users submit
Form fields: Individual fields like text boxes, dropdowns, checkboxes where users enter information
Submit action: Forms won't work without a "submit form" interaction. Users can fill out all the fields, but their responses won't be captured unless you add a "submit form" action to your form container.
Building a Form
Start by adding a form container:
Go to Components > Forms
Drag "Form container" onto your canvas
Drag any available form inputs onto your form container
Drag a button into your form container
In the Toolbox > Interactions, add "Submit Form" action
Important: If you configure multiple interactions on the button (like Submit Form + Redirect), the Submit Form action must be listed FIRST
Form Input Types
Input Type | When to Use It | Best For |
Text Input | Short answers like names, job titles, company names | General information gathering |
Text Area | Longer responses like comments, feedback, or detailed explanations | Qualitative feedback |
Email Input | Collecting email addresses with validation | Contact information, domain-based segmentation |
Select Input | Single choice from a predefined list (dropdown) | Job roles, industries, company size. Great for segmentation! |
Checkboxes | Multiple selections from a list | "Select all that apply" questions. Good for segmentation! |
Single Select Cards | Single choice presented as visual cards instead of dropdown | More engaging alternative to Select Input |
Multi-Select Cards | Multiple selections presented as visual cards | More engaging alternative to Checkboxes |
Configuring Form Inputs
Select any form input to configure it in the Toolbox. All inputs have these general settings:
Label and placeholder
Label: The field name that appears above the input
Placeholder: Gray text inside the field showing an example
Show/hide the label (the label name still matters for reporting even if hidden)
Mark as required (users can't submit without completing required fields)
Important: Always rename your labels to be descriptive. When viewing form responses or analytics, you'll only see the label names.
Input-specific settings
Email Input:
Toggle email validation on/off (Recommended: keep it on to ensure valid email addresses)
Select Input, Checkboxes:
Add options with "Text" (what users see) and "Value" (what gets stored)
For checkboxes, set number of columns for layout
Single/Multi-Select Cards:
Set number of cards and columns
Add images to cards for visual appeal
Form Container Settings
Click on the form container itself (not individual inputs) to access these settings in the Toolbox:
Form name: Give your form a descriptive name for tracking in Form Responses
Redirect on submission: Enter a URL to send users to a specific page after they submit (optional)
Prevent resubmission based on User ID: Toggle this on to ensure each user (based on User ID) can only submit the form once. After submission, the form won't appear for them again.
Form states: Forms have three states you can customize:
Normal: How the form looks before submission
Submitted: What users see after successfully submitting (customize this message in the styleguide to confirm their response was received)
Error: What users see if submission fails (rare, but you can customize the error message in the styleguide)
You can edit the text and styling for each state. Most users only customize the Submitted state to show a "Thank you" message.
Where Form Data Goes
When users submit a form, two things happen automatically:
Responses are stored in Candu: You can view them in the Form Responses section (more on this below)
Data syncs to Segments as User Properties: Each form input becomes available for creating segments
Example workflow:
You create an onboarding survey asking "What's your job role?" using a Select Input
User selects "Product Manager"
That response appears in Form Responses
A new User Property is automatically created: "What's your job role? - Select Input" with value "Product Manager"
You can now create a Segment targeting all Product Managers and show them role-specific content
How to find synced data
Go to Form Responses > select your form > Integrations
You'll see which form inputs are syncing to as User Properties
In Segments > User Properties, look for properties named:
[Your Label] - [Input Type]
To turn off syncing: If you don't want form data in Segments, go to Form Responses > select your form > Integrations > toggle off the sync. This is enabled by default.
Sending data to other tools: You can export form responses as webhooks or use integrations to push data to your other tools automatically.
Viewing Form Responses
After publishing your form, responses appear in the Form Responses section. You can view responses in two ways:
List view (☰): Shows all form submissions in chronological order with submission dates. Click into any response to see that user's complete answers.
Form view (▭): Shows all responses organized by form field. Expand the drawer for each field to see what everyone answered for that specific question. Useful for analyzing patterns in specific questions.
Remember: The label names you set on each input become the column headers in your responses and exports. This is why descriptive labels matter.
Note: Click "Download all responses" to download responses as CSV for analysis.
Styling Forms
Forms follow styles set in your Styleguide under the Forms section. You can customize:
For all form elements:
Font type, weight, size, and color
Spacing (margin and padding)
For each field type:
Border, radius, background
Colors for different states (hover, focus, selected)
For field errors:
Font and color for validation messages
Creating multiple form styles: If you need different visual styles for different forms, you can clone form styles in the Styleguide. This lets you have, for example, a minimal style for quick surveys and a more detailed style for onboarding forms.