Session (web analytics)

From HandWiki
Revision as of 17:32, 6 February 2024 by Wincert (talk | contribs) (linkage)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

In web analytics, a session, or visit is a unit of measurement of a user's actions taken within a period of time or with regard to completion of a task. Sessions are also used in operational analytics and provision of user-specific recommendations. There are two primary methods used to define a session: time-oriented approaches based on continuity in user activity and navigation-based approaches based on continuity in a chain of requested pages.

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 context of search engines, "sessions" and "query sessions" have at least two definitions.[1] A session or query session may be all queries made by a user in a particular time period[3] or it may also be a series of queries or navigations with a consistent underlying user need.[4][5]

Uses

Sessions per user can be used as a measurement 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 is seen as a more accurate alternative to measuring page views.[10]

Reconstructed sessions have also been used to measure total user input, including to measure the number of labour hours taken to construct Wikipedia.[11] Sessions are also used for operational analytics, data anonymization, identifying networking anomalies, and synthetic workload generation for testing servers with artificial traffic.[12][13]

Session reconstruction

an illustration of the different criteria used by different session reconstruction approaches.

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.[14]

Time-oriented approaches

Time-oriented approaches to session reconstruction look for a set period of user inactivity commonly called an "inactivity threshold." 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 and sometimes described as the industry standard.[15][16] Some have argued that a threshold of 30 minutes produces artifacts around naturally long sessions and have experimented with other thresholds.[17][18] Others simply state: "no time threshold is effective at identifying [sessions]".[19]

One alternative that has been proposed is using user-specific thresholds rather than a single, global threshold for the entire dataset.[20][21] 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.[17]

Navigation-oriented approaches

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.[14] 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.[22] 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.[23] This class of heuristics "exhibits very poor performance" on websites that contain framesets.[24]

References

  1. ↑ 1.0 1.1 Gayo-Avello 2009, p. 1824.
  2. ↑ Arlitt 2000, p. 2.
  3. ↑ Donato, Bonchi & Chi 2010, p. 324.
  4. ↑ Gayo-Avello 2009, p. 1825.
  5. ↑ Lam, Russell & Tang 2007, p. 147.
  6. ↑ Weischdel & Huizingh 2006, p. 464.
  7. ↑ Catledge & Pitkow 1995, p. 5.
  8. ↑ Jansen & Spink 2006, p. 10.
  9. ↑ Jansen, Spink & Saracevic 2000, p. 12.
  10. ↑ Khoo et al. 2008, p. 377.
  11. ↑ Geiger & Halfaker 2014, p. 1.
  12. ↑ Meiss et al. 2009, p. 177.
  13. ↑ Arlitt 2000, p. 8.
  14. ↑ 14.0 14.1 Spiliopoulou et al. 2003, p. 176.
  15. ↑ Ortega & Aguillo 2010, p. 332.
  16. ↑ Eickhoff et al. 2014, p. 3.
  17. ↑ 17.0 17.1 Mehrzadi & Feitelson 2012, p. 3.
  18. ↑ He, Goker & Harper 2002, p. 733.
  19. ↑ Jones & Klinkner 2008, p. 2.
  20. ↑ Murray, Lin & Chowdhury 2006, p. 3.
  21. ↑ Mehrzadi & Feitelson 2012, p. 1.
  22. ↑ Cooley, Mobasher & Srivastava 1999, p. 19.
  23. ↑ Cooley, Mobasher & Srivastava 1999, p. 23.
  24. ↑ Berendt et al. 2003, p. 179.

Bibliography



Retrieved from "https://handwiki.org/wiki/index.php?title=Session_(web_analytics)&oldid=3369442"