Analytics
Privacy-friendly website analytics that show you how many people visit your site, where they come from, and what pages they view — without cookies.
Adding a website
Go to Analytics and click Add Website. Enter a name and your domain (for
example mysite.com). After creating it, you will see a tracking script on the
settings page — paste it inside the <head> tag of your website's HTML.
Understanding your dashboard
Once the script is installed, your dashboard shows:
- Pageviews — total pages loaded
- Visitors — unique people
- Visits — total sessions
- Bounce rate — single-page sessions
- Avg. duration — time on site
Use the date picker to view different time periods.
Breakdowns
Below the main stats you will see breakdowns by top pages, referrers, browsers, operating systems, devices, and countries. These help you understand which content performs best and where your traffic comes from.
Realtime
Visit the Realtime tab on any website to see who is on your site right now — live visitor count, active pages, and a real-time event log.
Custom events
Track button clicks, form submissions, or any user action by adding event tracking to your site. Events appear in the Events tab with counts and custom properties.
Sharing
In website settings, enable sharing to get a public link anyone can view — no login required. Useful for sharing stats with clients or stakeholders.
Browser storage
The tracking scripts set no cookies. They use these browser-storage keys on your website, which you should list in your own privacy or storage notice:
| Key | Store | Lifetime | Purpose |
|---|---|---|---|
aa_visitor_id | localStorage | Until the visitor clears site data | Random pseudonymous visitor ID used to count returning visitors (advanced script only) |
aa_session_id | sessionStorage | Until the tab is closed | Groups one visit's page views into a session (advanced script) |
analytics_session | sessionStorage | Until the tab is closed | Groups one visit's page views into a session (standard script) |
The persistent visitor ID (aa_visitor_id) is not written or sent when any of
these applies, and the advanced script also removes an existing one:
- No persistent visitor ID is turned on in the website's settings and
your site uses the updated install snippet, which carries
data-persistent-id="false". Ingestion ignores any visitor ID a browser sends for that website as soon as the setting is on, even before you update the snippet. - The visitor's browser sends Global Privacy Control.
- The visitor's browser sends Do Not Track.
Without the persistent ID, visitors are counted from a server-side hash of IP address, user agent and website ID; the IP address is not stored. If the browser blocks storage, the scripts write nothing and keep working.
These controls apply to browser tracking. On the server-to-server API
(/v1/track) you supply the visitor ID and are responsible for honouring your
visitors' privacy preferences; with No persistent visitor ID on,
/v1/track drops any supplied visitorId.