How to segment users and accounts throughout

Updated over a week ago


With a high volume of signups or churns, it can be challenging to know who to focus on. With Segments, you can create groups of users or contacts to focus on, by any possible criteria.

Segments lets you create realtime groups of customers that matter most or least. You can filter your users or account by pretty much any datapoint possible, from properties over events and screens, over scores and signals and tags, to eventually even stages and health. Here are some examples of Segments that are commonly created:

  • Top customers by usage who signed up in the last 30 days

  • Customers who spend over $1000 last month and sent more than 3 tickets in the last 30 days

  • Top paying customers who had the biggest usage drops

  • Accounts that are adding the most users in the last 7 days

All these segment rules are defined in UI. There's nothing the developer has to do beyond providing identification, properties, events and screens. The logic itself as well as the classification is done in real-time by

Create or edit a segment in contact list view

How does a user or account get into a segment?

Automatically. Upon defining the rules of a segment, each user and account is constantly queried if those rules apply, and if so, they're just simply part of the segment.

Once rules defined, users and accounts are just simply part of segments

Segments throughout

Since users and accounts will be part of one or more segments, not perse mutually excluding one against the other, defined segments will be used throughout the platform. Whether quickly checking contact lists or looking for marketing analytics, segments is always the first filtering element. In analytics, we even allow for up to 3 segments to be compared to each other...

Up to 3 segments can be compared to each other

Segments as actionable field in the tools you already use

Property segments is part of the data catalog automatically adds a computed property 'Segments' to each user and account, and fills in the names of the different segments as multiple entries separated by a CR (carriage-return character). As with all properties, it can be sync'ed to the proper connections where the 'Segments' property was mapped to a custom destination field. If that customer destination field is of type single line, the various values will be separated by a space " ". If it's a multi-line field, a carriage-return character will be used and each value will appear as a separate entry.

Tip: offers free onboarding! 🚀

Go to the Onboarding Page and book your 60 minute spot!

Did this answer your question?