Session (web analytics)
Lua error in package.lua at line 80: module 'strict' not found. Sessions, or visits, is a unit of measurement in web analytics, capturing either a user's actions within a particular time period, or a user's actions in completing a particular task. As well as being directly useful as a metric within web analytics, sessions are also used in operational analytics and to provide personalised features, such as user-specific recommendations for other pages or items to view. These uses are dependent on session reconstruction - taking a series of user events and splitting the series into a set of sessions - which tends to use one of two classes of methodologies: time-oriented approaches, which use user inactivity as a signal to end a session and begin a new one, and navigation-based approaches, which divide requests into sessions based on an unbroken chain of hyperlinks between the requested pages.
Contents
Definition
The definition of "session" varies, particularly when applied to search engines.[1] Generally, a session is understood to consist of "a sequence of requests made by a single end-user during a visit to a particular site",[2] In the specific context of search engines, "sessions" and "query sessions" have multiple, contradictory and interchangeable definitions;[1] some researchers consider a session or query session to be all queries made by a user in a particular time period,[3] while others argue that sessions can be divided thematically, and a "session" is a series of queries with a consistent underlying user need, and that sessions terminate when that need does, even if the user continues searching for other purposes.[4][5]
Uses
Sessions can be used directly in web analytics, with sessions-per-user serving as a metric of website usage.[6][7] Other metrics used within research and applied web analytics include session length,[8] and user actions per session;[9] session length, particularly, is seen as a more accurate alternative to measuring page views.[10] With all of these metrics, and with sessions as a concept, the goal is to improve the website's usability, due to the substantial impact that usability has on website usage and operator profits.[11] Sessions are also used to provide personalised features such as user-specific recommendations and search term suggestions.[12]
Reconstructed sessions have also been used to measure total user input, including to measure the number of labour hours taken to construct Wikipedia.[13] Sessions are also used for operational analytics, including developing data anonymisation methodologies, identifying anomalies in networking,[14] and synthetic workload generation for testing servers with artificial traffic.[15] Some writers have argued that sessions are not appropriate as a workload characterisation metric within the context of e-commerce platforms, due to substantial variations in how different classes of user interact with that type of site. Instead, a state transition network is suggested.[16]
Session reconstruction
Essential to the use of sessions in web analytics is being able to identify them. This is known as "session reconstruction". Approaches to session reconstruction can be divided into two main categories: time-oriented, and navigation-oriented.[17]
Time-oriented approaches
Time-oriented approaches to session reconstruction look for a period of inactivity, or "inactivity threshold": a span of time between requests by a user. Once this period of inactivity is reached, the user is assumed to have left the site or stopped using the browser entirely, and the session is ended: further requests from the same user are considered a second session. A common value for the inactivity threshold is 30 minutes,[18][19] a well-established value sometimes described as the industry standard.[18] The utility of this value has been questioned: some researchers have argued that it produces artefacts around naturally long sessions,[20] and have experimented with other thresholds, including 10 and 60 minutes.[21] Despite this, Jones & Klinkner argue in a paper at the 2008 Conference on Information and Knowledge Management that, at least in relation to search data, "no time threshold is effective at identifying [sessions]".[22]
One alternative that has been proposed is using user-specific thresholds rather than a single, global threshold for the entire dataset.[23][24] This has the problem of assuming that the thresholds follow a bimodal distribution, and is not suitable for datasets that cover a long period of time.[20]
Navigation-oriented approaches exploit the structure of websites - specifically, the presence of hyperlinks and the tendency of users to navigate between pages on the same website by clicking on them, rather than typing the full URL into their browser.[17] One way of identifying sessions by looking at this data is to build a map of the website: if the user's first page can be identified, the "session" of actions lasts until they land on a page which cannot be accessed from any of the previously-accessed pages. This takes into account backtracking, where a user will retrace their steps before opening a new page.[25] A simpler approach, which does not take backtracking into account, is to simply require that the HTTP referer of each request be a page that is already in the session. If it is not, a new session is created.[26] This class of heuristics "exhibits very poor performance" on websites that contain framesets.[27]
References
- ↑ 1.0 1.1 Gayo-Avello 2009, p. 1824.
- ↑ Arlitt 2000, p. 2.
- ↑ Donato 2010, p. 324.
- ↑ Gayo-Avello 2009, p. 1825.
- ↑ Lam 2007, p. 147.
- ↑ Weischdel 2006, p. 464.
- ↑ Catledge 1995, p. 5.
- ↑ Jansen 2006, p. 10.
- ↑ Jansen 2000, p. 12.
- ↑ Khoo 2008, p. 377.
- ↑ Heer 2002, p. 243.
- ↑ Huang 2003, p. 638.
- ↑ Geiger 2014, p. 1.
- ↑ Meiss 2009, p. 177.
- ↑ Arlitt 2000, p. 8.
- ↑ Menascé 1999, p. 119.
- ↑ 17.0 17.1 Spiliopoulou 2003, p. 176.
- ↑ 18.0 18.1 Eickhoff 2014, p. 3.
- ↑ Ortega 2010, p. 332.
- ↑ 20.0 20.1 Mehrzadi 2012, p. 3.
- ↑ He 2002, p. 733.
- ↑ Jones 2008, p. 2.
- ↑ Murray 2006, p. 3.
- ↑ Mehrzadi 2012, p. 1.
- ↑ Cooley 1999, p. 19.
- ↑ Cooley 1999, p. 23.
- ↑ Berendt 2003, p. 179.
Bibliography
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
.svg){kind=link}