Support

Features

Analytics starts after publish, not during preview

The `Analytics` tab shows traffic for the live published site. It is designed to answer what happened after release, not whether the preview is loading correctly during iteration.

Features3 sections

States

Expect different analytics states

The `Analytics` tab does not always open into charts. Its state depends on whether the project is live and whether traffic exists yet.

Unpublished project

The tab explains that analytics are not available yet and points you back toward the website/publish flow.

Published, but no traffic yet

You can still open the live site, but the charts stay empty until requests arrive.

Published with traffic

Flutty shows request totals, trend charts, and daily limit context.

Load failure

If analytics data cannot be fetched, the tab shows an explicit failure state instead of silent emptiness.

Usage

Read the metrics in the right order

The most useful way to read the tab is from current demand to longer-term pattern.

  1. 01

    Start with today

    Check how many requests the live site received today and how much of the daily allowance was used.

  2. 02

    Check what remains

    Review the remaining quota before reset if the plan exposes a daily limit.

  3. 03

    Read the chart trend

    Use the daily graph to spot whether traffic is flat, growing, or peaking on specific days.

  4. 04

    Open the live site when needed

    If numbers look suspicious, compare them against the actual published URL rather than the preview.

Boundary

Use analytics for live questions only

The `Analytics` tab becomes much clearer when you treat it as a post-publish surface.

Use `Website` for preview validation.

Use `Publish` to push a known-good state live.

Use `Analytics` to understand what happened after users reached the live site.