✦ Cookieless analytics, built around daily rotating IDs
☰
All featuresWeb AnalyticsCustom EventsCookieless AnalyticsIntegrationsPricingDocumentationComparisonsFree toolsBlogGlossary
PLATFORM

One analytics model for ingestion and reporting

Ingest browser events through the collector and retrieve project-scoped reports through the authenticated API. Keep events and profiles in Tinybird and application settings in Supabase.

How to install ↗

Keep write and read credentials separate

The public SDK write key authorizes collection for a registered site. Authenticated report reads use the application’s access controls. MCP has its own private project key; these credentials are not interchangeable.

Reuse the event envelope

Page and track payloads include a message ID, event timestamp, context, scalar properties, and optional user ID. The collector resolves the project from the write key and derives anonymous identity instead of trusting a browser-supplied visitor ID.

Query the same definitions

KPI, time-series, pages, sources, activity, profile, funnel, and Web Vitals endpoints are implemented over Tinybird. Date ranges and filters should match the dashboard. SQL investigation is a separate bounded read path.

Operate your own pipeline

The app repository contains the API, worker, queue infrastructure, and Tinybird project. There is not yet a general public API-key REST contract for every hosted report. Self-hosted operators must configure origins, credentials, and resource limits.

Frequently asked questions

Can I read analytics with the SDK write key?

No. The SDK write key is for ingestion only.

Where does analytics data live?

Tinybird stores analytics events, materialized profiles, and replay chunks. Supabase holds application state.

Is there a stable public read API for every report?

The app API endpoints exist, but hosted external REST authentication and rate-limit documentation are still being finalized. MCP provides the documented project-key read path.

Start with a clear measurement model.

Install the SDK, then explore traffic and product activity with the same definitions.