Segmentation

User Segmentation is a service where the admin can divide the users of each project into segments according to a specific set of rules. The rules will be provided by the admin, and can be differentiated into 3 categories.

  • Attribute

  • Event

  • Intent

Each category will contain multiple parameters. A rule can be constructed by selecting a parameter and can be extended by comparing with a specific value.

How to construct a rule

To construct a rule, the admin needs to select a few key points. Firstly, the admin need to choose a category, and decide on whether he wishes to find the user set which will fall according to the rule or not by choosing the Include or Exclude option. Then the admin will be shown a list of parameters from which he can choose the parameter on which he wishes to construct the rule. The parameter can again be compared to a single value or multiple values depending on the type of comparison the admin has chosen. Currently, the comparison operators provided are:

Segmentation
  • Is: This operator is used with the category Attribute. It will compare the attribute of each user with the value provided by the admin and filter out the users whose attributes are the same as the value provided by the admin. This operator also can be used with the categories Intent/Event. The admin can provide an integer value (e.g. 5) and filter out the users who have triggered the selected Intent/Event exactly that number of times.

  • Is not: This operator is used with the category Attribute. It will compare the attribute of each user with the value provided by the admin and filter out the users whose attributes are different to the value provided by the admin. This operator also can be used with the categories Intent/Event. The admin can provide an integer value (e.g. 5) and filter out the users who have not triggered the selected Intent/Event that number of times.

  • Contains: This operator is used with the category Attribute. It will compare the attribute of each user with the value provided by the admin and filter out the users whose attributes contain the value provided by the admin.

  • Does not contain: This operator is used with the category Attribute. It will compare the attribute of each user with the value provided by the admin and filter out the users whose attributes do not contain the value provided by the admin.

  • Is any of: This operator is used with the category Attribute. It will compare the attribute of each user with the list of values provided by the admin and filter out the users whose attributes are the same as at least one of the values provided by the admin.

  • Is not any of: This operator is used with the category Attribute. It will compare the attribute of each user with the list of values provided by the admin and filter out the users whose attributes do not contain any of the values provided by the admin.

  • Greater than or equal to: This operator is used with the categories Intent/Event. The admin can provide an integer value (e.g. 5) and filter out the users who have triggered the selected Intent/Event at least that number of times.

  • Less than or equal to: This operator is used with the categories Intent/Event. The admin can provide an integer value (e.g. 5) and filter out the users who have triggered the selected Intent/Event at most that number of times.

  • Is greater than: This operator is used with the categories Intent/Event. The admin can provide an integer value (e.g. 5) and filter out the users who have triggered the selected Intent/Event more than the provided number.

  • Is less than: This operator is used with the categories Intent/Event. The admin can provide an integer value (e.g. 5) and filter out the users who have triggered the selected Intent/Event less than the provided number.

Short Note on each Category

  • Attribute: The user base of a project can be segmented on a specific set of user attributes.

    • Phone

    • Email

    • Language

    • Gender

    • Timezone

    • City

    • Country

Segmentation Example
  • After selecting the attribute, all users who have provided data on this attribute will be filtered in the segment. The admin may further refine the rule by comparing the attribute with a string value.

  • Intent: The user base of a project can be segmented on the intents provided by the wit app(?). The admin may select an intent to construct a rule and find the number of users who have triggered that intent at least once. The admin may also customize the rule by selecting one of the comparators according to the description provided above and getting the desired statistics.

  • Event: The user base of a project can be segmented on the events created by the admin while building the bot. The admin may select a specific event to construct a rule and find the number of users who have triggered that event at least once. The admin may also customize the rule by selecting one of the comparators according to the description provided above and getting the desired statistics.

‚Äč