Kobbe

Product Introduction

1. Definition: Kobbe is a privacy-first, cookieless web analytics platform. Technically, it is a SaaS (Software-as-a-Service) application that collects, processes, and visualizes website traffic and user interaction data without using cookies or building persistent visitor profiles by default.
2. Core Value Proposition: It exists to provide website owners, marketers, and developers with essential traffic, conversion, and revenue insights while fundamentally respecting visitor privacy and simplifying GDPR compliance. Its primary value is delivering actionable analytics—tracking pages, sources, funnels, and custom events—without the privacy invasiveness of traditional analytics tools.

Main Features

1. Privacy-First, Cookieless Tracking: Kobbe's default tracking method does not use analytics cookies or localStorage to create persistent user IDs. It generates a daily rotating, non-reversible identifier from minimized request data (like a hashed combination of IP, User-Agent, and site-specific salt) to count daily unique visitors without profiling. The system discards raw IP addresses at the point of collection and does not store them in its application database.
2. Integrated Revenue Attribution: This feature connects payment platforms (Stripe, Paddle, Polar, Creem) via webhooks to attribute sales revenue directly to traffic sources and pages. It uses tab-scoped session attribution, passing a temporary identifier through checkout metadata rather than relying on long-lived cookies, aligning revenue data with pageview and source analytics on the same dashboard.
3. Funnel Analysis & Conversion Tracking: Users can build multi-step funnels from sequences of pageviews and custom events (e.g., Homepage -> Pricing Page -> Signup Click). The system calculates conversion rates and drop-off percentages at each step. It also auto-tracks conversions like form submissions, contact link clicks, and outbound link clicks, allowing the dashboard to be filtered by these goals.
4. Core Web Vitals & Performance Monitoring: When enabled, Kobbe collects real-user performance metrics (Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift, etc.) using the browser's Performance API. It displays percentile trends (p50, p75, p95), identifies slow pages, and breaks down performance by country, browser, and device directly within the analytics interface.
5. Search Console Integration & AI Traffic Grouping: This opt-in feature imports Google Search Console data (queries, clicks, impressions) into Kobbe dashboards. Additionally, its source analytics automatically group traffic from AI agents and platforms (like ChatGPT, Perplexity) into a dedicated "AI" category, providing clarity on modern referral sources.

Problems Solved

1. Pain Point: The complexity and legal risk of using traditional, cookie-based analytics (like Google Analytics) in privacy-conscious regions like the EU. Many businesses struggle with GDPR compliance, cookie banner requirements, and the ethical concerns of pervasive user tracking.
2. Target Audience: Website Owners & Marketers at small to medium-sized businesses who need clear traffic and conversion insights without legal overhead. SaaS Founders & Product Managers who require integrated revenue attribution to understand marketing ROI. Developers & Technical Teams who prioritize site performance, lightweight integration, and tools like a CLI/MCP server for workflow integration.
3. Use Cases: A European SaaS company needs to track sign-up funnels and revenue from marketing campaigns without implementing a complex cookie consent banner. A content publisher wants to understand which articles drive traffic and engagement while respecting visitor privacy preferences. A development team needs to monitor real-user Core Web Vitals alongside traffic spikes after a new deployment.

Unique Advantages

1. Differentiation: Unlike Google Analytics (complex, privacy-invasive) or simpler alternatives like Plausible/Fathom, Kobbe combines deep feature parity (funnels, revenue, performance) with a staunch privacy-by-default stance. It offers revenue attribution and advanced tracking as opt-in features rather than forcing a binary choice between simplicity and capability.
2. Key Innovation: The Model Context Protocol (MCP) integration within its CLI tool. The @kobbe/cli package can run as an MCP server, allowing AI-powered coding assistants (like Cursor, Claude Code, Windsurf) to directly query analytics data (traffic, pages, health) from within the code editor. This bridges analytics insights directly into the development workflow.

Frequently Asked Questions (FAQ)

1. Is Kobbe GDPR compliant and do I need a cookie banner? Kobbe is designed for GDPR compliance with cookieless tracking by default, no raw IP storage, and a provided Data Processing Addendum (DPA). For the core analytics, a cookie banner is typically not required as it uses no analytics cookies. However, a banner may still be needed if you use other cookie-based tools on your site or enable optional Kobbe features like cross-domain tracking.
2. How does Kobbe count unique visitors without cookies or fingerprints? Kobbe uses a privacy-conscious method that creates a daily-changing, non-reversible identifier. It combines and hashes minimized request data (like a truncated IP and user agent) with a site-specific salt. This identifier resets every 24 hours, preventing long-term cross-session tracking while allowing for accurate daily unique visitor counts.
3. Can I import my historical data from other analytics platforms like Plausible or Umami? Yes, Kobbe provides a data import feature that allows you to migrate historical analytics data from supported platforms including Plausible, Fathom, and Umami, ensuring you don't lose your trend history when switching.
4. What counts as an "event" towards my monthly limit? Your monthly event limit is a unified quota that includes: every pageview, every custom event (clicks, form submissions, etc.), every scroll visibility event (if enabled), and every accepted Web Vitals measurement. Funnel analysis uses these existing events and does not incur additional costs.
5. How does the revenue attribution work without cookies? Kobbe uses session-based attribution. When a visitor is on a site, a short-lived session identifier can be passed to a connected payment provider (e.g., Stripe) as metadata during checkout. When the payment webhook fires, Kobbe matches the revenue to the originating session's traffic source and page, all within a limited time window without needing a persistent cookie.