Analytics
What visitors asked, where they came from, and whether the assistant answered. Everything is measured from the widget itself — there is no third-party tracker and no cookie beyond the session id.
What is measured
| Metric | Meaning |
|---|---|
| Sessions | One conversation. A returning visitor continues their existing session rather than starting a new one. |
| Messages | Questions the visitor sent. Assistant replies are not counted. |
| Page views | Pages where the widget loaded, whether or not it was opened. |
| Widget clicks | Times the launcher was opened. |
| Engagement rate | Share of page views that led to a conversation. |
| Messages per session | Average visitor messages in a conversation, as a measure of how far conversations go. |
By domain
A widget installed on several sites reports each separately, so you can see which one drives conversations. The domain is the page’s own origin, read at the moment the widget loads.
A file:// row means the widget was opened from a file on disk rather than a served page — usually your own testing.
By country
Country comes from the visitor’s browser timezone, mapped to an ISO country code. Asia/Dubai becomes AE, Europe/London becomes GB.
Timezone is used rather than language settings deliberately: a visitor in Dubai reading an English interface reports a locale of en-US, which would place them in the wrong country. Their timezone reflects where they actually are.
Two caveats worth knowing. A visitor on a VPN reports wherever their device believes it is. And a timezone Minaya does not recognise falls back to the region in the browser locale, then to unknown — so a small share of unknown is normal rather than a fault.
What is not collected
- No IP addresses. Country is derived in the browser from the timezone; no geolocation lookup is performed and no IP is stored.
- No third-party analytics. Nothing is sent to Google Analytics or any similar service.
- No cross-site tracking. The visitor identifier is scoped to one widget and cannot follow someone between customers.
Conversation transcripts are stored so you can read what was asked and improve your knowledge base. They are visible only to you.
Timeframes
The dashboard shows the last 7, 30 or 90 days, counted in UTC calendar days with today included. The totals always equal the sum of the daily chart.
A session is attributed to the day and hour it started, so a conversation spanning midnight counts once; its page views and widget clicks count on that day too. Messages count on the day and hour they were sent.
Sessions whose domain was never recorded are grouped under unknown.
How fresh the numbers are
Counts are calculated in the background about once a minute rather than on every page load, which keeps the dashboard fast however much traffic you have. A new conversation shows up in the numbers within a few minutes; the conversation list itself is always live.