User Events are one of the core conditions you can use when creating Segments in Candu. They represent any tracked action a user performs, whether it comes from Candu-built content (buttons, cards, checklists) or Custom Events coming from your product.
In other words, User Events include:
Candu Events generated through in-app interactions with Candu content.
Custom Events that you send through your installation script or a third-party integration.
Candu Events
Every Candu interaction carries an event label. These labels come from the editor and appear in Analytics and in the Segmentation builder. Clear naming is essential so you can understand what each interaction represents and use it reliably in conditions.
Examples of Candu Events:
Button clicks
Card clicks
Card dismissals
Checklist item checks
Checklist completions
Custom Events
Custom Events extend tracking beyond Candu UI elements. They capture key actions inside your own product and are passed into Candu through your installation script or an integration like Segment.com.
Example use cases:
A user connects an integration
A team member is added
A key activation milestone is completed
A workflow is finished during onboarding
Once Custom Events reach Candu, you can use them exactly like any other event to build tailored experiences.
Using User Events in Segmentation
User Events allow you to create targeted segments based on what users have done in your product through custom events or Candu events. For example:
If someone clicks a “Start Tour” button, you can add them in a segment for users who have already taken that tour.
On their next login, you can show them different content like a checklist, advanced tips, or feature highlights.
Defining event labels and choosing which Custom Events to send is a small upfront investment that pays off in flexibility, personalization, and clarity.