Skip to main content

IBM Verify

Metrics in this section come from IBM Verify, which records two different kinds of event. It raises an authentication event when someone presents an authentication method to CanadaLogin: a password, then a second factor. It raises an SSO event when someone who is already signed in reaches a partner service, and files that one under application usage. These are separate event types, so a figure taken from one is never comparable to a figure taken from the other.

A user signs in to CanadaLogin once and gets a session. Reaching a partner service afterwards does not sign them in again: CanadaLogin uses the session it already holds and issues the partner a freshly minted assertion or token. One sign-in, then as many handoffs as the user needs.

Term Means Which table
Sign-in The human act: a password, then a second factor None counts it directly
Authentication event What IBM Verify records while that happens. Runs ahead of sign-ins events_auth_total_logins
Session The signed-in state at CanadaLogin, reusable by later handoffs None
SSO event The session being used to reach a partner service events_app_login_counts

“Sign-in” is prose only. No table counts it, so it is never an output column name or an axis label, and names a metric only where that metric is labelled an estimate.

The relevant IBM Verify tables are:

Their from_date is a string, so every query below casts it. See Dates are strings.

Internal CanadaLogin components. Internal CanadaLogin components are typically excluded from public-facing adoption metrics. Which ones are internal comes from rp.service.is_internal, resolved to IBM Verify’s application IDs through rp.alias:

SELECT al.alias
FROM   rp.alias al
JOIN   rp.service s ON al.rp_id = s.rp_id
WHERE  s.is_internal

Use the subquery rather than a pasted list, so the classification stays in one place. Match it against application_id. See the internal CanadaLogin components note in notes.qmd.

CanadaLogin Metrics

Metrics in this section describe CanadaLogin overall, across all applications, sourced mainly from ibm_verify_events_transformed.events_auth_total_logins (the estimated sessions metric also draws on ibm_verify_events_transformed.events_mfa_activity).

Metric Description
Authentication Events Total authentication events, successful and failed.
Authentication Success Rate Share of authentication attempts that succeeded, across CanadaLogin.
Completed Sign-In Sessions (Estimated) Estimated number of sign-ins that got all the way through the flow.
Sign-Ins per Active User (Estimated) Estimated sign-ins per user in a calendar month, among users who signed in.
Cumulative Unique Users Distinct users who signed in this month or this calendar year.
Average Daily Users Distinct users on a typical day over a reporting window.
New Accounts and Idle Account Rate Accounts created per day, and the share that never reached a partner service.
No matching items

Application Metrics

Metrics in this section describe how much each application is used, sourced from ibm_verify_events_transformed.events_app_login_counts. IBM Verify records this as SSO events, filed under application usage: someone who is already signed in reaching a service. The person enters no password and no second factor, which is why these counts are not inflated the way the CanadaLogin-wide authentication events are.

Metric Description
SSO Events by Application Total SSO events for each application.
SSO Success Rate by Application Share of SSO events that succeeded, by application.
Peak Daily Unique Users Highest number of unique users on any single day.
Cumulative Unique Users by Application Distinct users per application this month or this calendar year.
Daily Share of Monthly Users by Application The share of an application’s monthly users who sign in on a typical day.
Multi-Service Users Share of users who have signed in to two or more public services.
Average Daily SSO Events Average SSO events per day for each application.
No matching items

Multi-factor Authentication Metrics

Metrics in this section describe multi-factor authentication (MFA) activity, sourced from ibm_verify_events_transformed.events_mfa_activity. That table has one row per day per MFA factor (mfa_type) per outcome (result), with the number of events in count. A sent row is a code issued; success and failure rows are outcomes. Most metrics here cover only the factors the public can sign in with.

IBM Verify files MFA as a subtype of the authentication event rather than as an event type of its own, so these counts are a slice of the CanadaLogin-wide authentication events, not a separate stream.

Metric Description
MFA Challenges Second-factor challenges issued at sign-in in a reporting period.
Second-factor Attempts Second-factor outcomes at sign-in, successful or failed, in a reporting period.
MFA Success Rate Share of second-factor attempts at sign-in that succeeded.
MFA Success Rate by Factor MFA success rate for each factor.
All MFA Activity by Factor MFA challenges by factor, with each factor’s share of the total.
Sign-in MFA Activity by Factor MFA challenges across the factors the public can sign in with, with each factor’s share.
Sign-in Factor Share of Successes Each sign-in factor’s share of successful second factors, including passkey share.
SMS Code Entry Rate Share of SMS codes sent that someone entered correctly.
Sign-up Email Verification Rate Share of email code entries that succeeded, almost all of them at sign-up.
Sign-up Email Code Speed How fast sign-up email codes are entered: codes entered and the median seconds per day.
No matching items