Overview

Pirsch was founded by Marvin Blum and co-founders in 2021 in Vienna, Austria, as a privacy-first lightweight web analytics brand. This document explores three deep angles: privacy compliance, self-hosting, and event tracking. Pirsch identifies sessions by hashing the IP address combined with the User-Agent, sets no cookies, and collects no personal identifiers, so it is GDPR, CCPA, and ePrivacy compliant out of the box without a cookie consent banner. Its core code is open source (GPL) and implemented in Go, fully self-hostable so data stays 100% in your hands.

On event tracking, Pirsch supports custom events and Goals configuration to track button clicks, form submissions, page scrolls, and other key interactions, linking events to business metrics for lightweight conversion analysis. Compared with the broader platform overview of the same-brand Pirsch platform, this article focuses on the practical depth of privacy architecture, self-hosted deployment, and event tracking, suiting teams with explicit data-sovereignty and compliance requirements.

Key Strengths

  • Cookieless privacy architecture: Session identification via IP hash + User-Agent, no cookies and no PII, GDPR/CCPA/ePrivacy compliant out of the box with no consent banner.
  • Fully self-hostable: Implemented in Go with open core (GPL), running on a single binary plus a database, with full control over storage, retention, and data egress.
  • Event and goal tracking: Custom events and Goals quantify key interactions such as clicks and form submissions for lightweight conversion analysis.
  • Server-side tracking: A JS-independent integration reports events and visits directly from the backend for no-JS and SPA scenarios.
  • Extremely lightweight: An about 4KB async script never blocks rendering, with minimal Core Web Vitals impact.

Product Ecosystem

Privacy Tracking Architecture

Cookieless session identification, IP hashing, and data-retention policies keep privacy built into the whole pipeline; see the GDPR compliance checklist for details.

Event Tracking and Goals

Report interactions via the custom event API and configure Goals to measure conversions, covering clicks, form submissions, and scroll depth; see the website API integration basics.

Self-Hosted Deployment

A Go single binary plus PostgreSQL with one-click Docker deployment keeps data fully under your control; see the Docker production deployment guide.

Server-Side Integration

Tracking without JavaScript reports visits and events directly from the backend for complete, accurate data, ideal for privacy- and accuracy-sensitive sites.

Cloud and Team Collaboration

Official cloud hosting supports multi-site management and team collaboration, with automatic weekly reports and dashboards for continuous trend insight.

Limitations

  • Focused on deep scenarios: Lacks heatmaps, session recordings, and A/B testing, so breadth is narrower than full-featured platforms.
  • No permanent free tier: Only a limited trial, so zero-budget sites must weigh cost.
  • Self-hosting needs ops skills: You maintain servers, databases, and upgrades yourself; non-technical teams should use the cloud.
  • Event instrumentation learning cost: Custom events and goals require manual setup with initial effort.

Use Cases

  • Teams with data-sovereignty requirements (Recommended ★★★★★): Self-hosting plus open source gives 100% data ownership, ideal for compliance-sensitive industries.
  • Privacy-sensitive websites (Recommended ★★★★★): Cookieless, no-PII architecture is GDPR compliant out of the box; see the GDPR compliance checklist.
  • Sites needing event and conversion tracking (Recommended ★★★★): Custom events and Goals cover key interaction analysis.
  • Performance- and SEO-focused sites (Recommended ★★★★): The about 4KB async script has minimal Core Web Vitals impact; see Core Web Vitals optimization.
  • Product teams needing deep behavioral analysis (Recommended ★★): Lacks funnels and heatmaps - consider Matomo.

Pricing

Plan Reference Price Key Features
Trial Free (limited) Evaluate core analytics, events, and goals
Business From about $8/month Event tracking, multi-site, API, team collaboration
Self-hosted Free (GPL) Full data control, requires your own server

Prices above are public reference figures; confirm on the official website. The self-hosted edition is open source and free, costing only server resources.

FAQ

  • What is the relationship between Pirsch and Pirsch-an? They belong to the same brand with consistent data; "Pirsch" covers the full platform while "Pirsch-an" explores privacy, self-hosting, and event-tracking depth - see the website analytics setup guide.

  • How do I use Pirsch event tracking? Report interactions through the custom event API, then configure Goals to measure conversions; see the website API integration basics.

  • What does Pirsch self-hosting require? A Linux server with Docker plus PostgreSQL; single-binary deployment completes in about 10 minutes with 100% data control - see the Docker production deployment guide.

  • Does Pirsch really need no cookies? Yes. It identifies sessions via IP hash + User-Agent, sets no cookies, and collects no PII, so no consent banner is needed and it is naturally GDPR compliant.

  • Is Pirsch suitable for Chinese websites? Cloud servers are in Europe, so script loading from mainland China may occasionally lag; for a mainland audience, self-host on a domestic server or use CDN acceleration; see overseas CDN acceleration for Chinese websites.