Usage insights

Turn it on#

Usage insights are off until you turn them on, per project, in Abrova Auth › Settings › Usage insights (owners and admins). Counting starts at that moment; nothing from before is filled in.

Pick the time zone your days are counted in (default UTC; for users in Iran, Asia/Tehran), so "today" matches your market. It is one setting per project, the same for everyone who views it. A change applies from the next day; past days keep their numbers, and on the day of the change some users can be counted twice.

Turning it off stops counting and deletes the project's usage numbers.

What you see#

Under Abrova Auth › Overview › Usage:

Numbers update within about a minute. Weekly and monthly active users are for the current week and calendar month, not a rolling 7 or 30 days.

What "active" means#

A user is active on a day when they sign in or renew a session that day. The SDKs renew the 1-hour access token when it has less than 2 minutes left and your app (or another Abrova SDK) asks for it: in practice when the app starts after more than an hour, and about once an hour while it is used.

• A request that is refused does not count: the monthly user limit with an empty wallet (MAU_LIMIT), a disabled user, an expired or ended session.
• Deleting a user, or the removal of idle anonymous users, does not change past days.

Known gap. A user who opens the app late in the evening and again shortly after midnight, within the same hour, is not seen on the second day: their token is still valid, so nothing reaches Abrova Auth. Daily numbers can therefore be slightly low, never high.

What is stored#

Counts, not tracking. Abrova Auth stores how many of your users were active on each day — for example "312 users on 24 October" — never a list of the days or times a person used your app.

• No new data leaves the device; only requests Abrova Auth already receives are counted.
• No IP address, e-mail, phone, token or user id is part of a count.
• The numbers are only for you: no third parties, no advertising, no profiling.
• Counts are kept 400 days.

You can describe it in your own privacy policy, for example: "We count how many people use the app each day with an anonymous id; no name, no e-mail, no tracking."

Free and with a wallet balance#

Usage insights cost nothing extra. How much the Console shows depends on whether your project uses only the free monthly allowance or pays as you go from a wallet balance:

Counts are always kept 400 days; only what is shown changes, so topping up the wallet shows your full history at once.

Insights API#

For your own dashboards and scripts, when your project pays as you go from a wallet balance. Call it from your server with your API key and server secret, never from an app or a browser: the server secret must not ship in client code. An app that only signs users in needs none of this — the Console shows the same numbers.

curl "https://auth-users.abrova.ir/v1/projects/YOUR_PROJECT_ID/insights?from=2026-10-01&to=2026-10-24" \
  -H "x-api-key: $ABROVA_API_KEY" \
  -H "x-server-secret: $ABROVA_SERVER_SECRET"

{
  "enabled": true,
  "timeZone": "Asia/Tehran",
  "today": "2026-10-24",
  "activeToday": 312,
  "weeklyActive": 1104,
  "monthlyActive": 1840,
  "stickiness": 0.17,
  "days": [
    { "day": "2026-10-24", "active": 312, "new": 41,
      "byPlatform": { "android": 201, "ios": 111 },
      "byMethod": { "anonymous": 290, "google": 22 } }
  ],
  "returning": [
    { "cohort": "2026-10-17", "size": 52, "day1": 21, "day7": 12, "day30": null }
  ]
}

• from and to are days in the project's time zone, YYYY-MM-DD. Without them you get the whole window you can see; a range outside it is shortened to it.
• day1, day7 and day30 are null until the cohort is old enough.
• Your project's server-secret IP allow-list applies.

Not included#

Events, funnels, screens and custom properties are not part of Abrova Auth: it counts users, not what they do. Keep "did users finish level 3" in your own data, for example one Abrova Sync document per user.