Woopra’s Segmentation filters allow you to set up powerful behavioral Segments to study the audience that is most important to you and your KPIs.
Leveraging segmentation filters, you can answer some of the most critical questions such as:
- What behavioral attributes do my users have in common?
- What actions have my users taken while engaging with my marketing website or product?
Our segmentation filters are both very powerful when it comes to defining your audience and extremely flexible as you can leverage multiple types of data within Woopra.
The following data points can be applied to the segmentation filters:
- Actions or associated Action Properties
- Visit or associated Visitor Properties
More information about each type of data can be found in this document.
Harnessing Actions/Action Properties, Visit Properties, Visitor Properties or a combination of those within the segmentation filters will help you to better understand your users and take action on your valuable data.
To access Woopra’s segmentation filters, click the “+” sign in the “Performed by” section of Woopra’s analytics reports, or go to Segments in the Configure Section and press on “+” sign right to next to the “Filter by” field.
You’ll see a dropdown where you can search for a property or an action you want to filter by. To help differentiate, all filters in the drop-down are tagged as either “Action”, “Visit” or “Visitor”.
When it comes to understanding what actions users have performed, it’s always a good idea to start filtering by Actions and Action Properties. Actions are any events that you’re tracking within Woopra and action properties are the associated attributes defining these events. Learn more about action and action properties here.
First, select the action you want to analyze by – this could be a payment, signup, login or any other custom action you’re tracking within Woopra. Please note that Woopra will default to an action performed at least once within the last 30 days. You can always customize how often you want this action to be performed by your users and what the timeframe for this action is.
After selecting an action in the drop-down, you’ll see the “+ Add condition” button underneath the action. This is where you can select your action properties. Note, that for every action Woopra defines two types of action properties:
- Custom Properties - These are the custom properties you’ve set up for tracking with your event. Every action will have its own custom action properties – for example, if you’re tracking payment as an event, custom action properties associated with this event could be the payment amount, user plan, payment type etc. You can manage custom action properties in your Action Schema. Please check our documentation on tracking custom properties for your project. If you have any questions about how to set up custom action properties, consult with your developer or feel free to reach out to us at [email protected]
- System Action Properties – These are the action properties associated with every action you’re tracking in Woopra by default. They include Campaign Name/Source/Medium, Exit/Landing Page, Action Type and Duration. Check out this document on all system action properties that Woopra tracks by default.
Select an action property that you want to define your event by.
Note: You don’t need to select an action property if you want to analyze just only that action, however, action properties can expand your insights if you’d like get more specific in the analysis you’re performing.
For example, you could select “Payment” as an action to see all users who’ve made a payment. Similarly, you can select “Payment” as an action and add an action property such as “Payment Plan equals Enterprise.” In this case, Woopra would show all Enterprise users who have made a payment in the defined period.
The “Aggregation” section of the Segmentation filter allows you to sum up an action or one of its properties. Think of Aggregation as a way of defining how many times a user has performed or not performed a certain action or the total value of action properties you want to set a constraint for. There are three types of aggregations you’ll find in the Segmentation filter:
- Count – The Count function allows you to define the number of times a user has performed the action you’re analyzing. An example would be, “users who’ve made a payment at least three times.” Alternatively, you could set the count to “0” to see users who have NOT performed a certain action. For example, you could segment by, “users who have never visited your website.”
- Count Once Per visit – The Count Once Per Visit function allows you to define the number of times a user has done a certain action while having an active session on your website or app. For example, using the Count Once Per Visit function, you could define a constraint such as, show me, “users who have visited my documentation pages at least times in a single visit.”
- Sum of Amount – The Sum of Amount function enables you to calculate how many times an action was performed within the selected timeframe. For example, by applying Sum of Amount, you could analyze a payment action where the sum of the amount is greater than $5,000. Woopra would then create a Segment of users who’ve made payments of more than $5,000 in total within the time period defined.
- Sum of Action Duration – The sum of Action Duration helps you to sum up the durations of your actions.
The “Timeframe” section allows you to define a date range for the action you’re analyzing. There are three timeframe options:
- Preset Timeframe – You can select a number of timeframe options preset for you such as last 30 days, last 90 days, last 365 days and so on.
- Date Range – Date range allows you to select a static timeframe for your segment, such as “March 4, 2017 through March 16, 2017.”
- Relative – Relative timeframe allows you to select a timeframe that is relative to the present day. This timeframe is dynamic and is updated in real-time. For example, you could select a relative timeframe that’s dynamically updated to look at people who performed an action, “from ten to fifteen days ago.”
Visit properties give you incredible power for analyzing a users visits or sessions performed on your website or application. Keep in mind that visit properties are dynamic and can change with each user session. Woopra tracks visit properties out of the box and you can find more information on which visit properties Woopra tracks automatically here.
You can apply visit properties in the Segmentation filters within the same drop-down used for action properties. Simply type in the visitor property you’d like to filter by and set the constraint accordingly. For example, you could filter by the visit property “Country” where the country is “Canada.”
After selecting a visit property, you’ll notice that the action section will default to “All Actions.” This means that Woopra will build a segment of users who’ve performed any action on you’re tracking and who match the visit property you’ve defined.
You can always change “All actions” to any action you want to expand your analysis with visit property constraints. For example, you can choose “Payment” as an action, and if the visitor property country is set to Canada, Woopra will create a segment of users who’ve made a payment while being in Canada.
Visitor Properties in Woopra help you answer the question about who your users are and what attributes define them. Examples of visitor properties might be user company, age, gender email address etc. You can set up any visitor properties that are relevant to you and our visitor schema would assist to manage these properties
By applying visitor properties in the segmentation filters, you could build a segment of users who match certain demographic, firmographic or behavioral constraints.
For instance, if you’re tracking “Company” as a visitor property, you can leverage the “Company” visitor property in the filter drop-down and set the company name Slack, for example. Woopra will create a segment of users at the company, Slack, in this example, who’ve engaged with your product within the defined time period.
Please note that with visitor properties, you need to define a certain condition you want to filter by. If you’re segmenting by companies, you’ll need to select a company name to filter by. If you’re segmenting by ages, you’ll need to select the age range for your segment.
You can create multiple Segmentation filters in Woopra to be more specific in defining your Segments. Woopra has the option of combining the filters using the following functions:
- 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.
For example, if you want to create a Segment of users who’ve submitted at least five support tickets within the last 90 days and who have an ARR greater than $10,000, you could create the two following filters:
- Action is set to “Ticket Submitted”, count is “at least 5 times”, and the timeframe is last 90 days
- Visitor Property is set to “ARR”, visitor property constraint is “ARR>$10,000.”
Alternatively, if you want to create a Segment of all “United States” users who’ve started a chat conversation with you or opened a promotional email, you’ll set up segmentation filters as follows:
- Visit Property is country, visit property constraint is USA, action is “Chat Initiated”
- Visit Property is country, visit property constraint is USA, action is “Email Opened.”
If you have more than two filters that you want to combine, you can leverage even more complex Segmentation called Nested Logic Segmentation. Just drag and drop filter buttons to use this feature.
Let’s take an example. Say you want to identify all customers that are non-paying, basic users of your web and mobile app in the last month so that you can determine how to engage with them. Simply add the nested logic statement as shown below:
- ARR (visitor property) equals 0 AND Email (visitor property) exists AND
- Web View (action) at least once in last 30 days OR Mobile View (action) at least once in last 30 days.
Updated 2 years ago