With advanced segments, you can create more specific and maintainable segments than basic segments. You can also use reference segments and transaction mixins in your advanced segments. Advanced segments provide the following additional features:
- Ability to nest grouping logic.
- Share query logic between segments.
- See how many users match a particular chunk of query logic.
You can also generate audience insights for the segment as you build it by clicking 'Analyze Segment' to identify the right set of customers.
Conditions
Conditions are the logical building blocks of a segment. Segments are composed of one or more conditions. Each condition describes a particular activity and/or set of attributes, which a user must match in order to be included in the segment. The attribute type determines the type of search you can run for an attribute. For more information on operators supported for filtering, refer to the conditional operators for various data types.
When a condition is added to a segment, it has to belong to a logical grouping. There are three possible groups - ALL, ANY, and NONE.
Segment filters
Blueshift offers a range of filters that enable you to create segments targeting the right users based on specific features and attributes. For more information, you can view the segment filter categories.
Nested grouping
You can use the advanced segmentation editor to create more complex grouping logic with arbitrary depth and breadth. With advanced segments, you can make AND, OR, and NOT groupings on the fly and nest groupings within groupings.
You can think of AND, NOT, and OR groups as Venn diagrams of logic that match sets of users. In the following example, circles A, B, and C represent a unit of segmentation logic, such as a user attribute match, event match, messaging history match, or another group.
Consider the following points when you create your complex segments:
- The number of matching users inside an AND group decreases as you add logic because the search criteria of who to include gets increasingly specific.
- The number of matching users inside an OR group increases as you add logic because the search criteria of who to include gets increasingly broad.
- The number of matching users inside a NOT group decreases as you add logic because the search criteria of who to exclude gets increasingly broad.
- Groupings are entirely isolated from each other. This means that a given grouping always returns the same set of matching users, regardless of its parent groups.
If you would like more information on using nested grouping to create a segment, please refer to the example of Advanced nested grouping to search for specific customers in the segment examples.
Create an advanced segment
To create an advanced segment, complete the following steps:
- Go to the segmentation index page and click "+SEGMENT."
- Select Advanced Segment as the Type of Segment.
- If available, select the Users option to segment on.
- Add a segment Name.
- Click Create Segment.
- Configure the required logic.
- You can also include a reference segment or a transaction mixin segment.
- Save the segment.
Accessing traffic source data in the segment builder
In basic segments, traffic source details appear under the Traffic Source tab. In advanced segments, use user attributes such as first_utm_campaign
, first_utm_medium
, and first_utm_source
to segment users based on traffic source data. You can find the full list of UTM-related attributes here.
Segment count for an advanced segment
The segment membership count indicates the number of users who match the criteria.
- Segment counts are displayed only for channels that have at least one adapter configured.
- Select the channels for which you want the segment count to be displayed, and then click Refresh user counts to get the latest segment membership count.
- The time of the last segment count refresh is displayed. Click 'Refresh user counts' to obtain the latest segment membership count.
In addition to the total customer count for a segment, you can also find the count of customers in the segment who are eligible for messaging via a specific channel. The counts are obtained as per the definitions below:
Users | Total unique customers (known and unknown) who meet the segment criteria as identified by Blueshift |
Emailable | Any customer who has a valid email address associated with their profile, has not unsubscribed or reported your emails as spam, and has not hard bounced. |
Push Enabled | If you just have a single mobile app setup for your account and your account is configured to message only one device per customer (i.e. their last used device):
|
If you just have a single mobile app setup for your account and your account is configured to message all devices that a customer has:
| |
If you just have set up multiple mobile apps for your account: Any customer who has installed the selected mobile app, has push notifications enabled for the selected app on at least one of their devices, and has never explicitly unsubscribed from any of your push campaigns in the past. | |
SMS Enabled | If you are using Blueshift Full Service SMS or have multiple SMS sender IDs set up for your account:
|
If you are not using Blueshift Full Service SMS and have just a single SMS sender ID set up for your account:
| |
In-app Enabled | If you just have a single mobile app setup for your account:
|
If you have set up multiple mobile apps for your account:
|
Faster user count refresh
To quickly get updated user counts, do not select any channel. This way, Blueshift only computes the total users in the segment when you refresh the segment count. It saves time, as user counts for each channel won’t be calculated.
Matching users for logical grouping
From the summary pane, you can scan for matching users in any chunk of logic. By scanning individual chunks, you can make sense of the numbers from the bottom up.
Additional Information
- Segment conditions and operators
- Segment filter categories
- Basic segment builder
- Optimizing your segments
- Reference segments
- Transaction-based segments
Comments
0 comments