Skip to main content

ibm_verify.app_login_counts

Deprecated. Daily SSO event counts by application.
Warning

Deprecated. Use events_app_login_counts instead. See IBM Verify (deprecated).

Daily SSO event counts for each CanadaLogin-integrated application.

Each row represents one application on one day, summarizing that application’s usage and unique-user reach for the day. This table records what IBM Verify calls the sso event type, filed under application usage and raised when someone who is already signed in reaches an application.

auth_total_logins records a different event type (authentication). Figures from the two tables are therefore not comparable and must never be added together or presented side by side.

Keywords: SSO events, application usage, sign-ins, logins, applications, unique users, adoption, daily counts

Provenance

Queried directly from the IBM Verify production instance via API.

  • Updated: Daily, at 06:00 ET
  • Retention: While CanadaLogin exists
  • Steward: EDCP Data and Research Team
  • Contact: Yinlin Zhang

Fields

One row per application_name per day.

Field Name Type Description
application_name string Name of the integrated application (for example, “IRIS - PRC - Prod”)
from_date timestamp Start of the reporting day (midnight)
to_date timestamp End of the reporting day (23:59:59)
total_logins integer Total SSO events recorded for the application that day. Counts events, not people
unique_users integer Number of distinct users who reached the application that day
failed_logins integer Number of failed SSO events that day
successful_logins integer Number of successful SSO events that day
mtd_unique_users integer Cumulative distinct users for the application month-to-date. Resets at the start of each month
ytd_unique_users integer Cumulative distinct users for the application year-to-date. Resets at the start of each calendar year
rolling_365d_unique_users integer Distinct users who reached this application in the trailing 365 days ending on that row’s date
fetched_at timestamp When the aggregation last fetched this row
date string The reporting day as a text date (for example, “2026-04-23”). Mirrors from_date

Notes

total_logins, unique_users, failed_logins, and successful_logins are daily values. mtd_unique_users, ytd_unique_users, and rolling_365d_unique_users are cumulative counts of distinct users and should not be summed across rows; take the latest value within the window instead.

rolling_365d_unique_users is null before 2026-06-13, its implementation date.

Warning

ytd_unique_users and rolling_365d_unique_users may be unreliable. Both are computed by IBM Verify over a longer window than its underlying data retention actually covers, so the figures can undercount, and ytd_unique_users has been seen decreasing from one day to the next. Treat both as estimates only. See Why Unique Users Cannot Be Added Up for detail.

Unlike auth_total_logins, these counts are not inflated by second factors. The per-authentication-method event inflation described there only happens when a person signs in to CanadaLogin itself. Reaching an integrated application uses the session they already hold: CanadaLogin issues the application a freshly minted assertion or token, the person enters no password or second factor, and one handoff records one SSO event. total_logins and successful_logins still count events rather than people, because one person can reach an application repeatedly. Use unique_users when the question is about how many distinct people used the application.