Usage & analytics
- Written for
- + Written for
- Deprecated
- + Deprecated
- Applies to
- + Applies to
Usage & analytics
The dashboard gives you a straight read on how authentication is going — how many people are signing up, signing in, and coming back — without wiring up a separate analytics tool.
The metrics
Under Analytics (or GET …/usage on the dashboard API) Atlas reports daily time series plus a headline number:
Sign-ins per day — successful authentications.
Sign-ups per day — new users created.
Emails per day — transactional messages sent (verification, reset, invitations).
Active users per day — distinct users who were active that day.
Monthly active users (MAU) — a trailing 30-day distinct count. MAU is computed as a true distinct count of users, never a sum of the daily active-user rows (which would double-count anyone active on more than one day).
Reading the trends
A gap between sign-ups and sign-ins over the following days is your activation/retention signal.
A spike in emails without matching sign-ups can indicate reset loops or abuse.
MAU is the number to watch for growth and for plan sizing.
Security analytics
Attack protection keeps its own view: the anti-bot signal rows (risk verdict, network origin, geo, CAPTCHA result, newest first) show why requests were challenged or stepped up. See Attack protection.
Getting the data out
The usage series is available on the dashboard API, so you can pull it into your own dashboards.
For event-level data rather than aggregates, stream webhooks to your warehouse, or export the audit log as CSV.
Next
Return to the start → What is Atlas?.