Web Analytics
Web Analytics
Traffic, conversions and real-user performance for your sites, without cookies and without storing IP addresses. Turn it on for a Hubfly space domain with one switch, or add one script tag to a site hosted anywhere.
A site belongs to a project. Add one from the Analytics tab of a Cell or Box project, or create a standalone Web Analytics project for sites you host elsewhere. All sites in a project share one event counter, and the first 100,000 events each month are free per account or organization. See pricing and limits.
Web Analytics is coming soon
Choose a guide
How it fits together
| Resource | What it is |
|---|---|
| Project | The billing pool. A Cell or Box project has an Analytics tab; a Web Analytics project holds only sites hosted elsewhere. Every project with analytics can set a monthly event cap. |
| Site | One website with a public id such as hfa_k7m2p4q9x3w5n8r6, one or more domains, a time zone and its own settings. Each site has its own database in the project's region. |
| Domain | A hostname whose pages are counted. Events from other hosts are filtered. A site can include subdomains. Domains of sites hosted elsewhere are verified with a DNS TXT record. |
| Goal | A pageview path or custom event you want to count as a conversion, optionally with revenue. |
| Funnel | An ordered list of pages and events, showing how many visitors reach each step. |
| Ingest key | A secret (hfak_…) that lets your servers send events for one site. Shown once when created. |
| Shared link | A read-only view of a site's dashboard for people without a Hubfly space account, with an optional password and expiry. |
What is collected
| Data | From | Billable |
|---|---|---|
| Pageviews, including single-page app navigation | The script, the <noscript> pixel or your server | Yes |
| Custom events with props and revenue | hubfly('track', …) or your server | Yes |
| Outbound link clicks, file downloads, form submits and 404s | The script, when turned on for the site | Yes |
| Engaged time and scroll depth | The script | No |
| Web Vitals: LCP, INP, CLS, FCP and TTFB | The script, when turned on for the site | No |
| JavaScript errors and unhandled promise rejections | The script, when turned on for the site | No |
From each pageview Hubfly space derives the page path, the referrer source and channel, utm_* campaign tags, the country and region, the browser, operating system and device class, and the language. The rest of the query string, IP addresses and full user agents are discarded before anything is stored. Bots, automated browsers and excluded IPs and paths are filtered and never billed.
Reports
- Overview: visitors, visits, pageviews, bounce rate and visit duration, compared with the previous period, plus live visitors.
- Sources, pages, locations and devices, with a filter bar that applies to every view (is, is not, contains) and a date range with comparison.
- Events & goals: conversions, conversion rate, revenue and a props explorer.
- Funnels and journeys: step-by-step drop-off, and the paths visitors take between pages.
- Web Vitals: the 75th percentile and the good / needs improvement / poor split, per page.
- Errors: grouped JavaScript errors with the pages and browsers they happen on.
- Realtime: visitors and events as they arrive.
The site's Settings → Data & export downloads raw events, visits or daily summaries as CSV or NDJSON, and hubfly analytics reads the same reports from a terminal.
Location data comes from IP geolocation by DB-IP.
How the script reaches your site
Sites hosted on Hubfly space use a first-party path on their own domain: the script loads from /.hubfly/a/s/<site>.js and sends events to /.hubfly/a/e. It is same-origin, so a script-src 'self' Content Security Policy allows it and events need no CORS. With automatic injection, HubProxy adds the script tag to your HTML pages, so no code change is needed.
Sites hosted elsewhere load the script from the HubProxy of their project's region, https://hfa.<region>.hubfly.app. Dashboard shows the exact tag for each site.
The script is small: its core is at most 2.5 KB compressed, and the Web Vitals and error modules are added only when a site turns them on. A site that is paused or deleted serves an empty script, so your pages never show console errors because of it.
Regions and moves
A site's data lives in its project's region and events are sent only to that region. When a Cell project is moved to another region, its sites, settings and daily summaries move with it, so trend charts continue. Raw events from before the move stay in the old region, read-only, until their retention ends; reports that span the move combine both.
Team access and sharing
Anyone who can see a project can read its analytics; changing sites, goals, funnels, keys and settings needs permission to manage the project. A shared link gives read-only access to one site's dashboard without a Hubfly space account. Revoke it at any time from the site's Settings → Shared links.