Changelog¶
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[Unreleased]¶
Added¶
- The tracker measures more, for the reports of 0.5: the Core Web Vitals (LCP, INP, CLS) and how far each page is scrolled, sent with the heartbeats and once more when the page is hidden; the screen's width as a class (phone, tablet, laptop, desktop) and the browser's language. Visits keep the browser's and system's major versions. A page marked
data-404, or that callsabilianAnalytics.notFound(), counts as not found. The privacy notice says so. - Engagement and speed, a card of the report: for the top pages, the median time on the page and scroll depth, and the 75th percentile of LCP, INP, CLS and the load time, coloured by Google's thresholds. The table in full lists every page.
- Compare with, next to a report's range: the period before, as until now; the same period a year earlier, weekdays matching; or nothing. The figures, the chart's dashed line, the goals and the tables in full follow the choice, which holds from one project to the next.
- Not found, a card of the report: the addresses that a site marks as not found, with the links that led there: the page before, for the site's own, or the referrer. One viewed 10 times in a week shows on the bell and in the alerts.
Changed¶
- One process runs the web app and the background jobs, on Myxo:
myxo serve layout.toml. The jobs keep their schedules in the app's database, so each runs once per period. Theworkerprocess is gone, with theworkerandgeoip keep-updatedcommands. Before each start,myxo migrate layout.tomlcreates Myxo's tables (on Hop3,hop3.tomlruns it);make runstarts both, restarted when a file changes. - The range chosen holds from one project to the next, and on the overview, until another is chosen.
- A report's controls sit on a row under the title, whatever the project's name: the range on the left, the links to Visits, Excluded traffic and Settings on the right.
- Excluded traffic is the new name of the Filtering page, which lists what the rules left out; the report's filters keep their name. "Add filter" now has a plus.
- The menu lists starred projects first.
- One-line forms (a goal, a person, a share link, a site to monitor) keep their fields on one line, as tall as their buttons.
- The theme toggle shows a moon in light mode, a sun in dark.
- Monitoring is a page of its own in a project's settings: each site with the address checked, whether it is up, the answers over 30 days, response time and certificate, and Start monitoring or Stop monitoring. It says where incidents are sent, and when they are not. It was the Uptime card of the Alerts page.
- The log has one format, Myxo's, and one line per event: a site down or back up, an alert or a report sent, a GeoIP download, a failure. Successful outgoing requests are left out, as are Alembic's start-up lines. Incoming requests are logged in development only: method, path, status and time, without address or query string.
- Instance health and the Monitoring page say when monitored sites go unchecked: the background jobs have stopped, or the app was started without them.
[0.4.1] - 2026-11-17¶
Added¶
- Email: weekly or monthly email reports, chosen per project on the account page; and alerts by email, from a project's settings. Through the SMTP server
SMTP_HOSTnames, such as Hop3's email addon; without it, nothing is offered. - Liveness checks, optional, per site: the worker requests the site every 5 minutes. Two failures in a row open an incident, shown on the bell and the report, posted to the webhook, and marked on the chart; an Uptime card gives each watched site's availability over 30 days, response time and certificate expiry. A certificate expiring within 14 days shows on the bell.
- Alerts by webhook: a project's settings take a Slack or Mattermost incoming webhook, or any address taking JSON. The worker posts each problem the bell shows once, when it appears, with a link to the report when
PUBLIC_URLis set. abilian-analytics workerruns the background jobs, each at a set interval; a failing job is retried at the next turn without stopping the others. On Hop3, thegeoipworker becomesworker.- Notes on the chart: a dated text, added from a project's report, marked on the chart with a dashed line. Share links and viewers see them.
Changed¶
- A project's settings are five pages, each saved separately: General, Tracking, Privacy, Alerts and Sharing. Checking that a site answers moved from the Sites card to the Alerts page. A new project's page asks for the name, hostnames and privacy settings only. Each form ends with Cancel and Save buttons. Snippets, links, tokens and the privacy notice show as code with a Copy button, no longer as read-only fields.
- The menu lists the current project's pages under the project's name: Report, Visits, Filtering and Settings.
[0.4.0] - 2026-11-16¶
Added¶
user list, on the command line: every account, with the username, role, whether it is active, and when it was created.- Opting out:
<div data-aa-optout></div>on a site's privacy page shows a checkbox; a visitor who unticks it is no longer counted in this browser. The objection is the only thing the snippet stores, in the site's local storage. A site's consent interface can callabilianAnalytics.optOut(),optIn()andisOptedOut(). The project's settings show the element to paste, and show on which page of each site the switch was last seen. - Consent-exempt mode, a project setting, on for new projects: it collects and shows only what the CNIL's exemption from consent allows. No campaign parameters, referrers reduced to their site, no visit log, and no figure about 1 to 9 visits (table rows, goals, comparisons, filtered reports). A guide, Without a consent banner, goes through the CNIL's criteria one by one. A card of the same name in each project's settings checks those the settings decide: the mode, the opt-out switch seen on each site, retention within 25 months, Do Not Track respected. Instance health counts the projects that meet them.
- A privacy notice in each project's settings, in English and French, to paste into the sites' privacy page: what is measured, how long visits are kept and how to object, filled from the project's settings, with the opt-out switch.
- Import of Matomo's history from a
mysqldumpfile, after Umami's: on each site, it stops where Umami's history, or our tracker's, starts. Imported visits are judged on their browser's name too: the headless browsers Matomo counted are left out. - All time, next to "90 days": from the day of the first visit, imported ones included.
- A map of countries above the countries table, each shaded by its visits; click one to filter the report. Drawn from Natural Earth's public-domain data and served by the app: no third-party tiles or scripts.
- Archiving a site, from the new Sites card of a project's settings: its hits are no longer recorded, its history stays in the reports; Restore records them again.
- Goals, in a project's settings: a page, every page under a prefix (
/docs/*), or an event. The report lists the visits that reached each, the conversion rate and their change from the period before; click one to filter the report by it. The page filter takes prefixes too. - Outbound links and downloads, counted by the snippet without markup: clicks on links to other sites, and on links to files (PDF, archives, office documents, media), as "Outbound link" and "File download" events with the link's address, less its query string.
data-outbound="off"on the script tag turns them off. - Exit pages, next to pages and entry pages: the page each visit ended on. Visits now keep their entry and exit pages, which an upgrade fills in for the visits already stored; entry pages and campaigns get cheaper to count.
- Tables in full: each table of a report links to a page with every row over the same period and filters, a hundred at a time, with their share and their change from the period before. Pages, entry and exit pages, referrers and campaigns can be searched. Shared reports have them too.
- Documentation as a site, built with Zensical from
docs/and deployed on Hop3 at analytics.lab.abilian.com: getting started, a guide, operations and a reference. - Pagebar in production, for administrators only: each page's time and SQL queries, with the slowest, in a corner.
Changed¶
- Needs attention moved from the overview to a page of its own, behind a bell in the top bar that counts the alerts, judged over the last 7 days. On the overview, a project with alerts shows an icon, which names them in a tip; a project's report shows its own alerts above its figures.
- Switching between "Pages" and "Entry pages", or "Referrers" and "Campaigns", no longer reloads the page. The address still names the tab, so a reload or a filter keeps it.
- Custom periods cover up to 50 years, not two, so an imported history can be seen whole; beyond two years the chart counts per month. A period that was too long fell back to the last 30 days without saying so.
Fixed¶
user set-passwordtakes--generate, asuser createdoes: run remotely, with no terminal to type the password in, it failed with "Empty password".- A hit, a form or a favicon with an address that isn't one, such as
http://[x, made the request fail; it now counts as invalid. - The custom dates and "Add filter" menus had their fields against the menu's edges.
- Custom dates the wrong way round, before 1990 or over 50 years now say why they were refused, in the open menu, instead of showing the last 30 days without a word.
[0.1.0] - 2026-11-13¶
This first release runs in production on our own sites, next to Umami.
Added¶
- Projects that claim hostnames by pattern (
example.com,*.example.com), with sites created as their hits arrive; a list of the hostnames no project claims, attached in one click; archiving; favicons fetched and served from our domain, or uploaded; search. - Collection: one snippet for every site (
/t.js), single-page apps included, and a pixel for pages without JavaScript; custom events (data-event,track()) with a few short properties. Nothing stored in the browser, nor any IP address (a daily-salted visitor hash); Do Not Track and Global Privacy Control respected; of a page's address, only the path and the standard UTM parameters are kept. - Filtering: each visit left out gets its reason: declared bots and AI crawlers, headless browsers, hosting networks, blocked countries, referrer spam. The lists ship with the app; projects and administrators add to them, from the settings or in one click on the filtering page; the rules can be re-applied to past visits. Forged hits are refused.
- Reports per project, in the viewer's time zone: visits, page views, bounce, duration and pages per visit against the period before; hourly or daily charts; pages, entry pages, referrers, campaigns, countries, devices, browsers and systems; filters on any of them; events and their properties; a visit log with CSV export.
- Overview of every project, sorted by any column, starred projects first, with what needs a look (silence, traffic down, visits left out rising, unclaimed hostnames), dismissed for a week.
- Sharing: read-only links to a project's report; read access for other accounts.
- Administration: users, instance-wide filtering rules, instance health (collection, GeoIP freshness, housekeeping, schema).
- API under
/api/v1, with bearer tokens. - Import of Umami's history from a
pg_dumpfile, without counting twice what our tracker recorded. - Command line:
abilian-analyticsfor users, tokens, imports, rules, icons, GeoIP and purges. - Deployment on Hop3 (
hop3.toml), with a runbook indocs/user-guide/runbook.md.
Upgrading an instance deployed before this release¶
- Migrations run before the app starts. One lowercases stored emails, and stops, naming them, if two accounts differ only by case: merge or rename one, then deploy again. Another strips stored page addresses down to their UTM parameters and referrers down to their path: what it removes can't be restored.
- API scripts must use
/api/v1.