Analytics
Sitebase counts the visitors and pageviews of every website you connect. No cookies, no consent banner, nothing stored in your visitors' browsers.
Setting it up
Open a website in the dashboard and switch to its Analytics tab. Before any data arrives it shows
your tracking snippet — one script tag to add to every page of your site (in the <head> or
before </body>):
<script async crossorigin="anonymous" src="https://sitebase.dev/embed.js" data-sitebase-site="sb_9956592511db47e1ad398ff1"></script>
The data-sitebase-site key identifies your website. Two shortcuts worth knowing:
- Pages that embed a Sitebase feature already report pageviews. The embed script doubles as the tracker, so a page with a waiting list or testimonials wall on it doesn't need the analytics snippet too.
- Single-page apps work out of the box. Client-side navigations (pushState and back/forward) are counted as pageviews automatically.
Visit your site after installing and the first numbers appear within seconds.
What you see
The website's Dashboard tab (and the overview homepage) shows the headline: unique visitors and pageviews over the last 30 days, with a visitors-per-day chart. The Analytics tab is the full report, switchable between the last 7 days, the last 30 days, and a 12-month view:
- Unique visitors, pageviews, bounce rate, visit duration — the headline metrics.
- Visitors over time — a per-day chart for the selected range.
- Top pages — which pages people actually visit.
- Sources — where visits come from: search engines and social networks get friendly names
(Google, X, Hacker News…), and links tagged with
utm_source,sourceorrefquery parameters are attributed to that tag. - Countries, devices, browsers, operating systems — who your visitors are.
Data retention
Sitebase keeps analytics at two levels of detail:
- Per-visit detail for 30 days. Everything the breakdowns are built from — pages, sources, countries, devices, browsers, operating systems — is kept for the last 30 days, then deleted.
- Daily totals long-term. Visitors, pageviews, visits, bounce rate and visit duration are summarized per day and kept, so the 12-month view always shows how your traffic evolved.
This keeps the analytics fast and is a deliberate privacy choice: visitor-level data doesn't pile up forever. Sitebase analytics is the built-in pulse of your website, not a full historical archive — if you need deep, unlimited-history analysis, pair it with a dedicated tool like Plausible or Fathom; the tracking snippets coexist happily.
How visitors are counted, and privacy
The design follows Plausible Analytics, the reference for privacy-first web analytics. The tracker stores nothing in the browser — no cookies, no localStorage, no fingerprinting. Each pageview is attributed to a visitor by hashing the visitor's IP address and browser together with a random salt that changes every day and is then deleted: the same person counts once per day, the raw IP is never stored, and yesterday's hashes can never be linked back to anyone.
A visit (or session) groups pageviews from one visitor with less than 30 minutes of inactivity between them. A visit that sees a single page counts as a bounce. Known bots and crawlers are filtered out before anything is stored.
To exclude your own visits while you work on your site, run
localStorage.sitebase_ignore = "true" in your browser's console on your site — that browser stops
being counted.
Next: Appearance