Pirsch

Pirsch is a web analytics platform built on a single premise: most sites do not need to identify individual visitors to understand their traffic, and if you stop trying, most of the privacy problem disappears. It tracks pageviews, sources, pages, devices, locations and custom events without setting cookies and without writing to local storage. The practical consequence is that in most jurisdictions a site using Pirsch does not need a consent banner for analytics, which removes a layer of friction, a category of legal risk and a chunk of JavaScript from the page.

The mechanism is worth understanding, because it is what makes the compliance claim credible. Instead of a persistent identifier stored on the visitor's device, Pirsch derives a short-lived fingerprint from non-identifying request characteristics combined with a daily-rotating salt, which allows it to count a unique visitor within a day without being able to track that person across days or across sites. Nothing is written to the browser. Because the approach does not use cookies or local storage, it falls outside the storage-and-retrieval provisions that drive consent requirements under European rules, and the vendor hosts in the European Union with data processing agreements available. This is not a legal opinion and a serious organisation should still have its own counsel review the position for its jurisdictions, but the architecture is genuinely designed for the constraint rather than retrofitted to it.

The tracking script is small, on the order of a kilobyte, and it is loaded asynchronously so it does not block rendering. For teams working on Core Web Vitals, this is a real advantage: a full-featured analytics or tag-manager stack can add hundreds of kilobytes and several hundred milliseconds of main-thread work, and swapping it for a lightweight script shows up in field data. Pirsch also supports server-side tracking, where events are sent from your backend rather than the browser, which is useful for single-page applications, for tracking behind ad blockers, and for sites that want no client-side analytics script at all.

Feature coverage is deliberately close to what a standard analytics report contains. Real-time and historical dashboards show visitors, pageviews, sessions, bounce rate and visit duration. Acquisition reporting covers referrers, utm campaign parameters, landing pages and, where available, organic search keywords. Content reporting ranks pages and shows scroll depth and time on page. Audience reporting covers country, city, language, device, browser, operating system and screen size. Conversion features include custom events with optional numeric values, funnels that measure progression through defined steps, and goal tracking. Data can be filtered by any dimension and by date range, dashboards can be shared publicly or privately, and retention settings control how long raw data is kept.

The API and integrations round it out. A read-only REST API exposes the same data the dashboard shows, so reports can be pulled into internal dashboards, spreadsheets or a data warehouse. There are also integrations and community libraries for common platforms and frameworks, and the ability to send events from the backend means almost any system can feed data in without a browser.

Against competitors, Pirsch belongs to the lightweight privacy-first analytics category alongside Plausible and Fathom, both of which are established, both open-source or self-hostable in Plausible's case, and both with the same cookieless architecture and the same value proposition. The differences between the three are mostly a matter of feature emphasis, pricing structure, interface taste and self-hosting options; Plausible has the largest community and the most mature self-hosted distribution, Fathom emphasises simplicity and compliance marketing, and Pirsch offers a somewhat broader feature set including funnels and server-side tracking at a comparable price. Google Analytics 4 remains free and vastly more capable in attribution modelling, audience building, cross-device tracking, BigQuery export and advertising integration, and it is the incumbent that these tools exist to replace for sites that do not need any of that. Matomo is the self-hosted full-featured alternative for organisations that want Google-Analytics-level capability under their own control. Cloudflare Web Analytics is free and derived from network logs. Simple Analytics and GoatCounter occupy similar niches. Pirsch's position within the group is a full-featured, developer-friendly option with funnels, an API, server-side tracking and EU hosting.

Pricing is subscription-based and paid, with a free trial rather than a permanent free tier. Plans are priced primarily by monthly pageviews and by the number of sites or projects included, with higher tiers raising those limits and unlocking additional features such as funnels, longer data retention, more team members, higher API rate limits and priority support. Annual billing is discounted. The pageview-based model means cost tracks traffic rather than team size, which is predictable for a growing site but requires attention if traffic spikes. Because the free trial is time-limited, evaluating Pirsch on a real property requires either paying or accepting a short window. Current figures are published on the vendor pricing page.

The limitations are inherent to the approach and should be understood before adoption. There is no cross-day or cross-device user identification, so you cannot build cohorts of returning individuals, track a user journey spanning multiple days, or attribute a conversion to a specific person. There is no advertising integration, no audience export to ad platforms, no attribution modelling across channels and no campaign-level user paths. Organic search keyword data is limited because search engines strip it. Bot filtering and traffic quality assessment are less sophisticated than in enterprise suites. Self-hosting is possible in some configurations but is not the mainstream deployment path, unlike Plausible. And if your organisation genuinely needs the depth of Google Analytics 4 or a warehouse-native analytics stack, a lightweight tool is not a substitute; it is a different product for a different requirement.

Pirsch fits marketing sites, blogs, documentation, portfolios, small and medium ecommerce properties, agencies managing multiple client sites, and any team in or selling to the European Union for which a consent banner is an avoidable cost. It fits developers who care about page weight and want an API. It fits organisations that want to stop thinking about analytics compliance. It does not fit performance marketing teams running paid acquisition who need attribution and audience activation, product teams running cohort analysis and retention modelling, large enterprises requiring warehouse export and governance, or anyone whose reporting depends on identifying individual users across sessions.

In the closing comparison, choose Pirsch when you want a full-featured cookieless analytics platform with funnels, an API and EU hosting and are willing to pay for it. Choose Plausible when you want the largest community and a proven self-hosted option. Choose Fathom when maximum simplicity is the goal. Choose Google Analytics 4 when you need attribution, advertising integration and cross-device analysis and can absorb the consent and performance costs. Choose Matomo when you need full capability under your own control. For a typical content, marketing or small commerce site that wants honest traffic numbers without a consent banner and without a two-megabyte script, Pirsch is one of the strongest choices in its category.