Portfolio Site Visitor Analytics Summary Overlay

WHAT IT DOES

This script tracks visitor behavior on your site using browser events and page interactions, then displays a real-time analytics summary overlay. It captures session duration, scroll depth (percentage), click count, page views per session, time on page, device type (Desktop/Mobile/Tablet), screen resolution, referral source, and page load time. The dashboard shows current session metrics and historical summaries including total visits, unique days, average scroll depth, average clicks, and average pages per visit. A "top pages" section reveals which pages visitors engage with most. All data is stored per domain with timestamps, enabling trend analysis over time. Export the complete dataset as CSV or reset data for the current domain at any time.

WHERE IT RUNS

Works on any website—portfolio sites, blogs, landing pages, or any site you want to understand visitor behavior. The script uses standard browser APIs and event listeners, so it works without external services or third-party cookies. All tracking is privacy-first: data never leaves your browser.

HOW TO USE

The panel appears automatically when you visit a page. The "Visitor Analytics" section shows current session metrics—everything from how long you've been on the site to how far you've scrolled and how many pages you've viewed. The historical summary provides aggregate insights across all your visits: total visits, unique days, and averages for scroll depth, clicks, and pages per visit. Click "Track Visitor Data" to toggle tracking on/off—the script continues tracking even when the panel is closed. Use "Reset Data" to clear all stored analytics for the current domain. Click "Export CSV" to download a complete history of all tracked sessions with timestamps, metrics, and device information. Toggle individual metrics on/off in the "Display Metrics" section to customize which stats appear in the summary.

TECHNICAL MECHANISM: EVENT-DRIVEN SESSION TRACKING WITH LOCAL PERSISTENCE

The script initializes a VisitorTracker instance on page load, which generates a unique session ID and captures session start time. It then sets up event listeners for scroll (with 500ms debounce to avoid excessive writes), click (every click increments a counter), visibilitychange (to track time on page when the user leaves or returns), and beforeunload (final snapshot on exit). Scroll depth is calculated as the percentage of the maximum scrollable height relative to the viewport. Page views are tracked by monitoring URL changes (via setInterval every second) and maintaining a unique list of visited page paths. Every 30 seconds, or when key events occur, the tracker saves a snapshot to GM_setValue with all current metrics. Snapshots are stored as an array of entries per domain, capped at 500 to prevent storage bloat. Each entry includes timestamp, session ID, all tracked metrics, and the page path. When the panel renders, it aggregates these entries to compute historical averages, unique days, and top pages using frequency counting. The settings store per-metric display toggles and tracking enable state, all persisted via GM_setValue.

THE PANEL

The analytics overlay appears in a draggable, resizable panel that remembers its position per site. The current session section shows real-time stats with a clean metric grid. The historical summary displays aggregate data with a grid of key figures. Drag by the header to reposition, collapse to a compact icon with a click, and resize using the bottom-right corner. The panel snaps to screen edges for tidy placement and closes with the Escape key. All settings—tracking toggle, display metric toggles, and panel position—persist per website using GM_setValue, so your view returns exactly as you left it.

PLEASE NOTE

This script requires the free BotGentz extension to run. All visitor data is stored locally in your browser using GM_setValue—no data is transmitted to any server, and no third-party analytics services are used. The script tracks behavior only on pages where it's active and does not access other tabs or browser data. Scroll depth and click tracking rely on standard DOM events; performance may vary on heavily interactive pages. The history cap of 500 entries ensures storage remains reasonable; older entries are automatically removed when the limit is reached. Data is stored per domain, so switching domains resets the history view (though data for previous domains remains stored separately).