Passkey Adoption Report
The Passkey Adoption Report helps you understand how users authenticate in your application. It visualizes the login flow, showing how many users attempt passkey login, how many fall back to other methods, and the success or failure along each path. You can use this report to track adoption progress and identify opportunities to improve your passkey onboarding experience.

Where to Find It
You can access the adoption report from your dashboard:
Applications → [Your App] → Overview → Adoption Report
The report is available alongside the General, Usage, and Latency tabs.
Reading the Flow Chart
The flow chart helps you understand how users move through passkey authentication and where you may need to improve the integration.
It highlights adoption, platform support, user behavior, and drop-offs.
Adoption
Measure how many users choose passkey login versus fallback authentication logins.
Use Case: Track whether your passkey integration is being adopted.
Support
Check the split between passkey supported and unsupported devices.
A high unsupported rate suggests gaps in platform or device readiness.
Behavior
Review login initiation paths to understand how users start the flow:
- Autofill – Sign in directly using passkey autofill.
- Username Provided – Provide a username to LoginID and sign in with a passkey signin without autofill.
- Password Manager – Use an external password manager (e.g., 1Password, BitWarden) to sign in with a passkey.
- Other – Use alternative passkey signin methods such as cross-platform or hardware/security keys.
Use Case: Helps you understand which initiation patterns to optimize or test against.
Drop-offs
Review Outcomes to spot friction points:
- Passkey Appended – Successfully created passkey (first or additional on another authenticator).
- Passkey Already Exists – User attempted to create a passkey that already exists on this authenticator.
- Implicit Abort – Flow ends due to a passkey error.
- Explicit Abort – User declines to add a passkey before attempting creation.
Use Case: High abort rates may indicate confusing UI.