This privacy-focused approach natively measures traffic without cookies, relying entirely on anonymized metrics to guarantee compliance with privacy laws.
The platform is fundamentally built on a cookieless architecture, prioritizing user privacy over granular individual tracking. Instead of relying on persistent identifiers, it tracks unique visitors within a 24-hour window using a salted, rotating hash based on the user's IP address and user agent. This hash is permanently destroyed daily, meaning it is mathematically impossible to track a single user across multiple days or sessions. Because this approach strictly avoids processing Personally Identifiable Information (PII) as defined by GDPR, businesses are legally permitted to operate without intrusive cookie consent banners. This ensures a clean user experience and captures 100% of website traffic, rather than losing data from users who decline consent.
The tool supports basic custom events through lightweight JavaScript snippets, allowing users to track actions like file downloads and outbound clicks.
Beyond standard pageviews, the platform allows developers to track specific interactions by implementing simple JavaScript event tags. Users can define straightforward goals, such as 404 error occurrences, file downloads, outbound link clicks, or specific form submissions. The setup requires manually tagging HTML elements or configuring a Tag Manager to push the custom event name to the tracking script. While it effectively measures conversion volume for these specific goals, the capability is rudimentary. It does not support attaching multiple custom dimensions or metadata parameters to a single event, meaning analysts cannot extract deep context (e.g., tracking a purchase event but failing to pass the specific product ID or category).
The platform automatically blocks bot, crawler, and spam traffic at the server level, keeping dashboard metrics clean without user configuration.
To ensure reporting accuracy, the platform natively filters out known automated traffic before it ever reaches the user's dashboard. It relies on a continuously updated server-side exclusion list to identify and drop hits generated by search engine crawlers, common scraping tools, and referrer spam networks. This entirely automated background process is crucial for preventing artificially inflated traffic numbers, particularly for smaller websites where a single scraper can severely skew daily metrics. However, because it operates as an opaque, automated system, users do not have access to an interface for defining custom bot rules, whitelisting specific IP ranges for internal testing, or inspecting exactly what was blocked.
Users can build simple, linear conversion funnels to track step-by-step drop-off rates across predefined custom events and pageviews.
Despite its minimalist design, the platform provides a basic funnel analysis tool directly within its dashboard. Analysts can define a sequential path by combining standard pageviews and custom events, allowing them to visualize the exact drop-off rate between each step (e.g., Landing Page -> Add to Cart -> Purchase). This is highly useful for identifying where users abandon a standard conversion flow. However, the functionality is strictly limited to linear, closed funnels; users cannot create complex, multi-directional journey analyses or apply deep audience segmentation to see how different user cohorts navigate the funnel. It serves the needs of basic conversion tracking but lacks the depth required by dedicated product teams.
The platform includes a basic flow report that shows the next page visitors navigate to after landing on a specific URL.
The platform offers a lightweight pathing feature designed to help users understand immediate site navigation. By clicking on any specific page within the Top Pages report, analysts can access an "Entry Pages" or "Exit Pages" view to see the immediate next steps visitors took. While this provides a quick snapshot of user flow and common drop-off points from a specific landing page, it is not a full-scale journey mapping tool. It lacks the complex, tree-graph visualizations needed to track a user across five or six sequential steps, making it difficult to analyze deep, convoluted navigation loops typical of large enterprise websites or applications.
The dashboard prominently features a real-time visitor count, showing currently active users and the specific pages they are viewing.
The primary dashboard includes a live monitoring widget that constantly updates to show the exact number of active visitors currently on the website. Below the counter, it displays a breakdown of the specific URLs being viewed, the real-time geographic location of the visitors, and their referring traffic sources. This immediate, unsampled feedback loop is highly valuable for verifying that the tracking script is working, monitoring the instant impact of a newly sent newsletter, or tracking viral social media traffic. However, it is strictly a surface-level monitoring tool; analysts cannot drill down into specific live sessions or debug real-time event firing.
E-commerce tracking is supported by assigning custom revenue values to specific conversion goals, providing a high-level overview of campaign ROI.
The platform handles e-commerce measurement through a simplified revenue tracking mechanism rather than a complex, dedicated retail schema. Users can assign dynamic or static monetary values to specific custom events (like an 'Order Completed' goal). The dashboard then aggregates these values to display total generated revenue and calculates standard ROI metrics against campaign sources. This provides an excellent, high-level overview of which marketing channels are driving the most financial value. However, it completely lacks granular e-commerce reporting; it cannot natively track individual product views, cart abandonment rates, or calculate metrics like Average Order Value (AOV) across multiple items in a single transaction.
Users can deploy the tracking script via a reverse proxy to bypass client-side ad blockers and ensure more complete data collection.
To combat the increasing use of aggressive browser ad-blockers that often incorrectly block privacy-first analytics scripts, the platform officially supports reverse proxy deployment. Developers can configure their own server infrastructure (like Nginx, Apache, or Cloudflare) to route the analytics tracking requests through a first-party subdomain (e.g., stats.yourdomain.com). This makes the tracking requests appear as essential first-party traffic, significantly reducing the likelihood of being blocked and ensuring a much higher degree of data accuracy. While highly effective, implementing a reverse proxy requires technical knowledge and direct access to server configuration, making it inaccessible for non-technical marketers.
The platform is architected explicitly for absolute privacy compliance, requiring no cookie banners and storing no personally identifiable information.
Compliance is the platform's strongest competitive advantage. It is open-source, European-hosted, and designed from the ground up to never collect, store, or process Personally Identifiable Information (PII). By relying strictly on ephemeral hashing instead of persistent cookies, it fundamentally bypasses the legal requirement for GDPR, ePrivacy, and CCPA consent banners. This provides businesses with a risk-free analytics solution that respects user privacy while still capturing accurate, aggregate data on 100% of website visitors. For organizations primarily concerned with legal compliance and minimizing their digital footprint, this architectural choice makes it a vastly superior alternative to traditional, invasive tracking platforms.
Users can programmatically extract their aggregated dashboard data using a robust Stats API for custom reporting.
The platform provides automated access to its data primarily through a comprehensive Stats API. Developers can use this API to query specific metrics, filter by timeframes or dimensions, and extract the aggregated data for use in custom internal dashboards, client reports, or data warehouses. Additionally, casual users can download basic CSV exports directly from the dashboard UI. However, due to the platform's strict privacy architecture, there is no "raw, user-level" data to export. Because individual user journeys are never persistently tracked or stored, all exported data is inherently pre-aggregated, limiting the ability of data science teams to build complex, retrospective attribution models.
The platform retains its anonymized, aggregated reporting data indefinitely without forcing users into restrictive historical limits.
Because the platform exclusively processes and stores anonymized, aggregated data, it does not run afoul of the strict data minimization rules mandated by global privacy laws. Consequently, the vendor does not impose arbitrary data retention limits on active accounts. Users can access their complete historical data indefinitely, allowing for accurate year-over-year comparisons and long-term trend analysis. This is a significant advantage over complex enterprise platforms that often restrict historical access to granular data after 2 or 14 months to save on server storage costs or to force users into premium subscription tiers.
nan
nan