Skip to main content
Analytics shows you who’s using your published app: how many people visit, which pages they land on, where they came from, and how much revenue you’re bringing in. You turn it on per project, and the data is anonymous.

​
Turn analytics on

Analytics is off by default. You enable it one project at a time, either from the Analytics page or from a project’s settings.
1

Open Analytics

Go to the Analytics page and pick the project you want from the project dropdown. If analytics is off, you’ll see an “Analytics is off for this project” message with an Enable analytics button.
2

Read the disclosure, then confirm

A short disclosure explains what gets collected: screen views, visitor counts, and traffic sources, all anonymous. No names, no emails, no device advertising IDs. Click I understand to turn it on.
3

Wait for data to land

Once it’s on, the tracking starts with your live traffic. Charts fill in as visitors arrive, so a brand-new project will look empty until people start showing up.
You can also flip the toggle from a project’s Analytics settings. Turning analytics off is instant. Turning it on always shows the disclosure first.
Publishing to the App Store or Google Play? You’re responsible for disclosing analytics in your app’s privacy label as “Usage Data → Product Interaction.” Anything collects the data, but the store listing is yours to declare.

​
What you can see

Once analytics is on, the dashboard breaks down into a few sections.

​
Headline metrics

Four cards at the top, each with a trend badge comparing the current period against the one before it:
MetricWhat it means
VisitorsUnique people who opened your app
Page ViewsTotal screens or pages loaded
Views / VisitorAverage pages each visitor looked at
Bounce RateShare of visitors who left after a single view
If your app takes payments through Stripe, this chart shows total revenue, paying users, and average revenue over the selected period. No Stripe account connected yet? The card prompts you to connect one instead of showing an error.
Revenue reads from your connected Stripe account on demand, so it covers the same web payments you already manage there. See Stripe payments for connecting an account.

​
Traffic over time

A line chart of visitors and page views across the period, so you can spot spikes, launches, and quiet stretches at a glance.

​
Top pages

Your most-visited pages, ranked. This table also has two AI shortcuts that hand the work back to the agent:
  • Improve low-traffic pages opens the builder with a prompt to diagnose why your quietest pages aren’t landing and make specific fixes.
  • Brainstorm new pages uses your top performers as a starting point and suggests new pages that build on what’s already working.

​
Traffic sources and visitor breakdowns

The second table groups your traffic a few ways. Switch between them with the dropdown:
  • By Source buckets referrers into search, social, and direct.
  • By Browser, By OS, and By Device show what people are using to reach your app.

​
Filter the view

Two controls sit above the dashboard and apply to everything below them:
  • Period: Today, Last 7 Days, Last 30 Days, Last 90 Days, or Last 12 Months. Defaults to the last 30 days.
  • Device: All Devices, Web (desktop and mobile browsers), or Mobile App (native iOS and Android events).
Switching either one refreshes the metrics, charts, and tables in place.

​
How the data works

A few things worth knowing about what’s behind the numbers:
  • Anonymous by design. Anything tracks screen views and a stable, anonymous device signal. It doesn’t store names, emails, or advertising IDs.
  • Web and native. Web traffic is measured with a lightweight beacon on each page. Native mobile apps send screen-view events directly, so the Mobile App filter reflects real native usage, not mobile-browser visits.
  • Period-over-period. The trend badges compare your current window against the equal-length window right before it, so “Last 30 Days” is measured against the 30 days before that.