As you know, throughout a user’s browser session, certain information accumulates inside their browser history that is easy to keep track of.
Thus, any data that can be tracked from one’s browser session passed through your code snippet (container JS code) can be used as a segmentation property.
To create a base, UserGuiding provides you 5 different segmentation properties. If you open the dropdown list, you see the following properties:
Visited Page: Pages that users have visited during their unique browser session.
Cookies: Cookies that can be found on users' browser history.
Language: Browser Language of users.
Referrer URL: URL of the page which a user visits right before visiting the targeting page of the segmented guide.
Guide: Guides they’ve interacted with.
In the example below, you can see the rules for the Visited Page. By typing down a value -a complete URL of a page or a partial URL-, you can segment users based on the pages they've visited.
Segmentation rules utilize the data which is stored in an end-user's browser session to condition which users are targeted.
They vary according to the property you'd go for.
For instance, if you select Guide as the property, the conditioning rule can be "not seen", meaning, users who've not yet seen X(guide name) constitute this segment.
As another example, you can review the following image of a segment that is set to a group of end-users whose Browser Language is Belarusian. Here we use the rule is.