Simple Web Analytics

Category Description

Simple web analytics software gives website owners visibility into how visitors find and use their sites, without the complexity or privacy invasiveness of traditional analytics platforms. The core value proposition is a clear, immediately understandable view of traffic—page views, visitor counts, referral sources, and top pages—delivered through a single dashboard that requires no training to interpret. Products in this category deliberately limit the data they collect, operating without cookies or personal identifiers, which both satisfies privacy regulations (GDPR, CCPA, PECR) and eliminates the need for cookie consent banners on the tracked site. They are positioned explicitly as alternatives to heavyweight analytics suites, trading depth of analysis for speed of understanding and ease of compliance.

Example Implementations

Plausible Analytics
Fathom Analytics
Simple Analytics

Target Audience

The primary customers are small to mid-sized businesses, independent publishers, bloggers, freelancers, and digital agencies that need to understand website performance without investing in analytics expertise or infrastructure. Individual site owners typically interact with the dashboard directly and do not require separate analyst or engineer roles. Agencies frequently manage analytics on behalf of multiple client sites from a single account and need the ability to share or delegate access to specific sites without exposing unrelated client data. Privacy-conscious operators—particularly those serving EU users—are a core segment due to the regulatory advantages these tools provide.

Core Requirements

Tracking script installation: The system must provide a lightweight JavaScript snippet (or equivalent embed code) that site owners can add to any web page to begin collecting analytics data. The script must not use cookies or store personally identifiable information about visitors.
Core traffic metrics: The dashboard must display, at a minimum, the following metrics for any selected date range: total page views, unique visitor count, visit (session) count, bounce rate, and average visit duration.
Top pages report: The system must show a ranked list of the most-visited pages on the tracked site, including the page path and its page view count for the selected period.
Traffic sources report: The system must show where visitors are coming from, broken down by referrer domain. The display must distinguish between direct traffic, known search engines, social platforms, and other referral sources.
UTM parameter tracking: The system must automatically capture and display standard UTM parameters (source, medium, campaign, content, term) when they are present in inbound URLs, allowing users to measure the performance of tagged marketing campaigns and newsletter links.
Geographic breakdown: The system must display the countries from which visitors originate, ranked by visit volume.
Device and browser breakdown: The system must display a breakdown of visitor traffic by device type (desktop, mobile, tablet), browser, and operating system.
Real-time or near-real-time data: The dashboard must reflect visitor activity with a delay of no more than a few minutes. A live or current-visitor count indicator must be visible.
Custom date range selection: Users must be able to select arbitrary date ranges for all dashboard views, including preset options (today, last 7 days, last 30 days, this month, last month, year to date) and a custom date picker.
Custom event tracking: The system must support tracking of named custom events (e.g., button clicks, form submissions, file downloads, outbound link clicks) beyond page views. Events must be triggerable via a JavaScript API call. Event counts must appear in the dashboard alongside page view data.
Goal and conversion tracking: Users must be able to define goals based on page views or events and view a conversion rate or count for each goal within the dashboard. Goals must support at minimum single-step conversions (a visitor completed event X or reached page Y).
Bot and spam filtering: The system must automatically filter known bots, crawlers, and referral spam from reported metrics so that dashboard numbers reflect human visitor activity only.
Public/shared dashboard: Users must be able to make a site's analytics dashboard publicly accessible via a URL, without requiring the viewer to log in, so that data can be shared with clients, stakeholders, or the public.
Email reports: The system must support scheduling automated email summaries (at minimum weekly and monthly frequency) that can be sent to the account owner or additional recipients, covering the key metrics for one or more tracked sites.
Multi-site management: A single account must be able to track multiple distinct websites, with each site's data isolated from others. The dashboard must provide a way to switch between sites and view per-site metrics independently.
Data export: Users must be able to export their analytics data (page views, referrers, events, etc.) in a standard machine-readable format (e.g., CSV) for any selected date range.
Historical data import: The system must provide a mechanism to import historical analytics data from Google Analytics (Universal Analytics and/or GA4 properties) so that users migrating from Google Analytics can preserve continuity in their reporting.
IP and traffic filtering: Users must be able to exclude specific IP addresses (e.g., their own team's traffic) from being counted in analytics data, either by adding addresses to a block list or via a browser-based opt-out mechanism.

Cross-Cutting Requirements

Multi-tenancy: The application must support multiple independent organizations (tenants), each with isolated data.
Authentication: Users must authenticate with email/password at minimum. SSO and OAuth are not required.
Role-based authorization: The application must support at least three roles — administrator, manager, and standard user — with distinct permission levels appropriate to the category.
Data persistence: All user data must be persisted across sessions in a database.
Web application: The application must be accessible via a web browser. Native desktop or mobile applications are not required.
Concurrent users: The application must support multiple users within the same tenant using the application simultaneously without data corruption or loss.
Responsive design: The web application must be usable on both desktop and mobile browsers. A native mobile app is not required.

Scope Boundaries

Funnel analysis is not required. Multi-step conversion funnels (tracking a visitor through a sequence of pages or events) are present in some products (Plausible, Simple Analytics) but are a higher-order feature beyond single-step goal tracking.
Google Search Console integration is not required. Displaying search keyword data from GSC alongside analytics is offered by Plausible but not by Fathom or Simple Analytics.
Ecommerce revenue tracking is not required. Associating monetary values with events or transactions is a feature present in some products but is not table stakes for the category.
Uptime monitoring is not required. Some products include basic site uptime checks as a bonus feature; this is a distinct category of functionality.
Heatmaps and session recordings are not required. These require substantially different data collection and are typically a separate product category.
Self-hosting / on-premises deployment is not required. While some products offer a self-hosted community edition, the bounty target is a cloud-hosted SaaS application.
Ad-blocker bypass proxy is not required. Some products offer a feature to route the tracking script through the customer's own domain to evade ad blockers; this is an advanced infrastructure feature not shared by all products in the category.
A/B testing is not required. Splitting traffic between variants and comparing conversion rates belongs to a separate category of tooling.
User-level journey tracking is not required. These tools deliberately do not track individual users across sessions; cohort or individual-user analysis is out of scope.
Mobile app analytics (SDK) is not required. Tracking native iOS or Android app usage is outside the category scope; this is web analytics only.
Annotations / milestone markers on charts is not required. The ability to mark events (e.g., a site redesign) on time-series graphs is present in Fathom but not in all products.
White-labeling is not required. Rebranding the analytics UI for agency resale is an enterprise-tier feature not universally offered.
API access is not required at the core tier. A stats/data API is available in some products but is gated behind paid or higher-tier plans; it is not considered table stakes for the minimum viable implementation.
City or region-level geographic data is not required. Country-level geographic breakdown is required; drilling down to city or sub-national region is present in some products (Fathom) but not universal.
Data sampling avoidance need not be explicitly tested. All products in the category process 100% of hits without sampling; this is an implicit architectural characteristic, not a user-facing feature that needs its own requirement.
Retroactive event tracking is not required. Applying new event definitions to historical data after the fact is not consistently supported across the category.
Slack or webhook notifications are not required. Alerting integrations beyond email are present in some products as optional extras.
Third-party CMS plugins (WordPress, Ghost, etc.) are not required. Native plugin packages are convenience wrappers for the tracking script and are not a core system feature.

Spec Metadata

Version: 1.0
Created: 2026-03-15
Last Updated: 2026-03-15
Status: Draft