Cross-Device Authentication Completion Rate
Cross-Device Authentication Completion Rate measures how reliably desktop-to-phone passkey flows finish when the credential is not available locally. This is a critical usage benchmark because cross-device friction can block otherwise ready users from turning credential coverage into passkey logins.
How often desktop-to-phone passkey logins finish
Cross-Device Authentication (CDA) happens when a user's passkey is on a different device than the one they're logging in on, typically a desktop browser scanning a QR code with their phone. This benchmark measures how often that flow finishes once the user opts into it. Same-device flows and mobile-only flows are excluded.
| Platform | CDA completion |
|---|---|
| Windows web 1 | 60%–78% |
| macOS web 2 | 66%–86% |
Completion = the user opened the CDA prompt on desktop and finished the passkey ceremony on their phone.
CDA Completion by Login Context
Identifier-first is the new-device / unrecognized-device case where desktop CDA is most exposed. Same-device nudges are continuity flows and complete much more reliably.
| Platform | Same-device nudge | Identifier-first |
|---|---|---|
| Windows web | 79%–98% | 52%–67% |
| macOS web | 83%–98% | 59%–76% |
Android In-depth Data: Google, Authenticate 2025
Google's Authenticate 2025 numbers are the available in-depth Android drop-off view: user cancellations and device availability are a different problem from credential-not-found or connection failures.
| Flow step | Rate |
|---|---|
| Starting page -> browser prompt | 48% |
| Browser prompt -> QR code scan | 29% |
| QR code scan -> authenticator success | 64% |
| Authenticator success -> user signed in | 89% |
| Android authenticator failures | Share |
|---|---|
| User cancellations | 44% |
| Credential not found | 32% |
| Connection issues | 17% |
| Other | 6.8% |
- When asking if CDA should be started, Windows shows a 34% decline branch, most likely because users do not have access to the phone at that moment.
- Equivalent in-depth drop-off data is only available for Android from Google, Authenticate 2025; macOS is therefore reported as a desktop CDA completion benchmark without the same Android-style failure taxonomy.
Further Reading
Curated Corbado research and primary references.
- Passkey Device Support Compatibility matrix for cross-device passkey behavior across operating systems, browsers and devices.
- WebAuthn Passkey QR Codes & Bluetooth: Hybrid Transport Deep dive on QR-code initiation, Bluetooth proximity and why CDA behaves differently from local passkeys.
- WebAuthn Cross-Device Authentication: Passkeys via Mobile-First Strategy Mobile-first view of cross-device authentication when the passkey is available on a phone.