Skip to content Skip to main navigation Skip to footer

Tag: Sessions

Understanding Behavior Analytics: Hits, Visits, and Sessions

In Behavior analytics, “Hits,” “Visits,” and “Sessions” are fundamental metrics that build on each other. Here’s an explanation that reflects their interrelated nature:


  • Definition: A ‘Hit’ refers to any record stored for a unique user interaction with a website.
  • Details: This includes every element (like images, JavaScript files, Cascading Style Sheets (CSS), embedded objects) loaded or interacted with on a webpage. Each element counts as a separate ‘Hit’. Notably, these elements might not always be loaded from the website’s primary domain; often, they are served from another domain, such as a Content Delivery Network (CDN), which is common for media files and scripts.
  • Example: Loading a single web page that includes five images and two JavaScript files from a CDN, along with one CSS file from the primary domain, would result in eight hits.


  • Definition: A ‘Visit’ represents each individual interaction a user has while on a website or online application.
  • Details: This is measured by user actions that lead to new page loads or significant interactions within the same page. Each distinct action, like a click leading to a new page or a notable change on the current page, is counted as a separate visit.
  • Example: A user clicks on a link to open a new page, and then another link to visit a different section, with each action counted as an individual visit.


  • Definition: A ‘Session’ encompasses a series of visits by a user within a specific timeframe.
  • Details: It begins when a user first accesses a website or application and ends after a period of inactivity or user logout. A session includes all visits (and therefore, all hits) made during that period.
  • Example: A user visits a website, browsing through different pages (each page view is a visit), and then logs into an online application. All the activities, including website browsing and interactions within the online application until the user logs out or becomes inactive, constitute a single session.


The Session Settings Screen allows you to customize, run, and analyze your session algorithm against specific log file configurations and defined timespans. Built with adaptability in mind, you can modify session algorithm parameters to better align with the unique requirements of any customer environment.

Go to Settings – Reports – Sessions. The Session screen is displayed

Session Analyzer

  1. To manually run the session algorithm go to the Session Analyzer section
  2. Select Log File Configuration: Use the dropdown to select the log files you’d like to include in your analysis.
  3. Define Your Timespan: Using the calendar tool, select your desired start and end dates and times.
  4. Press the button labeled ‘Analyze’ on the screen to initiate the session algorithm.

Session Analyzer Configuration

If you’re familiar with the specifics of the session algorithm and wish to fine-tune it, use the input boxes to adjust the default parameters. If unsure, it’s recommended to consult the definition below or contact our support team for assistance.

  1. To override the system defaults use the below input boxes to adjust the default parameters.
  2. Press the button labeled ‘Update Configuration’ to apply Session algorithm parameter changes.

Session Parameter Definitions

  • Minimum Duration (minutes): The least amount of continuous Web activity to a particular Application/Site required to constitute a session.
  • Inactivity Cutoff (minutes): The amount of time since the last activity to an Application/Site for a session to be considered complete. Future activity will start a new Session.
  • Minimum Session Hit Count: The minimum amount of Web activity (log hits) required to each Application/Site for the activity to constitute a Session.
  • Maximum Session Duration(hours): A hard limit in hours for acitvity to single Application/Site.
  • Required Browser User-Agent: When enabled Log records containing known browser types will be analyzed.
    • Notes:
      • Keeping the checkbox enabled allows for a more refined and relevant session analysis by focusing on known browser types.
      • Users who wish to view all log records, regardless of browser type, should disable the checkbox. However, please note that disabling this option will affect the accuracy of the session analysis.
      • Disabling this checkbox might be necessary if SSL inspection is not enabled on your firewall. Without SSL inspection, the session analysis may not only be inaccurate but could also return without any results because the user agent field would be empty.