Privacy note: Location is derived from the visitor's IP address at ingestion and stored at city level. The IP address itself is not stored, and no precise location tracking is performed.

Powering the map view

The geographic data displayed on maps and in regional breakdowns is typically derived from the user's IP address at the beginning of a session. Pageviews and sessions are tracked automatically; there is no separate SDK option to enable them. See SDK configuration for the optional controls.

Technology stack analysis

Understand your audience's technical environment:

Device analytics

Device types

Categories:

Desktop: Traditional computers
Mobile: Smartphones and mobile devices
Tablet: Tablets and large mobile devices Metrics:
Visitor distribution
Device-specific performance
User behavior patterns

Browser information

Data included:

Browser names and versions
Market share among your visitors
Browser-specific performance data
Compatibility insights

Operating system insights

Platform distribution:

macOS: Apple computers
Windows: Microsoft Windows
Linux: Linux distributions
iOS: Apple mobile devices
Android: Android devices

Strategic benefits:

Optimize for popular platforms
Debug platform-specific issues
Understand technical demographics
Plan feature compatibility

Cross-platform considerations: Ensure your website works well across all popular platforms used by your audience.

Custom events analytics

Track and analyze your business-specific events with detailed property breakdowns:

Populating this section

The analytics, breakdowns, and examples shown here are populated by the custom events you actively send from your application using the db.track('your_event_name', {your_properties}) method. The more relevant and well-structured custom events you track, the more insightful this section will become. For detailed guidance on how to implement custom event tracking, please refer to the Tracker helpers guide.

Enhanced event interface

Tree-structure analytics:

Event level: Overall event metrics and performance
Property categories: Organized property groupings with counts
Property values: Individual values with percentage distributions
Visual hierarchy: Color-coded dots and professional typography

Event display features:

Event badges: Blue dots for main events
Count displays: Total events and unique users
Share percentages: Relative event frequency
Occurrence tracking: First and last event timestamps

Event examples

E-commerce events

{
  "event": "purchase_completed",
  "properties": {
    "product_id": "prod_123",
    "revenue": 29.99,
    "currency": "USD",
    "category": "software"
  }
}

Engagement events

{
  "event": "feature_used",
  "properties": {
    "feature": "export_data",
    "plan": "pro",
    "usage_count": 5
  }
}

Advanced filtering and segmentation

Slice and dice your data for specific insights:

Available filters

Segmentation strategies

User behavior segments

High-engagement users: Multiple page visits
Quick browsers: Short session durations
Deep readers: Long time on page
Mobile-first users: Primarily mobile traffic

Technical segments

Performance impact: Fast vs slow connections
Browser compatibility: Modern vs legacy browsers
Device capabilities: Screen size and features
Platform preferences: Operating system usage

Performance monitoring

Monitor your website's technical health and user experience:

Enabling performance data

The performance metrics, including Core Web Vitals, are populated when you enable trackWebVitals={true} in your SDK configuration. This allows the SDK to collect Core Web Vitals from the visitor's browser.

Core Web Vitals

Essential performance metrics:

LCP (Largest Contentful Paint)

Good: ≤ 2.5 seconds Measures loading performance. Time until the largest content element is rendered.

INP (Interaction to Next Paint)

Good: ≤ 200 milliseconds Measures responsiveness across user interactions during the page visit.

CLS (Cumulative Layout Shift)

Good: ≤ 0.1 Measures visual stability. Sum of all unexpected layout shift scores.

FCP (First Contentful Paint)

Good: ≤ 1.8 seconds Time until first content element is rendered on screen.

Performance analytics

Detailed performance data:

Load time distribution: Histogram of page load times
Performance by page: Page-specific metrics
Performance trends: Changes over time
Mobile vs desktop: Device-specific performance

Performance tip: Use the performance data to identify slow pages and prioritize optimization efforts where they'll have the biggest impact.

Error tracking and debugging

Monitor and resolve issues affecting your users:

Enabling error data collection

Error tracking requires the Hobby plan or higher. To populate the error tracking sections of the dashboard, ensure you have trackErrors={true} enabled in your SDK configuration. This will automatically capture unhandled JavaScript errors and promise rejections. For more detailed context on specific handled errors, you can manually send error events using db.track('error', {/* custom properties */}) as described in the Tracker helpers guide.

JavaScript error analytics

Error resolution workflow

Identify: Spot errors in the dashboard
Analyze: Review stack traces and context
Prioritize: Focus on high-frequency errors
Fix: Implement solutions
Verify: Monitor error reduction

Error impact: JavaScript errors can significantly impact user experience. Regular monitoring helps maintain site reliability.

Mobile dashboard experience

Access your analytics on any device:

Mobile features

Optimized mobile interface:

Touch-friendly charts and graphs
Responsive table layouts
Mobile-optimized filtering
Fast loading on mobile networks

Mobile-specific insights:

Mobile vs desktop performance comparison
Mobile user behavior patterns
Mobile-specific error tracking
Mobile Core Web Vitals monitoring

Data export and integration

Get your data where you need it:

Export options

Data export

Download your data as JSON or CSV via Website Settings > Data Export.

API access

Programmatic access to your analytics data via REST API.

Investigations in Slack

Send actionable investigations to the Slack channels configured for your organization after each daily or weekly run. Replies are included clarifications using the same investigation's saved evidence. Start a new question or fresh analysis explicitly in the dashboard.

Uptime monitor alerts can be delivered to a webhook destination, but there is no outbound webhook streaming for analytics data.

Getting the most from your dashboard

Best practices

Regular monitoring: Check your dashboard weekly to spot trends and issues early.

Daily tasks:

Check overall visitor trends
Monitor error reports
Review performance metrics
Track custom events

Weekly analysis:

Compare week-over-week growth
Analyze geographic trends
Review device usage patterns
Evaluate traffic sources

Monthly reviews:

Assess monthly growth trends
Review goal achievement
Analyze top-performing content
Plan optimization strategies

Dashboard troubleshooting

Common issues

If you are choosing a reporting workflow, compare the analytics dashboard options. When a report needs an action you do not yet record, use the custom event guide to plan the missing measurement.

To bring supported exports from another tool, follow the historical import guide. Preview the source format and dates first, and review the limits on reconstructed aggregate reports before replacing an earlier import.

SDK reference

Complete SDK configuration and tracking options

Custom events

Implement custom event tracking for business insights

Performance tracking

Optimize your website's performance metrics

Security and privacy settings

Configure access control, allowed origins, IP restrictions, etc.

Need help? Join our Discord community or contact support for dashboard assistance.

Dashboard guide

Overview tab

Key metrics

Time range selection

Data granularity

Charts and visualizations

Top pages

Page analytics

Page insights

Traffic sources

Referrer categories

Traffic analysis

Geographic analytics

Geographic breakdown