Segment Definitions & Conditions

A detailed overview of the different operators & logic you can use to create different Segments of users.

Lauren Cumming avatar
Written by Lauren Cumming
Updated over a week ago

You can define your Segment using almost any combination of attributes. Start building conditions by defining an initial property and then define the logical operator.

Definitions and Conditions

Definitions can be combined or nested, allowing for complex logical variations. Once you select the property, the options will appear.

Definitions can be combined or nested, allowing for complex logical variations. Once you select the property, the options will appear.

Default properties

User ID - All or part of a user ID assigned by your application

To tie up user traits & events with a user's Candu interactions, we need their UserIDs. This is passed to Candu either via an integration with a data source that is pushing information into Candu, or the installation script that was initially set up.

  • Is one of - The property is any of the user IDs entered.

  • Equal to - The exact ID entered is the property.

  • Not equal to - The property is anything other than the user ID entered.

  • Contains - The text entered is included in the user ID.

  • Does not have - The property does not have any of the text entered.

  • Ends with - The user ID entered is the final string of the property.

  • Does not end with - The final string of the property excludes the text entered

  • Starts with - The text entered is the initial string of the property.

  • Does not start with - The initial string of the property excludes the text entered.


User Property - Key identifiable information about users.

The list of available properties will depend on what data you send to Candu. If you need specific properties, make sure they are included during installation.

This usually includes data such as name, email, plan type, role type, locale, domain, etc, and helps to build the foundations for your different user groups.

  • Is one of - The property is any of the text entered.

  • Equal to - The exact text entered is the property.

  • Not equal to - The property is anything other than the text entered.

  • Contains - The text entered is included in the property.

  • Does not have - The property does not have any of the text entered.

  • Ends with - The text entered is the final string of the property.

  • Does not end with - The final string of the property excludes the text entered

  • Starts with - The text entered is the initial string of the property.

  • Does not start with - The initial string of the property excludes the text entered.


First & Last Visit

First visit - The first time a user visits your site after Candu has been installed.

Last visit - The most recent time a user visited your site after Candu has been installed.

  • Occurred in the last - Enter the number of days.

  • Not occurred in the last - Enter the number of days.

  • Occurred after - Select a calendar date.

  • Not occurred after - Select a calendar date.

First & Last Visit after Candu has been installed

Content - To schedule a particular piece of content

There may be instances where you want certain content to show at particular times or fo content to automatically update with new content. This is helpful for things like announcement banners that are time sensitive, for example, lettings your customers know about your open hours over a holiday period, or for product release notes that update each month.

This means you can create all of your content in advance and set up different Segments to auto schedule it!

  • Show after - The initial date for the content to be seen.

  • Show until - The final date for the content to be seen.

Content - To schedule a particular piece of content

User Events - All Candu events such as button clicks + any custom events that are being passed into Candu

Candu Events

User Events track all of the Candu events so that you can create user segments based on how users have interacted with your Candu content. Example use case: If a user clicks a "Start Tour" button, then you could say "this person has taken a tour and next time they login we can show them new content."


Event examples include:

  • Button clicks

  • Card clicks

  • Dismissed cards

  • Checklist checks

  • Checklist completions

The events that come through will have the interaction labels that are set in the editor. It's important to set those up, both for analytics tracking and creating user segments.

Conditions can then be combined using AND/OR logic. Selecting AND requires all included conditions to be met. Selecting OR requires any included conditions to be met. For example, to create a Segment for admin users who visit your site frequently, you might define it as:

  • User Property - Is Equal to - Admin

  • AND Last Visit - Occurred in the last - 14 days

Custom Events

You can send key events through to Candu via a third party integration or the initial installation script. This can help to create Segments of users based on key actions they have taken within your product.

Event examples include:

  • Actions in the product for example connected a certain integration, added a new user or completed a key activation task

User Events - All Candu events such as button clicks + any custom events that are being passed into Candu

Did this answer your question?