3,141 total views, 12 views today
As I’ve mentioned in previous posts, the segment builder providers you with a huge amount of potential because it can help you to compare different audiences to find insights that can drive your eCommerce strategy. But in order to use the segment builder effectively, you will need to understand some terminology, so that your segments mean what you think they mean.
Here are a list of terms you will see used in the segment builder, and what they mean:
Per User / Filter Users: This option enables you to segment based on specific users. This means that if customers visit your website for more than one session you will see all of their sessions in aggregate, even if they didn’t perform any eCommerce actions in some of the sessions.
So, for example, “all users with a transaction” will show all the sessions by those users, even if the session did not contain a transaction.
It is also important to note that filtering by users in Google Analytics has a 93-day limit; essentially, equivalent to three months. (You can get around this using other tools alongside Google Analytics).
Per Session / Filter Sessions: This enables you to segment based on specific sessions (i.e. the specific visit in which the user did the thing that you are interested in). This means that if they visit your website for more than one session you will not see the other sessions.
So, for example, “all sessions with a transaction” will show only the sessions with a transaction, and not the sessions before or after a transaction if the user came back to your website again.
This is useful for identifying behaviours that are associated with another specific action, but not so useful if you want to understand your visitors’ behaviours overall. Filtering by sessions does not have a time limit, so you can also use this instead of users, if you need a segment that is longer than 93 days.
Include / Exclude: This lets you control whether you are including or excluding the condition from your segment. So including the country of Australia would provide you with a segment with only Australians, whereas excluding the country of Australia would give you people from everywhere but Australia.
Note: Include can have unusual behaviour. If you include A and B then the system will filter down to only data that is both A and B at the same time, not A and B separately. So be careful when you stack conditions with include, as you can end up with some highly misleading data.
Contains: The word ‘contains’ means ‘does the text contain the text that you have typed?’; i.e. “men’s shoes” contains “shoes” and “kids’ shoes” contains “shoes”.
Exactly Matches / Equals / Is one of: ‘Exactly matches’, ‘equals’ or the equals symbol ( = ) and ‘is one of’ means that the text or number that you have typed in your condition is exactly the same as the data stored in Google Analytics. In the case of ‘is one of’, it has to exactly match one of a list of items. You can also choose ‘does not exactly match’, ‘is not equal’, or ‘is not one of’ if you want to reverse the condition.
Starts with, ends with, matches regex: These conditions let you be more specific about the text and narrow it down to specific options, without being forced to narrow down to just one option. For example, all SKUs that start with ‘D’ will show all the SKUs that start with the letter only. Matches Regex lets you be even more specific. Regex is short for Regular Expression. You can read the Google Analytics Regular Expressions here.
Greater than ( > ), Less than ( < ), Greater than or equal to ( ≥ ), Less than or equal to ( ≤ ): These enable you to select from the data that is stored as numbers. So, for example, all sessions with transactions would require “include sessions where transactions > 0”.
OR: The condition will be met if A is true, or B is true. This means that the segment will be bigger.
AND: The condition will be met if A is true, and B is true at the same time. This means that the segment will be smaller.
Product data: you can specify any product data, whether it be name, category, brand, variant, SKU etc. You can also choose more than one criterion from this section. So, for example, if you have categories of women’s shoes, kids’ shoes, and men’s shoes then you can specify products in categories containing “shoes”, and all three will be captured.
As you can see, you can be very specific when building segments. It is important to build the segment logic carefully, because once you see the data in an aggregated form it is almost impossible to detect that you have made a mistake when constructing the segment. And this can cause you to infer results that just aren’t true.
Now that you understand the lingo and how to build your segments, lets have a look at what segments to build.