Skip to main content

ibm_verify.auth_total_logins

Deprecated. Daily CanadaLogin-wide authentication event totals.
Warning

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

Daily, CanadaLogin-wide authentication event totals across all applications.

Each row represents one day and summarizes overall CanadaLogin authentication activity. This table records what IBM Verify calls the authentication event type, raised each time someone presents an authentication method.

app_login_counts records a different event type (sso, which IBM Verify files under application usage). Figures from the two tables are therefore not comparable and must never be added together or presented side by side. There is also no per-application breakdown here.

Keywords: authentication events, sign-ins, logins, totals, CanadaLogin overall, unique users, daily

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 day.

Field Name Type Description
from_date timestamp Start of the reporting day (midnight)
to_date timestamp End of the reporting day (23:59:59)
unique_users integer Number of distinct users who signed in to CanadaLogin that day. In IBM Verify, this is referred to as “unique logins”.
failed_logins integer Number of failed authentication events that day
successful_logins integer Number of successful authentication events that day.
mtd_unique_users integer Cumulative distinct users month-to-date. Resets at the start of each month
ytd_unique_users integer Cumulative distinct users year-to-date. Resets at the start of each calendar year
rolling_365d_unique_users integer Distinct users who signed in to CanadaLogin in the trailing 365 days ending on that row’s date
last_updated_at timestamp When the underlying data for this row was last updated
fetched_at timestamp When the aggregation last fetched this row
date string The reporting day as a text date (for example, “2026-05-21”). Mirrors from_date

Notes

unique_users, failed_logins, and successful_logins are daily values. The mtd_, ytd_, and rolling_365d_ unique-user fields are cumulative 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.

When a user signs in to CanadaLogin itself, IBM Verify records each authentication method as a separate event. Entering a username and password followed by a second factor like an OTP counts as two successful events. A mistyped password that is then entered correctly, followed by a correct OTP, counts as three events: two successful and one failed. Both successful_logins and failed_logins are therefore inflated relative to the number of distinct sign-in sessions.

This inflation applies only to signing in to CanadaLogin itself. Reaching an integrated application does not add to these counts at all: it raises an SSO event on app_login_counts instead. CanadaLogin uses the session the person already holds and issues the application a freshly minted assertion or token, so the person enters no password and no second factor.

Summing successful_logins is therefore a misleading indicator of actual user engagement. Instead, use the unique_users field, which is daily active users, and is a measure of the number of users who engaged with the system in a given day.