User Session Identification Based on Strong Regularities in Inter-activity Time

Abstract

Session identification is a common strategy used to develop metrics for web analytics and behavioral analyses of userfacing systems. Past work has argued that session identification strategies based on an inactivity threshold is inherently arbitrary or advocated that thresholds be set at about 30 minutes. In this work, we demonstrate a strong regularity in the temporal rhythms of user initiated events across several different domains of online activity (incl. video gaming, search, page views and volunteer contributions). We describe a methodology for identifying clusters of user activity and argue that regularity with which these activity clusters appear implies a good rule-of-thumb inactivity threshold of about 1 hour. We conclude with implications that these temporal rhythms may have for system design based on our observations and theories of goal-directed human activity.

Contributors’ Withdrawal from Online Collaborative Communities: The Case of OpenStreetMap

“…The approach was based on the fact that when the participants have some free time to contribute, the changesets generated during their editing sessions will form clusters in time as demonstrated by Halfaker [22] for different online communities. The closer the changesets, the higher the odds the edits were made on the same editing session and consequently on the same day (from contributors' point of view).…”

Leverage Web Analytics for Real Time Website Browsing Recommendations

“…Such time measure often suffers from several distortions; actually getting the accurate time on page and/or delimiting users' web sessions has posited challenges continuously addressed for some years to the present e.g. [17] [18]. We had tackled this problem by implementing a combination of techniques that allows to achieve more accurate measures regarding the GA time on page metric.…”

A Framework for User Authentication and Authorization using Request based One Time Passkey and User Active Session Identification

“…Session ID keys [13] [18], in their conventional form, do not offer secure Web [19] browsing. In existing methods skilled hackers can acquire session IDs by using the process called session prediction, and then masquerade as authorized users in a form of attack known as session hijacking [3]. In all of the existing programming language the unique session identification number will contain 16 to 32 digit values [25].…”

“…To identify the user's session identification, the unique session identification value is used. Different programming languages use different value assigning methods for user session identification [3] [4]. Authentication is to prove that something is genuine and authorization is to give permission to someone.…”