Managing Player Segmentation

What are Segments?

The UserWise Segmentation module is an advanced player / audience segment engine that allows segmentation based on three core dimensions: time, player events, and player attributes.

You can manage your segments by clicking "Segments" in the top navigation bar.

You can create a new segment by clicking the "+ Segment" button, edit a Segment by clicking on its row, or delete a Segment by ticking the box to the left of it and clicking the now available red Delete button. 

Creating/Editing Segments

Although our segmentation is advanced, it does not have to be daunting. There are four total definitions you can use when creating your segment: Player Events, Player Attributes, Time, and Player IDs.

Although more technical in nature, our API Documentation also houses a Segment Targeting guide, as well as an Attribute Targeting and Event Targeting guides.

Player Events

One of the first items to note is that player events are different than an in-game event.  A player event is any event that happens to a player while they're playing your game.  Imagine a user completing the tutorial of your game; you can push the tutorial_completed event to UserWise.

Player events can also have attributes attached to them. Back to the tutorial_completed example, you could attach an is_first_time boolean attribute to the event which could tell UserWise if this is their first time completing the tutorial or not. You can learn more about player attributes below, and event attributes function on the same principles.

To add a new Player Event Group click the "+ Add Event Group" button. One of the first steps is deciding on the event group's logical operator; is it and, or, or not? If you choose and, then all event conditions in the group MUST be met in order for a user to be added to that segment. Choose or, and ONLY ONE of the event block conditions must be met.  And finally, choose not, and NONE of the event block conditions can be met in order for a player to be considered for this event group.

*Tip: If you are seeing a 🚫 icon when clicking "+ Add Event Group," this indicates that there are no available Player Events in the system yet and must be added first. 

Once you've chosen your group logical operator, you're going to need to fill out your event blocks.  You're provided with 1 when you create your first event group. First, choose an event from the dropdown. Then, if that event has attributes, you'll be provided with an optional "Where" button beside the dropdown.  This can be clicked to add attribute filtering to this event block. You can see an example of an event below:

You can also add more than one event group together.  This is where the connecting and and or logic comes in. You can say "match this event group" OR "match this event group", or you can say "match this event group" AND "match this event group".

Finally, player events in the UserWise system can be grouped logically and have logical operators (and/or) connecting the groups, and a logical operator that connects the internal items of the group (and/or/not).

Player Attributes

Player attributes (aka player traits) can be thought of as simple key-to-value pairs.  These keys can each have a single value with one specified data type. Those data types are: string, integer, float, datetime, and boolean.

To add an attribute click the "Add Attribute" button. You'll be provided with a new attribute row where you must select three items: the attribute name to filter against, an operator (e.g. equals, less than, greater than, between), and 1 or more values (depending on the operator).

Attribute selection is not chained together and is treated as such that all must pass all player attribute filters.

You can see a segment with a few player attributes setup below: