Traffic analytics
Every published Berrybell app measures its own traffic. There's nothing to install, no script to paste and no account to connect — publishing your app is what starts collection.
Open Project settings → Analytics to see it. It's per project.
What it shows
Pick a range — Last 24 hours, Last 7 days or Last 30 days — and you get:
- A row of headline numbers.
- A chart of traffic over the range.
- Breakdowns by traffic source (Sources) and by device (Devices).
Beside the range picker, two labels describe everything recorded for the project, whatever range you pick:
- Measured against names an address traffic has been recorded on — your Berrybell address or a custom domain; with several, the first alphabetically — and adds +N for the others. Hover it for the full list.
- as of gives the most recent hour with recorded traffic. If that hour is today, it shows just the time; otherwise it shows the date as well.
The headline numbers
The lead number changes with the range, on purpose:
- Over 24 hours the lead tile is Visitors, with visits underneath it.
- Over 7 or 30 days it swaps to Visits, with "≈ N visitors/day" underneath.
Then Page views, Views / visit and Visit duration.
What "visitors" actually means
This is the number worth understanding before you quote it to anyone.
Measurement is cookieless and first-party, and the identifier behind "visitors" rotates every day. So the visitor figure is really visitor-days, not distinct people: somebody who comes back on three different days counts three times.
That's why the 7- and 30-day views show an average per day rather than a total — summing visitor-days across a month would be a number that means nothing. It's a deliberate privacy trade-off, not an approximation to apologise for.
Two more definitions, straight from the panel:
- A visit ends after 30 minutes of inactivity.
- Visit duration is active time only — the beacon stops counting while the tab is in the background.
Both are why these totals won't match a Cloudflare dashboard you might also have open. Different definitions, not a discrepancy.
The "Estimated" badge
If you see an Estimated badge next to the range picker, the underlying service sampled some of those hours. The counts are already weighted to compensate — read them as close estimates rather than exact figures.
If the panel is empty
Four things it can be telling you:
- Publish this project to start collecting. The project hasn't been published to production yet. Traffic is measured by a beacon served on your published site, so nothing is recorded until the project is live.
- Collecting — first numbers appear within the hour. The project is published and the beacon is live, but nothing has been counted yet. Traffic is rolled up every 15 minutes, plus a further 15-minute lag so late-arriving visits aren't missed — allow about half an hour after your first visitor.
- No visits recorded in this period. Collection is working, but nothing came in during the range you picked, so the headline tiles show zero. Try a longer range.
- Traffic collection is switched off. Berrybell isn't adding new traffic numbers to the panel right now. This isn't a per-project setting, and there's nothing to change in your project. Numbers already collected stay on the panel for as long as they fall inside the range you pick (the longest is Last 30 days). No new visits are added, and as of stays at the last recorded hour. Collection resumes when it's switched back on.
How far back it goes
Hour-by-hour detail is kept for 35 days, and is then rolled up into daily figures which are kept for 400 days. Every range the panel offers (up to Last 30 days) is served from the hourly detail. The daily figures kept beyond that aren't shown on the panel yet.
What it doesn't show yet
Top pages and visitor country are collected but not displayed, and there's no traffic figure on project cards. Ask for what you need — it's collected data waiting on a screen, not missing measurement.
Environment traffic is different: it isn't recorded at all. Analytics count
production only, so visits to
environments you created,
such as staging, aren't counted, and changing the selected environment doesn't
change what the panel shows.
What it costs
Nothing, and no credits. The beacon script and the requests it sends are answered by Berrybell's own edge, before anything routes to your app — so your visitors' measurement doesn't come out of your hosting budget.