Web analytics and speed insights

Web analytics and speed insights are Pro features, turned on per app or function: in the dashboard, project → Settings → Analytics. Turn on both or either one. On Hobby the card shows the Upgrade button and the API answers 402 plan_required.

cloudhost analytics enable my-site            # both
cloudhost analytics enable my-site --speed    # speed insights only
cloudhost analytics settings my-site --speed-sample 50

The platform serves the script at /_insights/script.js on the hostname of every site it hosts. It is about 4 KB, has no dependencies and stores nothing in the browser. Add one of these to your site:

<script defer src="/_insights/script.js"></script>

• The script sends a page view on every page load and on every single-page navigation (it follows history.pushState), and the Web Vitals of the page load when the page is hidden.
• Events are batched and sent with sendBeacon, and the server answers at once: analytics never slows a site. Under heavy load extra events are dropped, never your site's requests.
• The Next.js and Astro components only add the route pattern (/blog/[slug]), so speed insights groups pages the way your app does. Without them, numbers, ids and long hashes in a path become [id].
• Only /_insights/script.js and /_insights/event are the platform's; any other path under /_insights/ is your site's own.

Production and preview are kept apart; production is the default. Periods of two days or less are shown by the hour, longer ones by day (Tehran time).

The period is 24 hours, 7, 30 or 90 days, 12 months, or any range the plan keeps. Every list is a filter: click a country to see that country's pages. Filters combine.

• Visitors are counted per day (Tehran time); someone who comes on two days is two visitors. This is the price of not tracking.
• Filtered to one page, the visitors are that page's own, and bounce rate is not shown.
• Bounce rate is the share of visits that saw one page only.
• Distinct paths per hour are capped (2,000 on Pro); the rest count as (other), so a bot inventing URLs cannot flood your data.

Each metric scores 0 to 100 on a log-normal curve through its thresholds: the “good” threshold scores 90 and the “poor” one 50, as page-speed tools do. The score is the weighted mean of the metric scores at the 75th percentile; a metric with no reports shares its weight out. 90 and up is good, 50 to 89 needs improvement, below 50 is poor.

Mobile and desktop are measured apart (tablets count as mobile). Percentiles are read from counts of reports in logarithmic ranges and are accurate to about 10%.

A busy site does not need every page load's vitals. In Settings, set the sample from 1 to 100 percent: at 10%, one page load in ten keeps its vitals and speed insights costs a tenth. A page load's vitals are kept or dropped together. Page views are never sampled.

cloudhost analytics settings my-site --speed-sample 10

Past the included amount you pay per 100,000; the prices are on the pricing page. Events that are dropped (feature off, bots, over the limit, not sampled) are not billed.

curl -H "Authorization: Bearer $KEY" \
  "https://api.ibel.ai/v1/apps/my-site/analytics?period=30d&country=IR"

curl -H "Authorization: Bearer $KEY" \
  "https://api.ibel.ai/v1/apps/my-site/speed-insights?device=mobile&period=7d"

Every route, parameter and error code is in the API reference.

Web analytics and speed insights collect no personal data. You can link this statement from your site's privacy notice.

• No cookies, no local storage, no fingerprinting. The script stores nothing in the visitor's browser.
• No addresses kept. The visitor's IP address is used once, when an event arrives, to look up a country, and is then discarded. It is never written to disk or to a log.
• Visitors are counted with a hash that cannot be reversed. To count unique visitors, we compute a hash of the visitor's address and browser string with a random salt that changes every day (Tehran time) and is deleted after the next day. The hash is kept only for that day and the next, then deleted with the salt. It cannot be linked to a person, nor to the same visitor on another day or another site.
• Only counts are stored. What is kept is how many page views and visitors each page had in each hour, by referring site (its hostname only, never the full address), country, device class (desktop, mobile, tablet), operating system and browser name; and, for speed, how many reports fell in each range of each metric, by route and device class.
• Query strings and fragments are dropped before anything is stored, so search terms, tokens and emails in URLs are never kept.
• Data stays in Iran, on the platform's own servers, and is deleted when the plan's retention ends, or at once when the project owner turns analytics off and deletes the data.
• No consent banner is needed for this data under the usual cookie rules, as no information is stored on or read from the visitor's device; site owners remain responsible for their own privacy notice.

The country comes from an IP-to-country list kept on the platform's servers; nothing is sent anywhere to look it up. Visits from bots (by browser string) are not counted.

Turning off stops collection; the counts already kept stay until the retention ends. “Delete data” in Settings (or cloudhost analytics delete) turns both off and deletes every count at once; with a dashboard session it needs step-up.