Private analytics without the usual tracking baggage
I joined cookie-free traffic measurement, campaigns, goals, journeys, crawler visibility, and search-console data in one self-hosted operator view.
75-operation OpenAPI contract · real tracker, API, UI, and browser tests
How the pieces connect
- Cookie-free event
- Privacy-bounded visitor-day
- Campaigns, goals, and journeys
- Search and crawler imports
- Operator reports
The job
Traffic analytics and search visibility usually live in separate tools, while AI and search crawlers disappear into server logs. The useful view is the relationship between them.
The hard part
Measure enough to make decisions without browser storage, persistent person profiles, raw IP retention, or inflated identity claims.
How I built it
- Use no browser storage for the tracker and do not persist raw IP addresses or full user agents.
- Report visitor-days instead of pretending a self-hosted identifier follows one person forever.
- Keep campaign, goal, journey, referrer, crawler, and webmaster observations in one inspectable model.
- Include backups, system metrics, and packaging because analytics is an operating system, not only a chart.
What I verified
- Pageviews, visitor-days, campaigns, goals, journeys, and referrers
- Search-engine and AI-crawler visibility
- Google Search Console and Bing integrations
- 75-operation OpenAPI contract with API, UI, tracker, and browser tests
Current state: Visitors are grouped per day rather than tracked as permanent people. High-volume production limits are not yet published.