For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
  • Getting Started
    • Overview
    • Best practices
  • Sightline Cyberfraud Defense
    • About Sightline Cyberfraud Defense
    • Getting Started
    • What's different in Sightline Cyberfraud Defense
    • Sensor changelog
    • About the Overview Dashboard
    • Glossary
  • AgenticTrust
    • Getting started with AgenticTrust
    • AI Agents Monitoring Dashboard
    • AI Visitors Overview Dashboard
    • Manage AI Agent Permissions
    • Agentic Activity Priority
    • Agent Trust Levels
  • Account Defender
    • Account Defender Overview
    • Use Cases
    • Prerequisites
    • Getting Started with Account Defender
    • Optimizing Account Defender Detection
    • Validating Account Defender Integration
    • Risk Triggers
    • About Network Events
    • Troubleshooting
  • Bot Defender
    • Bot Defender Overview
    • Detection
    • Bot Defender Policy Settings
        • Explore the data
        • Navigate the dashboard
        • Dashboard customization
      • Bot Characteristics
      • Investigate the Data
      • Data Export
    • Footprint
  • Credential Intelligence
    • Credential Intelligence Overview
    • How to Access the Breached Flag
    • Credential Intelligence FAQ
    • Credential Intelligence Dashboard
  • Code Defender
    • Code Defender Introduction
    • Getting Started with Code Defender
    • Code Defender Glossary
    • Website Risk Analyzer
  • Platform
    • Account settings
    • Manage users
    • Role permissions
    • Enforcer configurations
    • Page Type Mapping
  • Client-Side Integration
    • JavaScript tag
    • Improving first page performance
    • Use of cookies & web storage
    • Advanced client integration
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Data Retention
  • Data Type
  • Pageviews (analytic and marketing tools)
  • HUMAN Pageviews
  • Requests
  • Requests vs. Pageviews
Bot DefenderReporting and AnalysisGeneral Dashboard

Explore the Data

Was this page helpful?
Previous

Navigate the Dashboard

Next
Built with

Data Retention

Portal SectionMaximum Data Retention
Page View Reports24 hours
Investigation Page (when using Search filters)14 days
Captcha Report14 days
All “Tops” Tables14 days (Investigation tab), 120 days (Dashboard tab)
Top Incidents (only)14 months
All Graphs Over Time14 months

The dashboard’s default time range is the Last 1 hour or the last time range selected

Data Type

HUMAN Bot Defender Portal data is Requests based. Using Requests in the Dashboard and Investigation tabs allows HUMAN to:

  • Provide full visibility into the website’s traffic and provide more accurate information
  • Enable end-to-end investigation capabilities across multiple tools and systems

Previously (in the legacy classic Portal) traffic was calculated based on an aggregation of Pageviews and Requests, bundled together to a single HUMAN Pageview.

Pageviews (analytic and marketing tools)

A pageview is an instance of a website page being loaded (or reloaded) in a browser. Google Analytics and other marketing tools use this metric to track website traffic. Pageviews rely on running Javascript. When a website is accessed, the visitor’s browser runs Javascript, and a request with the visitor’s information is sent to the website’s servers.

HUMAN Pageviews

A certain portion of websites’ traffic can originate from automated tools that don’t run Javascript. In order to take into account non-Javascript traffic, HUMAN created HUMAN Pageviews. This is an aggregation of Javascript pageviews and server requests bundled together as a single HUMAN  Pageview. This metric is different than the common pageview metric being used by analytics and marketing tools since they are based on Javascript only.

For some customers, the Account Usage History, in Platform Settings -> Usage, will show Page Views. This is aligned with the user’s agreed billing metric

Requests

Requests measure how much traffic a server handles, including traffic from bots not running Javascript. Calls to a server can include page downloads, comments on a thread, “likes”, graphic or image views, or any other action on a website. Therefore the number of Requests is not identical to the number of pageviews, but it correlates to it. The request metric cannot be used by Javascript-based services such as common analytics and marketing tools since they don’t have access to the server traffic (they rely on Javascript only).

Requests vs. Pageviews

  • Requests include visitors that don’t execute Javascript, including bots and crawlers. This is unlike pageviews, that only count visitors who run Javascript.
  • Requests are used in industry web server metrics (e.g hits per second), calculating the load on the server. This is how developers, devOps and QA engineers can discover and analyze real-time daily usage, traffic spikes and potential attacks. This is unlike pageviews that only count indication of a page load, but not the number of actual requests to the website’s server.
  • Requests provide full visibility and analysis capabilities on the traffic. This is unlike pageviews that don’t count visitors that don’t run Javascript and requests that don’t require the loading of a new page.

For more information, contact HUMAN Support