Web Analytics

Analytics automatically starts collecting data once your project is publicly accessible. This allows you to monitor usage patterns, understand how visitors navigate your application, and evaluate product performance over time.

These insights help builders make informed decisions about design improvements, feature updates, and growth strategies.

Analytics data can be viewed across multiple time ranges. The most common view is Last 30 Days and a maximum of 90 days, which provides a rolling overview of recent activity.

This timeframe helps identify short-term trends such as:

• Traffic spikes after product launches
• Changes following UI or feature updates
• Growth driven by marketing campaigns or shared links

A timeline graph visualizes visitor activity across the selected period, making it easier to spot patterns and anomalies.

Core Metrics

The analytics overview displays several key metrics that summarize visitor behavior.

Visitors

Visitors represent the number of unique users who accessed the site during the selected period.

A visitor is counted once per session, even if multiple pages are viewed. This metric helps measure the overall reach of your project.

Page Views

Page views represent the total number of pages loaded across all sessions.

If a visitor navigates through multiple routes, each page contributes to the total count. Page views help evaluate how deeply users explore the application.

Views Per Visit

Views per visit measures the average number of pages users open during a session.

Higher values typically indicate:

• Deeper navigation across the application
• Stronger user engagement
• Interaction with multiple sections

Lower values may indicate users exit quickly or find what they need on the first page.

Visit Duration

Visit duration measures the average time visitors spend on the site during a session.

Longer durations generally indicate that users are actively exploring the application or reading content.

Short sessions may suggest navigation friction or mismatched expectations.

Bounce Rate

Bounce rate represents the percentage of visitors who leave the site after viewing only one page.

A higher bounce rate may indicate:

• Users quickly found the information they needed
• The landing page did not match expectations
• Navigation or next steps were unclear

Bounce rate should always be interpreted alongside page views and visit duration for accurate insights.

Visitor Timeline

The timeline graph visualizes visitor activity across the selected time range.

This view helps identify patterns such as:

• Traffic spikes after a launch or update
• Increased activity following link sharing
• Consistent daily or weekly usage trends

Understanding these patterns helps connect product changes with user behavior.

Traffic Sources

The Sources section shows how visitors discovered the site.

Common sources include:

• Direct visits
• Shared links
• External references
• Specific referral URLs

This data helps identify which channels or entry points are driving traffic to your project.

Top Pages

The Pages section highlights which routes receive the most visitors.

Examples include:

• /
• /pricing
• /features
• /docs

Page-level insights help identify:

• Primary entry pages
• Frequently visited sections
• Content users spend the most time exploring

These insights can guide navigation improvements and content optimization.

Geographic Distribution

The Countries section shows where visitors are located.

Geographic data helps builders:

• Identify key user markets
• Evaluate international adoption
• Plan localization or language support

Even small datasets can reveal where early adoption is occurring.

Device Distribution

Traffic is categorized by device type.

Typical device categories include:

• Desktop
• Mobile
• Tablet

Understanding device distribution helps prioritize responsive design and performance optimization.

If most traffic comes from mobile users, layouts and navigation should be optimized for smaller screens.

Using Web Analytics Effectively

Web analytics becomes most valuable when interpreted alongside product changes.

Builders commonly use it to:

• Measure analytics after launching a new project
• Identify which pages attract the most visitors
• Evaluate engagement after design or feature updates
• Understand how users navigate through the application

Over time, these insights help refine both the product experience and the application's overall structure.