Analytics

What Mezaic counts, how long it is kept, and how to read views, visitors, sources, locations and link clicks, all without cookies.

Website → Analytics shows how people find and use your site. Everything is measured by Mezaic on the server (no cookies, no tracking script, nothing loaded from third parties) so you do not need a consent banner for it.

What is counted

Event When
Page view Any public page renders, including each home tab.
Post read A blog post page renders.
Link click A visitor follows a link in your hub (through /go/…).

Known bots, crawlers and headless browsers are filtered out.

For each hit Mezaic records the path, referrer, UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content), device class, browser and operating system (major versions only), language, and country, region and city from the IP address. The IP address itself is never stored. Visitors are counted with a hash that changes every day, so a “visitor” is one person on one day, and a “session” is that person within a 30-minute window.

Reading the page

  • Traffic & clicks: views, visitors, sessions, clicks and post reads for the period, each with the change against the previous period.
  • Daily trend: a chart; hover a day for the breakdown.
  • Top pages, Sources (referrers and UTM campaigns), Locations, Technology (devices, browsers, systems) and Languages.
  • Top links: clicks per link, plus CTR, which is clicks divided by views of your Links tab in the same period.

The dashboard shows the same numbers for the last 30 days including today.

Retention

How far back you can look depends on your plan’s analytics history (see Plan limits). Older data is deleted on a rolling basis; the period picker is clamped to what your plan keeps. Upgrading extends retention for data recorded from then on, deleted data cannot be recovered.

Tips

  • Tag the links you share (?utm_source=newsletter&utm_campaign=launch) and the Sources card will attribute the traffic.
  • Compare CTR across links to decide what deserves to be featured.

Privacy

Location comes from a local IP-geolocation database (IP Geolocation by DB-IP) at request time. Nothing personally identifying is kept. See Privacy and your data.