Suppose your company has two competing subdivisions, such as www.myaudio.com and www.myvideo.com, and you don't want either division to see each other's data. You can configure event-based data segmentation using hostname events to segment the data.

1. Open the Event Manager.
2. From the Portal menu, select Configure > Event Manager.
3. On the Hit attributes tab, create a hit attribute.
   1. Enter the hostname in the Start Tag field. For example: www.myaudio.com.
   2. Do not specify an End Tag. This configuration means that the hit attribute searches for the explicit Start Tag.
   3. Set the other properties as desired.
      Note: When you configure the event for data segmentation, avoid using a NOT operator. The underlying search engine must retrieve all possible values for the event and then apply the NOT to generate proper results, which can significantly impact overall Portal performance.
4. Create an event.
   1. Set Evaluate to First Hit of Session.
   2. For the Track value, select First per Session.
   3. For the Value Type, select Text.
   4. Set Searchable & Reportable to true.
   5. Click the Condition step. For the condition of the event, select the hit attribute you just created.
   6. Click the Value step. Click Select Item to Record.... Select the hit attribute you created.
   7. Do not configure any other attributes.
   8. Click Save Draft.
5. Commit changes for both new objects.

After the changes have been committed, sessions from either website can be segmented based on the hostname events.

1. In the Portal menu, navigate to TMS.
2. In Servers view, open the Search Server node.
3. Click Search Server configuration.
4. Click View/Edit.

   The Search Server configuration window opens.

5. In the Authentication area, click Modify.
6. The Authentication dialog controls which groups have user access and administration access to the Search Server and consequently the Canister.
7. To enable NT authentication, click the NT Authentication button. Additional options are displayed.
8. From the Domain drop-down, select the domain name for your network. The Search Server automatically derives the domain controller on which the groups are located from the domain name.
9. To add the User Groups to the list, click Add to User Groups.
   Note: User groups are limited to see only the data specified by the Admin group and cannot use the Search Server interface to interact with the Tealeaf CX Server.
10. The Add Group dialog displays all the groups available on the network. To show all users belonging to a particular group, click List Group. Select a group and click Add.
11. To add the Admin Groups, click Add to Admin Groups.
    Note: Groups with administrative access can edit event definitions and see all the data on the Tealeaf CX system.
12. Configure Authentication.
    Note: You must select at least one admin group when using Authentication.
13. Add the user groups and admin groups. You must assign an admin group to administer the event definitions and perform other administrative tasks, like setting up profiles in RTV.

For example, when a member of the audio group views sessions in either the Portal or the CX RealiTea Viewer, only the sessions from www.audio.com are displayed.

Data segmentation is entirely event-based. Each group added in Search Server Configuration can have multiple events, which can be combined using the Boolean operators AND or OR. Users who are members of multiple groups have each set of group events combined by OR.

1. In the Authentication dialog, select the Group Name in the Data Segmentation Search Filters section.
2. Click Add Events to Group and select an event in the Event Selection dialog. You can add multiple events to the same group list.

   By default, the events are ANDed together, which means that AND is used as the operator when filtering sessions. When a session contains all of the events, it is viewable by that particular group. Data segmentation by event is essentially an event-based session search. The search query is appended to every Search Server request made from either the Report Server or Portal Web application.

3. In the Authentication window, click Events Visible in the Portal. Check the events you want to be displayed in the Portal Web application for the selected group. If no events are selected, no events are displayed in the Portal when a member of that group logs on.

Following are some additional examples of event filtering.

Suppose you have configured the following three groups in Search Config:

• tealeaf\usersevent 1tealeaf\eng (Items AND'ed together)
• event 2event 3tealeaf\qa (Items OR'ed together)
• event 4event 5event 6

A user who's a member of tealeaf\users searches for session: (canisterAppEvent contains 1) and (session)

A user who's a member of tealeaf\eng searches for session: (canisterAppEvent contains (2 and 3)) and (session)

A user who's a member of both tealeaf\eng and tealeaf\qa searches for session: (canisterAppEvent contains (2 and 3) or (4 or 5 or 6)) and (session)

Verify that Portal NT Authentication is enabled.

1. In TMS, select the Tealeaf node.
2. Click Shared Configuration information.
3. Click View/Edit.
4. Click the Portal tab.
5. Click the Authentication Method setting.
6. Verify that NT is selected in the drop-down.

What the individual user sees in the Portal depends on how the Administrator has configured that particular user.

1. Create an event that is triggered in all sessions that you wish to hide.
2. Through Search Server, create a group to contain all users who are not allowed to see the sessions.
3. Add the users to the group.
4. In event segmentation, add the created event to this group.
5. Set its operator as NOT.
6. Save changes.