Have a question?

Defining Segments

Overview

Segmentation filters allow you to define the population you would like to study.

Segmentation filters are used for segmentation in nearly all of Woopra’s features, such as:

  • People View – Segmentation filters allow you to view lists of specific customer segments
  • Analytics Reports – Segmentation filters allow you to segment reports
  • Notifications – Segmentation filters allow you to be notified when customers in specific segments behave in a certain way

There are two types of segmentation filters: People who are filters and People who did filters.

  1. People who are filters allow you to segment based on custom visitor data, such as company, email, gender, age group, etc
  2. People who did filters allow you to segment based on how customers behaved on your website

Segmentation Filters

“People Who Are” Filters

People who are filters allow you to segment based on data that defines who the customer is, such as their company, level of seniority, gender, and any other custom visitor data you are tracking. Please note that the custom visitor data you are able to segment by is defined in your Schema.

Example: How To Create a People Who Are Filter

If we are tracking the gender of our customers using custom visitor data, we may segment based on people who are male with the following steps:

  1. Click on the + button next to “People who are”
  2. Using the “Property” drop-down menu, select the the property “gender”. Since we have already defined the custom visitor data “gender” in our Schema, it will be pre-populated in the drop-down menu.
  3. Using the “Value” drop-down menu, select “is” and then type “male” into the field at the right
  4. Finally, click “Apply” to set the filter

“People Who Did” Filters

People who did filters allow you to segment based on customer behavior, such as which actions they’ve committed, what device they were using, and more.

Below is an explanation of each section of the “people who did” filter.

Action The “Action” drop-down menu lists all of the actions you may select from. This list includes both events Woopra tracks by default, such as pageviews, or custom events which you have added such as “payment”, “sign up”, “play video”, etc. Note that the custom events are pre-populated in the drop-down based on how you have defined them in your Schema.

Action Constraints

Once you select an action, a section will appear below the drop-down that reads “+ Add Action Constraints”. By clicking this, you will be able to add constraints to the action in order to further define it.

The options listed in the constraints drop-down are based on the properties you have defined for the given custom event in your Schema. For example, you may have a custom event “payment”, for which you track the properties “amount”, “package type”, and “payment method”. These three properties will be pre-populated in the actions constraints drop-down menu.

Aggregation The “Aggregation” section of the filter allows you to aggregate the action or one of its properties. There are two types of aggregations:

  • Count – This allows you to define the number of times the customer performed the action. For example, “customers who made payments at least three times”.
  • Sum – This allows you to add up a property to further define the filter. For example, “customers who made payments that totaled greater than $500”. Whether a property is pre-populated as a “Sum” option depends on how you have defined it in your Schema.
Timeframe The “Timeframe” section allows you to define the date range for the action. There are two timeframe options:
Relative – This allows you to select a timeframe that is relative to the present day. This timeframe is dynamic and will be constantly updated in real-time. For example, the timeframe “30 days ago” will always be 30 days before the current day.
Exact – This allows you to select a static timeframe, such as “March 4, 2013 to March 16, 2013”.
Visit Constraints The “Visit Constraints” section allows you to define certain criteria that the visit must match when the filter’s action is committed by the customer. This could be the visit referral source, the browser used during the visit, the customer’s location during the visit, etc.

For example, I may want to create a filter for “customers who made a payment from a mobile device”, where “device type is mobile” would be the visit constraint.

Why can’t I define location/browser/device/etc in “People who are”?

The reason you must define the customers’ location/browser/device/etc in the visit constraints is because these attributes may be different for each visit. For example, I may visit your website from my work computer in Palo Alto, CA and then subsequently visit your website from my iPad in San Francisco, CA. The device and location of each visit is different.

If you would like to filter out a segment of customers who ever did any action from a certain location/browser/device/etc, you can do so by creating a filter for “Any Action” with the desired visit constraint. To create this filter, follow these steps:

  1. Add a new “people who did” filter by clicking the + button next to “did”
  2. Leave the action drop-down menu set to “Any Action”
  3. Add a visit constraint at the bottom of the filter editor by clicking “+ Add Visit Constraint”
  4. Select the location/browser/device/etc you would like to filter by from the drop-down menu and enter the corresponding values
  5. Click “Apply”

Example: How To Create a People Who Did Filter

If we are tracking the custom event “payment” and sending the property “amount” with it as defined in our Schema, we may segment all customers who have made at least three payments over $200 in the last 2 weeks from a mobile device by following these steps:

  1. Open the “people who did” filter editor by clicking the + button next to “did”
  2. In the Action section, select the action “payment” from the drop-down menu. Since we have already defined the custom event “payment” in our Schema, it will be pre-populated in our actions drop-down menu.
  3. Add an action constraint by clicking “+ Add Action Constraint”
  4. Select “amount” from the action constraint drop-down menu. Since we have already defined the property “amount” in the Schema for our custom event “payment”, “amount” is pre-populated in the action constraint drop-down menu for the action “payment”.
  5. After selecting “amount” from the action constraint drop-down, select “greater than” from the next drop-down and type “200” into the next field so that it reads “amount greater than 200”
  6. In the Aggregation section “Count” view, set the drop-down to “at least” and then type “3” into the next field so that it reads “at least 3 times”.
  7. In the Timeframe section “Relative” view, type “14” into the first field and leave the second field as “0” so that it reads “From 14 to 0 days ago”
  8. Add a visit constraint by clicking on “+ Add Visit Constraint”. Select “Device Type” from the first drop-down menu, leave the second drop-down menu as “is”, and select “mobile” from the third drop-down menu so that it reads “device type is mobile”.
  9. Click “Apply”

Adding Multiple Filters

You can combine any number of filters to further segment your data. You have the option of combining the filters in one of three ways:

  • And – The “and” parameter will retrieve visitors who match all of the filters
  • Or – The “or” parameter will retrieve visitors who match any of the filters
  • Then – The “then” parameter will retrieve visitors who perform activities in the order in which the filters are placed.

Segmentation Operators

Please note that the “then” parameter is only available for the “people who did” filters.

To switch between “and”, “or”, and “then”, simply click the existing conjunction and select the desired one.

Need any help? Contact support