The segment editor is the place where you build your segments. Plainflow will empower you with an extremely flexible editor.
It all starts with the distinction between
known users and
Select the radio button
exclude anonymous users to create a segment pupulated by your customers profiles. Anonymous users will not be enrolled in this segment.
Select the radio button
include only anonymous users to create a segment populated by anonymous users only. Anonymous users only will be enrolled in this segment.
Once you’d definied the type of users that you want to select with your Segment, you need to define a set of
rules and a
A rule consists of set of instructions that need to be evaluated. A ruleset consists of a set of rules.
You can nest rules in
When creating a rule inside you have to explicit whether you want to segment for customer attributes (
properties) and/or customer activities (
How to filter for user properties? 👨
User properties are attributes saved in your user profiles.
Supported property types and operators:
|Property type||Supported operators|
How to filter for user activities? ⚡
User events can be
not performed. You will set how many times your user had to performed that event and you will set a time range range.
☝ Keep in mind! When you are filtering for the
dateproperty you are always using a UTC date time. That might be different from your timezone.
Additional default events parameters ⚡
For every user events you are sending to Plainflow, you can also filter for the following parameters.
These parameters are automatically populated by Plainflow.
If you want to filter for these additional parameters you need to use the suffix
|Boolean||Whether a user is active. This is usually used to flag an |
|Object||dictionary of information about the current application, containing |
|Object||Dictionary of information about the campaign that resulted in the API call, containing |
|Object||Dictionary of information about the device, containing |
|String||Current user’s IP address.|
|Object||Dictionary of information about the library making the requests to the API, containing |
|String||Locale string for the current user, for example |
|Object||Dictionary of information about the user’s current location, containing |
|Object||Dictionary of information about the current network connection, containing |
|Object||Dictionary of information about the operating system, containing |
|Object||Dictionary of information about the current page in the browser, containing |
|Object||Dictionary of information about the way the user was referred to the website or app, containing |
|Object||Dictionary of information about the device’s screen, containing |
|String||Timezones are sent as tzdata strings to add user timezone information which might be stripped from the timestampEx:|
|Object||Dictionary of |
|String||User agent of the device making the request.|
Learn more about context in the developers documentation.
Not using Plainflow yet? Get your free account here. 👈