Components are the building blocks you use in Candu to create in-app experiences. Some components serve a specific purpose, such as guiding users, collecting data, or prompting action, and can be styled centrally through your Styleguide for consistency.

By combining components like checklists, forms, flows, cards, buttons, and media, you can design onboarding, education, and engagement experiences without code, while tracking user interactions and personalizing what users see.

Checklists drive product adoption by guiding users through setup and key actions. User checklist items can be completed manually or automatically via product events, user properties, or Candu events. You can create custom styles in your Styleguide and checklists come in two display types:

You can choose between tracking progress per User or Group.

Forms allow you to capture data about your users directly in your product. You can use them to build onboarding or sign up surveys, feedback surveys or contact forms. Styles are set in your Styleguide to ensure consistency. In Candu, forms include:

Multi-step sequences that users navigate through, like a slideshow or carrousel. Use Flows for:

Flow settings:

A container component that can display content and act as an interactive block. This means cards can be used as calls-to-action and set to be Dismissible. Cards are incredibly versatile:

Great for personalization! Show or hide content dynamically based on conditions you set (user properties, location, behavior, etc.).

Learn more about conditional blocks here →

Text components with predefined styles (headings, body text, labels, etc.) Styles are set in your Styleguide to ensure consistency. Once defined, you can use them through your content.

A clickable component that triggers an action and is tracked a user event. Buttons can be styled in your Styleguide and can trigger many actions, such as:

Display images from uploads or URLs and can include GIFs, SVGs, PNGs, and Webpts. You can configure images with:

Image upload limits:

The Player component lets you add embedded video or audio content from supported media providers such as Wistia, YouTube, Vimeo, and Vidyard.
​

Candu does not host or process the video file directly. Instead, the Player component embeds the media provider’s player inside your Candu experience. This means the video provider controls video hosting, streaming, playback behavior, privacy settings, and embed permissions.
​

You can configure players in Candu with:

For the video to load correctly in Candu, the video must be accessible through the provider’s embedded player. It does not always need to be fully public, but the provider’s privacy and embed settings must allow the video to be embedded on the domain where the Candu experience appears.
​

For example, with Vimeo, a fully Private video may not load in an embedded Candu experience because Vimeo says private videos are only viewable by you and your team members, even if embedded elsewhere. Vimeo’s Hide from Vimeo setting is more suitable for this use case because the video is not viewable on Vimeo.com but can still be embedded on other websites. Vimeo also supports domain-level embed privacy, which allows you to specify which domains are allowed to embed the video.
​

Small visual indicators or labels, typically used to show status, counts, or categories. As with buttons, you can create primary, secondary, tertiary, warning, and danger badges. Style them through your Styleguide for consistency.

A simple horizontal line used to separate content sections.

Embeds let you include rich, interactive content, like calendars, forms, videos, or other tools. There are two embed types:

A component for displaying important messages, notifications, or status updates. Alerts are static on the page and you can set styles in your Styleguide for consistency.