Introduction
This page explains the concept of user segments/user lists and the impact it has on visibility on all the kinds of content you can create within Spencer.
Table of content
- The concept
- The importance of enriched data through your system of record
The concept
Various types of content you make available in Spencer – such as news publications, documents, links, etc – can be restricted to only be accessible to a sub-segment of your entire end-user audience.
To restrict content by audience, you’ll first need to create sub-segments – which you can do by creating user lists. A user list, is simply a collection of users. There are 3 user list types:
Dynamic user list: rule-based list of users, automatically updated
(e.g. all users who work in the Finance department, stationed in the Brussels office)Static user list: hand-selected list of users, not automatically updated
CSV user list: csv-selected list of users, not automatically updated
We highly recommend you to use Dynamic user list, as they update automatically whenever your user information gets updated.
Next, while creating or editing a specific instance of Spencer content – like a publication, document, or link – you’ll want to specify one or more user lists. A user that is part of one of the specified lists, will have access to this piece of content. If a user is not part of any of the specified lists, this piece of content will never show up in their Spencer app(s).
The importance of enriched data through your system of record
As the user lists are embedded throughout Spencer functionalities, it is important to understand that, if you want to create a Dynamic Userlist, enriched content, is key to created valuable user lists. In Spencer, we have multiple fields per user that contain information you can use to create a query. Below the fields that are segmentable:
- Contract Type
- Department
- Division
- Subdivision
- Job Title
- Domain
- Company
- Country
- Region
- Zone
- Default site
- Tags
- Preferred Language