About
This cookbook documents commonly used CanadaLogin metrics, including their definitions, plain-language alternate names, calculation logic, and example SQL queries.
The cookbook is organized by data source:
- IBM Verify
- Call Centre
- Platform
- Jira (PSOM)
- Google Analytics
- Cross-source / interpretive metrics (planned)
Each metric includes:
- a description of what it measures and when to use it
- plain-language alternative names
- the calculation logic
- an example query, shown in both SQL and R
- interpretation notes, where relevant
The companion Data Catalog describes the underlying tables that these metrics are calculated from, field by field.
All Metrics
| Metric | Description |
|---|---|
| Abandonment Rate | Share of accepted calls abandoned before an agent answered. |
| All MFA Activity by Factor | MFA challenges by factor, with each factor’s share of the total. |
| Answer Rate | Share of accepted calls answered by an agent. |
| Applications per Credential | Average number of distinct applications one credential reaches. |
| Authentication Events | Total authentication events, successful and failed. |
| Authentication Success Rate | Share of authentication attempts that succeeded, across CanadaLogin. |
| Average Call Length | Average length of answered calls. |
| Average Daily SSO Events | Average SSO events per day for each application. |
| Average Daily Users | Distinct users on a typical day over a reporting window. |
| Average Delay | Average wait before a call is answered. |
| Average Handle Time | Average agent time per call, including after-call wrap-up. |
| Call Topic Share | Each call topic’s share of all topic records. |
| Calls Accepted | Calls the call centre accepted in a reporting period, excluding staff test calls. |
| Calls Answered | Number of calls agents answered in a reporting period. |
| Calls by Topic Category | Calls about each topic or category, as a share of calls, not of topic records. |
| Calls per Active User | Call volume relative to the active user base, comparable across weeks. |
| Completed Sign-In Sessions (Estimated) | Estimated number of sign-ins that got all the way through the flow. |
| Cumulative Unique Users | Distinct users who signed in this month or this calendar year. |
| 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. |
| Dwell Time | How long readers stay on each Signal Check edition and dashboard, as a drop-off curve of page views. |
| Escalation Rate | Share of call centre calls escalated to Partner Success and Operations. |
| Escalations to PSO | Calls the call centre escalated to Partner Success and Operations. |
| MFA Challenges | Second-factor challenges issued at sign-in 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. |
| Mean Time to Resolution | Average minutes from incident detection to resolution. |
| Multi-Service Users | Share of users who have signed in to two or more public services. |
| New Accounts and Idle Account Rate | Accounts created per day, and the share that never reached a partner service. |
| Outage Events | Individual site outages: when a site went down, when it recovered, and the status code. |
| Peak Daily Unique Users | Highest number of unique users on any single day. |
| SLA First-Response Breach Rate | Share of PSOM tickets that missed the time-to-first-response SLA. |
| SLA PSO Time-to-Done Breach Rate | Share of PSOM tickets that missed the PSO time-to-done SLA. |
| SLA Time-to-Done Breach Rate | Share of PSOM tickets that missed the time-to-done SLA. |
| SMS Code Entry Rate | Share of SMS codes sent that someone entered correctly. |
| SSO Events by Application | Total SSO events for each application. |
| SSO Success Rate by Application | Share of SSO events that succeeded, by application. |
| Second-factor Attempts | Second-factor outcomes at sign-in, successful or failed, in a reporting period. |
| Service Level (Answered Within 60s) | Share of calls answered within 60 seconds. |
| Sign-Ins per Active User (Estimated) | Estimated sign-ins per user in a calendar month, among users who signed in. |
| Sign-in Factor Share of Successes | Each sign-in factor’s share of successful second factors, including passkey share. |
| Sign-in MFA Activity by Factor | MFA challenges across the factors the public can sign in with, with each factor’s share. |
| Sign-up Email Code Speed | How fast sign-up email codes are entered: codes entered and the median seconds per day. |
| Sign-up Email Verification Rate | Share of email code entries that succeeded, almost all of them at sign-up. |
| Signal Check Views | Page views of each Signal Check in its first 14 days, and against a typical Signal Check at the same age. |
| Site Response Time | Average HTTP response time for each monitored site, over rolling windows. |
| Site Uptime | Rolling-window uptime percentage for each monitored site. |
| Task Success Rate | Share of users who started a task and reached its finishing point, from GA4 funnels. |
| Tickets Opened, Closed, and Open | PSOM tickets opened and closed each week, the queue at the end of it, and how long tickets stay open. |
| Tickets by Priority | PSOM tickets in the latest snapshot, by priority. |
| Tickets by Status | PSOM tickets in the latest snapshot, by workflow status. |
| Top 10 Call Topics | The ten most common call topics. |
| Weekly Ticket Volume | Number of PSOM tickets in each Monday snapshot. |
| Where Sessions Started | Sessions that included a Signal Check or dashboard, by where the session started. |
How to Use
Use this cookbook as a reference when building dashboards, reports, briefing materials, or ad hoc analyses.
For each metric, confirm:
- Does it measure what I think it does?
- What table and columns are used?
- Should I apply any filters?
- Is this metric a count, a rate, a cumulative value, or an average?
Conventions
All example SQL targets Amazon Athena (Trino dialect). Constructs such as DATE '...' literals, ROW_NUMBER() OVER (...), and REGEXP_REPLACE follow Trino semantics.
In reporting language, prefer sign-in over login. The underlying IBM Verify field may be called total_logins, but “sign-ins” is preferred (and often enforced) when talking about CanadaLogin.
Where applicable, internal CanadaLogin components are excluded from external-facing adoption reporting. The exclusion list is not maintained here: it is derived from rp.service.is_internal at query time. See the internal CanadaLogin components note in notes.qmd for the pattern.
Scope
This cookbook covers calculated metrics. Metrics already present in a table without any calculation do not need to be included, although they can be if they need clarification.
It covers every source listed above. Cross-source metrics comparing sign-in activity and call volume are planned.