Analytics
Kitbase provides privacy-friendly web analytics without cookies. Track page views, sessions, users, and custom events from a unified dashboard.
Overview
Once you have the Kitbase SDK installed and initialized, analytics data flows into a single dashboard where you can monitor traffic, engagement, and conversions in real time. There are no cookies involved -- Kitbase relies on localStorage for anonymous identification and server-side enrichment for device, browser, and location data.
Dashboard Metrics
The analytics dashboard surfaces six core metrics at a glance:
| Metric | Description |
|---|---|
| Total Events | The total number of events received in the selected time range |
| Unique Users | Distinct anonymous or identified users who triggered at least one event |
| Sessions | Total user sessions (a session ends after 30 minutes of inactivity) |
| Page Views | Total screen_view events recorded |
| Bounce Rate | Percentage of single-page sessions out of total sessions |
| Session Duration | Average time between a session's first event and its last activity |
TIP
Bounce rate and session duration are computed server-side, so they remain accurate even if users close the tab without triggering a final event.
Breakdowns
Data in the dashboard can be broken down by a variety of dimensions to help you understand your audience.
Event
| Dimension | Description |
|---|---|
| Event name | Group metrics by the name of the event (e.g., screen_view, Purchase Completed) |
Geographic
| Dimension | Source |
|---|---|
| Country | IP geolocation (server-side) |
| Region | IP geolocation (server-side) |
| City | IP geolocation (server-side) |
Device & Browser
| Dimension | Source |
|---|---|
| Browser | User agent parsing |
| Browser version | User agent parsing |
| OS | User agent parsing |
| OS version | User agent parsing |
| Device type | Desktop, mobile, or tablet (user agent parsing) |
| Brand | Device manufacturer (e.g., Apple, Samsung) |
| Model | Device model (e.g., iPhone 15, Pixel 8) |
Pages & Traffic
| Dimension | Description |
|---|---|
| Page path | The URL path of the page where the event occurred |
| Referrer | The referring URL that brought the user to your site |
| UTM source | The utm_source query parameter |
| UTM medium | The utm_medium query parameter |
| UTM campaign | The utm_campaign query parameter |
Timeline
View event trends over time by selecting a time interval. The timeline chart adjusts automatically based on your date range, but you can also set the interval manually:
| Interval | Best for |
|---|---|
| Hourly | Monitoring traffic within a single day |
| Daily | Viewing trends over days or weeks |
| Weekly | Comparing week-over-week performance |
| Monthly | Long-term trend analysis |
Filtering
Use the filter bar at the top of the dashboard to narrow down the data you see. Filters can be combined for precise analysis.
Available Filters
| Filter | Description |
|---|---|
| Environment | Separate production from staging or development data |
| Date range | Select a start and end date for the data window |
| Event name | Show only specific events (e.g., screen_view, Purchase Completed) |
| Channel | Filter by event channel (e.g., __analytics, payments) |
| Browser | Filter by browser name or version |
| Country | Filter by geographic location |
| Device type | Filter by desktop, mobile, or tablet |
| OS | Filter by operating system |
| Referrer | Filter by traffic source |
| UTM parameters | Filter by UTM source, medium, or campaign |
Any dimension available in the breakdown view can also be used as a filter.
Data Enrichment
When an event arrives at the Kitbase server, it is enriched with additional context before being stored. This enrichment happens entirely server-side.
| Raw Data | Enriched Result |
|---|---|
| User agent string | Device type, browser name and version, OS name and version, brand, and model |
| IP address | Country, region, and city (the IP itself is not stored unless explicitly configured) |
| Page URL | Path and referrer |
| URL query parameters | UTM source, medium, and campaign |
IP Handling
By default, Kitbase does not persist raw IP addresses. Geolocation is resolved at ingestion time and only the resulting country, region, and city are stored.
Privacy
Kitbase is designed to be privacy-friendly by default:
- No cookies -- Analytics tracking does not use cookies of any kind.
- localStorage for anonymous ID -- A UUID is stored in localStorage to identify returning visitors. This can be disabled by setting
storage: nullin the SDK config. - No raw IP storage -- IP addresses are resolved to country, region, and city at ingestion time. The raw IP itself is not stored.
- Bot filtering -- Automated traffic from crawlers, headless browsers, and testing tools is filtered out automatically.