Overview
What metuno is made of, and what happens between someone opening your page and a number appearing in the panel.
metuno measures website traffic without writing anything to the visitor device. No cookies, no localStorage, no reading of browser properties. Several things follow from that, and this documentation describes them: you need no consent banner for the measurement itself, you will not see one person journey across several days, and the numbers will not match a tool that does store those cookies.
Four parts
The system has four pieces, and it is worth knowing which does what, because diagnosing a problem almost always comes down to one of them.
Desplaza la tabla en horizontal para ver las demás columnas.
| Part | What it does |
|---|---|
| Measurement script | 1.6 kB compressed with brotli. It sits on your page, sends an event on each pageview and again when the tab closes, once the visit duration is known. |
| Collector | Accepts events, recognises the site by domain, determines browser, system, device and country, then computes a daily pseudonym. It has no access to the account database or to passwords. |
| Event store | ClickHouse on servers in Warsaw. One table per site, partitioned by month. Events disappear automatically after 25 months. |
| Panel | Computes reports on request, from raw columns. That is why a new goal covers the whole history you already have. |
The path of one pageview
- The browser loads your page and fetches the measurement script with the defer attribute, so it never blocks rendering.
- The script checks the Do Not Track header. If it is on, it sends nothing and stops there.
- The script sends one request with the page address, the referrer and the window width. It asks the browser for nothing else.
- The collector recognises the site by domain, truncates the network address, computes a pseudonym with the daily salt and stores the event.
- The panel reads those events and computes the report at the moment you look at it.
Where to start
- Installation: pasting the script, checking that it works, and the variant for browsers without JavaScript.
- Events and goals: what to do so the panel counts more than pageviews.
- Sources and channels: how the panel knows a visit came from search, from an ad or from an AI assistant.
- Data and export: exactly what we store, for how long, and how to take it with you.
- Plans and limits: what happens when the pageview allowance runs out.