Apply segmentation rules for tracking Tribe activity and reach.*
This article describes how to configure and apply segmentation rules to your Tribes. This allows you to track and measure audience-specific activity and performance, so you can make informed decisions on campaigns or experiment with UX changes for specific groups.
Topics covered here:
How do I access the Tribes page?
To access the Tribes page, sign in to your mtribes account and open the Space you want to work in. Next, open the Tribes page using the vertical navigation on the left-hand side of the screen. Select a Tribe card and click to open the details page. This is where your Tribe metrics and insights will appear after integration.
How do I configure Tribe rules?
When you open the Tribe details page, you’ll see three primary selector menus. These dropdown menus contain a broad range of parameters for you to apply as filters. A maximum of ten parameter filters can be applied to each Tribe.
1. Audience selector menu - switch between Users, Visitors, or Users and Visitors.
- Users - the total number of users (known) associated with a Tribe.
- Visitors - the total number of visitors (unknown) associated with a Tribe.
- Users and visitors - the total number of combined users and visitors associated with a Tribe.
2. Any/All selector menu – switch between Any or All parameters.
- Any - the Tribe is tracked against any of the parameters set.
- All - the Tribe is tracked against all the parameters set.
3. Parameter selector menu – select from a broad range of Attributes, Behavior metrics, Contextual properties, Events, or User tags and set conditions to refine your segmentation.
Attributes include important moments and characteristics of your audience:
- Created - the first date a user record was created in mtribes.
- First seen - the first date a visitor or user was active on mtribes.
- Joined – the first date a user signed up for your product or service.
- Known – the first date a user became identified in mtribes.
- Location - filter on a specific location name or use a range of alternative options to filter out locations.
- User agent - filter on technical data (e.g., operating system, browser).
- Device type - filter on a specific device type (e.g., mobile, desktop).
Behavior includes various session metrics:
- Active days – the number of days a user or visitor was active in the last 7 or 30 days.
- Average sessions - the average number of sessions in the last 7 or 30 days.
- Total sessions - the total number of sessions in the last 7 or 30 days.
- Average session time - the average session length in the last 7 or 30 days.
- Total session time - the total number of minutes in a session time in the last 7 or 30 days.
- Last seen - the last date a visitor or user was seen on mtribes.
Contextual properties are unique user traits organically identified during the runtime of your app, like during a seasonal campaign. This could include labels like:
- Subscription type
- Referral campaign
Events are user interactions with your application, such as clicked, viewed, and watched. mtribes includes a list of existing events to select from, or you can define your own custom event.
User tags assign a set of tags to each user. This makes it possible to synchronize existing user segmentation from your CRM or other location with mtribes. User tags are persistent to the user and do not vary across devices. This could include tags like:
- In trial
- Football fan
Next - Customize Tribe cards