User actions are all the tracked Candu events that capture what your users do within your Candu content. Understanding user actions involves two key concepts:
Interactions are what you manually configure on interactive components like buttons and cards using the Interactions panel. When you set up an interaction, you define what happens when users click, like opening a URL, triggering a tour, or sending an email.
User actions encompass everything that gets tracked automatically, including:
Your configured interactions (button clicks, card clicks)
Automatically tracked actions (form submissions, checklist completions, modal dismissals, and more)
Both types of user actions are automatically tracked and appear in your analytics, giving you complete visibility into how users engage with your content.
This guide covers how to configure interactions on buttons and cards, what user actions are tracked automatically, and best practices for naming and using all your action data in analytics.
What User Actions Are Tracked?
All user engagement with your Candu content is tracked automatically. All of these user actions appear in your analytics. To see them, go to Analytics > Components or find them under Analytics > Interactions.
Components with configurable Interactions
These components let you set up interactions through the Interactions panel:
Buttons: Configure what happens when clicked (open URL, trigger tour, callback, etc.)
Cards: Configure click actions and track card dismissals
Automatically tracked user actions
These user actions are tracked automatically:
Forms: Form submissions and responses
Checklists: Individual item completions and overall checklist completion
Modals: Modal dismissals (when users click the X)
Hotspots: Tooltip dismissals (when users click the X)
Flows and Tours: Step progression and dismissals
Links: Link clicks within your content
How to Configure Manual Interactions (Lightning Bolt)
Interactions are configured through the Interactions panel in the Candu Editor. Click the lightning bolt icon in the Toolbox to access interaction settings.
This is where you manage what happens when users click or tap on buttons and cards. You can choose from a range of actions, including:
Dismiss overlay: Close a modal
Go to flow step: Navigate within a multi-step flow
Open URL: Send users to a specific page or external site (learn about URL templating for dynamic links)
Callback: Add JavaScript snippets in the installation and call them from the Editor. An example of this is triggering a chat widget to open when a "Start chat" button is clicked. See developer docs.
Trigger tour/hotspot/overlay: Start other Candu experiences
Change content: Update content dynamically
Send email: Open a user's default email client with a new email.
Trigger click: Clicks an element on the page on behalf of the user
When you configure an interaction, two things happen:
The interaction is automatically tracked as a user action in your analytics
The action you configured (opening a URL, triggering a tour, etc.) executes when users click
Naming User Actions
Naming Interactions
When you add buttons or cards to your content, they receive default data labels. To rename these labels, go to Interactions > Interaction label.
The names you give these interactions become the event names in your analytics, so choosing clear, descriptive names is essential for tracking and understanding user behavior.
Naming best practices:
Use consistent naming conventions: Establish a pattern for your user actions, such as:
Action + Object format: "Clicked upgrade CTA"
Location + Action format: "Dashboard - Opened settings"
Feature + Action format: "Collaboration - Invited user"
Make action names analytics-friendly: Choose names that will make sense when you're reviewing data weeks or months later.
Consider your tracking needs: If you're sending user action data to external analytics tools (Heap, Amplitude) or via webhooks, ensure names align with your broader tracking conventions.
Think about filtering: Well-named user actions make it easier to filter and segment your analytics data later.
Naming automatically tracked actions
For components that don't require interaction configuration (forms, checklists, modals, etc.), Candu automatically generates labels based on the component name.
Under content analytics > Components, you can see data for specific action components.
These labels are generated from the component names you set in the editor, so using clear, descriptive names for your components ensures the tracked actions are also labeled in analytics.
To rename a component:
Click on the component in the Candu Editor to select it
Click the pencil icon to see customization options in the right panel, the Toolbox.
User Actions by Component Type
Configured Interactions (Buttons and Cards)
Button labels you can customize:
Button name
Interaction labels (in the Interactions panel)
Card labels you can customize:
Component name
Card label (under Edit > Card Settings)
Dismiss action label
Interaction labels (if you've configured any)
Form Actions
Labels you can customize:
Component name
Form name (under Edit > Form Settings)
Input field labels (single-select cards, checkbox labels, text labels, value labels)
Submit button label
Checklist Actions
Labels you can customize:
Component name
Checklist title (under Edit > Checklist Settings)
Individual checklist item names
Note: In analytics, steps are tracked using the actual step names you've set.
Flow Actions
Labels you can customize:
Component name
Individual flow step names
Product Tour Actions
Labels you can customize:
Tour name
Individual tour step names
Dismiss action labels
Modal Actions
Labels you can customize:
Modal name
Dismiss action label
Hotspot Actions
Labels you can customize:
Hotspot name
Hotspot group names
Dismiss action labels
Building Segments Based on User Actions
You can create user segments based on user actions (found under User Events) in to:
Display, or "daisy chain", follow-up content after specific actions
Hide content once users complete key actions
Example: When users complete a checklist, use the checklist completed action to create a segment of users who've finished onboarding, then show them advanced features or remove the completed checklist.
Conditional Logic Based on User Actions
Use user action data to:
Display content only to users who've performed specific actions
Hide CTAs after users click them
Create personalized experiences based on action patterns
Important: User behavior outside of Candu components is not captured. For example, if a user clicks a Candu button that opens a page in your product, Candu tracks the button click but not what the user does on that page, unless you send those actions to Candu as custom events.