Skip to content

New Segment

When you are on your CDP, you can manage the Segments available to you.
If there are none, or you need to add some manually, you can follow the steps below.

First of all, on the CDP, find the 'Segments'-tab and click to open it:

Segment tab

This leads you to the Segments Overview page. If you have permissions to manage Segments, you will see a big '+' button. Click it to start making a new Segment manually.

Segments overview

Step 1: Segment info

Start by filling in the Segment information:

  • Name: the title that will appear on the Card, on the Segments overview. Let's make one to do with Marketing, so pick that for the name.
  • Description: a short description to give some information or context about the Segment. Appears on the card.
  • Tags: extra meta information, not currently used in the Platform to filter Segments but can be useful to provide extra context to Segments. 1 current use is to differentiate Segments made in the Platform (automatically tagged manual) from Segments created elsewhere via the Unomi API

Segments step 1

Step 2: Segment rules

Here we decide what criteria must be used to build a Segment.
We can combine Rules to create as simple or complex a group as we want.
We can nest these groups, also indicating if 'all' the rules in a group must be met or if 'any' will do.
And we can of course, combine Rules and groups of Rules.

Segments step 2


You will occasionally find a green i-icon next to a label or Rule. Clicking it opens a modal dialog with some extra information and/or a link to these support pages.

Setting a group operator

All segments start with 1 main group. You can start by changing (or leaving) the operator (located in the header of the group). The default value is all (so all the Rules inside the group must be met).
all uses the and operator behind the scenes, any uses the or operator.

Segment Rules start

Segment Group operator

Editing a Rule

At the very start of a new group, an empty Rule is already included, so you just need to change the Property, the Comparison and (depending on those) a Value.

  • Property: this dropdown lists the properties that are being logged by the data capture script that is added to the website (or web app) connected to this CDP.
    So if we pick last visit, for example, we can build a rule based on visitors last visits.

Segment Rule Property select

Segment Rule Property selected

  • Comparison: You will see this marked as 'required' now. There are a lot of options here. If I wanted to base my segment on an exact date or period when the last visit occured, would use equals. If I wanted to base my segment on visits occuring after a certain date though, I could use 'greater than' (a date in the future is 'bigger' than an older date).

Segment Rule Comparison select

Segment Rule Comparison selected


Picking a Comparison, makes a green i-icon appear at the start of the Rule. Clicking it gives you a bit more context and information about the Comparison.

  • Value: The type of value will depend on the Property and Comparison. Some require a checkbox, some a number or text and others (like 'last visit') requires you to pick a date. In our case, we don't want to use an absolute date (a point in time) but we want a relative date (a point or period in time relative to now). So we click that switch and choose This month in the dropdown.

Segment Rule toggle date type

Segment Rule relative date

Segment Rule relative date select

Segment Rule relative date selected


Only some Properties that deal with dates, let you switch between an absolute date (using a date picker) or a relative date (using a dropdown).
For this example, we're switching to a relative date. This has the side effect of resetting the Comparison. This is because there are different Comparisons for absolute vs. relative dates available.


Not all Rules use a Value. It's only once we have picked a Comparison that relies on a value, that we should now see a new field appear.

Adding a new Group

We now have 1 group with 1 rule that is filled in but we need more criteria.
Not only do we want a Segment based on visitors who last visited our website this month, we also want them:

  • to have surfed to our sales-marketing pages
  • or to have visited out site through a link from our marketing newsletter

To do so, we need to add a new Group after our current Rule. This new group will have to contain 2 new Rules, grouped by the 'any' operator (because we need any of the Rules to apply, not 'all' of them).

So start with clicking the green '+' button coming after the first Rule and pick 'Group'.

Segment add new group

We now have a new (nested) group available and can follow the same steps as before to build up our first Rule.

Segment nested rule

  • For the group's Operator, we set the dropdown to any
  • For the Property, we'll pick capture > surfing > full path.
  • As for the Comparison operator, we'll pick ends with, because the web pages we want to track are the ones ending with a certain text string.
  • The Value will be sales-marketing.

Segment nested rule filled

Adding a new Rule

How do we now add a second rule? We now click the green '+' button that follows our nested Rule (the one about the surfing path) and this time we pick 'Rule'.

Segment add second nested rule

Segment second nested rule

Here again, we set the Property, Comparison and Value:

  • Property: We use capture > utm campaign because this will let us reference a utm tag
  • Comparison: use equals to use exact matches
  • Value: we'll use marketing because that's the utm tag we've used for our links pages in our newsletter

Now we hit Complete and we are (almost) done.

Segment save

Saving the Segment will redirect us to the overview page, with a message that the Segment is being created. This can take a few minutes if your CDP handles a lot of profiles.

Segment creation in progress

Segment added to overview