If your employees regularly use your enterprise website, you might find it useful to filter out their session data from reporting while still capturing the information.
In the following solution, internal employee visitors are connecting to the company website from
the same IP address (aaa.bbb.ccc.ddd
). Through Privacy.cfg
configuration, Experience Analytics can universally identify the requesting application
(TLT_APPLICATION_NAME
) for employees with the value Employee
.
Note: This solution must be deployed in the pipeline before the Reference session agent is
applied.
In Privacy.cfg
, make the following changes:
[Rule1]
ReqField=REMOTE_ADDR
ReqOp=EQ
ReqVal=aaa.bbb.ccc.ddd
Actions=Employee
[Employee]
Action=ReqSet
ReqSet Section=appdata
ReqSet Field=TLT_APPLICATION_NAME
Replace String=Employee
After you have completed the above configuration, be sure to enable the Employee
value:
System\Reference_Application.txt A xx employee
To filter employee sessions:
- Employee sessions can then be easily filtered by Experience Analytics users as
needed based on
TLT_APPLICATION_NAME=Employee
. - To find employee sessions, use the search builder. In the
TLT_APPLICATION_NAME
value, enter Employee. - All existing reports can be filtered for employee session data by using the Application
Filter in charts.Note: The Windows™
Privacy.cfg
file contains many examples of filtering operations.
Comments
0 comments
Please sign in to leave a comment.