# Password manager Dashlane sees 70% increase in conversion rate for signing-in with passkeys compared to passwords

Dashlane is a password management tool that provides a secure way to manage
user credentials, access control, and authentication across multiple systems
and applications. Dashlane has over 18 million users and 20,000 businesses in
180 countries. It's available on Android, iOS, macOS, Windows, and as a web app
with an extension for Chrome, Firefox, Edge, and Safari.

## The opportunity

Many users choose password managers because of the pain and frustration of
dealing with passwords. While password managers help here, the fact remains
that one of the biggest issues with passwords are security breaches. Passkeys
on the other hand bring passwordless authentication with major advancements in
security.

[Passkeys](https://developers.google.com/identity/passkeys) are a simple and secure authentication technology that enables
signing in to online accounts without entering a password. They cannot be
reused, don't leak in server breaches of [relying parties](https://developers.google.com/identity/passkeys/developer-guide#anatomy_of_a_passkey_system), and protect users
from [phishing attacks](https://developers.google.com/identity/passkeys#security-considerations). Passkeys are built on open standards and work on all
major platforms and browsers.

As an authentication tool, Dashlane's primary goal is to ensure customers'
credentials are kept safe. They realized how significant the impact of
passkeys could be to the security of their users and adapted their applications
to support passkeys across devices, browsers, and platforms. With [passkey support](https://www.dashlane.com/passkeys)
they provide users a secure and convenient access with a
phishing-resistant authentication method.

## Implementation

Passkeys as a replacement for passwords is a relatively new concept and to
address the challenge of going from a familiar to an unfamiliar way of logging
in, the Dashlane team considered various solutions.

On the desktop web they implemented [conditional UI](https://developer.chrome.com/blog/webauthn-conditional-ui/) support through a browser
extension to help users gracefully navigate the choice between using a password
and a passkey to log into websites that support both login methods. As soon as
the user taps on the username input field, an autofill suggestion dialog pops
up with the stored passkeys and password autofill suggestions. The user can
then choose an account and use the device screen lock to sign in.

> [!NOTE]
> **Note:** To learn how to add passkeys support with conditional UI to your web app check out [Create a passkey for passwordless logins](https://web.dev/passkey-registration/) and [Sign in with a passkey through form autofill](https://web.dev/passkey-form-autofill/).

On Android, they used the [Credential Manager API](https://developer.android.com/training/sign-in/passkeys) which supports multiple
sign-in methods, such as username and password, passkeys, and federated
sign-in solutions (such as Sign-in with Google) in a single API. The Credential
Manager simplifies the development process and it has enabled Dashlane to
implement passkeys support on Android in 8 weeks with a team of one engineer.

<br />

<br />

> [!NOTE]
> **Note:** If you are a credential provider, such as a password manager app, check out the guide on how to integrate [Credential Manager with your credential provider solution](https://developer.android.com/training/sign-in/credential-provider).

## Results

Data shows that users are more satisfied with the passkey flows than the
existing password flows.

The conversion rate is 92% on passkey authentication opportunities on the web
(when Dashlane suggests a saved passkey for the user to sign in), compared to a
54% conversion rate on opportunities to automatically sign in with passwords.
That's a 70% increase in conversion rate compared to passwords--a great sign
for passkey adoption.

![Double-line graph showing the percent change of authentication and registration actions on passkeys over a seven month period.](https://developers.google.com/static/identity/passkeys/case-studies/dashlane/image/evolution-dashlane-passkey.png)


![Passkey prompt for signing in.](https://developers.google.com/static/identity/passkeys/case-studies/dashlane/image/password-sign-in-prompt.jpg) *Password sign-in prompt.*   
![The Podcasts app's settings menu in the 'General' section where the 'Refresh Podcasts' option is set to 'Every Hour'.](https://developers.google.com/static/identity/passkeys/case-studies/dashlane/image/passkey-sign-in-prompt.jpg) *Passkey sign-in prompt*   
The conversion rate here refers to user actions when they visit websites that support passkeys. If a user attempts to register or use a passkey they will see a Dashlane dialog appear on Chrome on desktop. If they proceed and create new or use an existing passkey it is considered a success. If they dismiss the dialog or cancel passkey creation, it's considered a failure. The same user experience flow applies to passwords.

<br />

Dashlane also saw a 63% conversion rate on passkey registration opportunities
(when Dashlane offers to save a newly created passkey to the user's vault)
compared to only around 25% conversion rate on suggestions to save new
passwords. This indicates that Dashlane's suggestions to save passkeys are more
relevant and precise than the suggestions to save passwords.
![Dashlane prompt asking to save passkey in Dashlane from username field](https://developers.google.com/static/identity/passkeys/case-studies/dashlane/image/save-passkey-prompt.jpg) Save passkey prompt.

<br />


![Dashlane prompt asking to save password from password field.](https://developers.google.com/static/identity/passkeys/case-studies/dashlane/image/save-passkey-prompt-2.jpg) *Save password prompt.*   

<br />

Dashlane observed an acceleration of passkey usage with 6.8% average weekly
growth of passkeys saved and used on the web.

![Line graph showing positive trending percent of active users that performed a passkey related event, out of users having ever interacted with a passkey over 8 months.](https://developers.google.com/static/identity/passkeys/case-studies/dashlane/image/user-passkey-events.png)

## Takeaways

While passkeys are a new technology that users are just starting to get familiar
with, the adoption rate and positive engagement rates show that Dashlane users
are more satisfied with passkey flows than the existing password flows.

Dashlane tracks and investigates all passkey errors and says that there haven't
been many. They also receive few questions from customers around how to use or
manage their passkeys. This can be a sign of an intuitive user experience,
clear help center documentation, a tendency of passkey users today already
being knowledgeable about passkeys, or some combination of these factors.

"Staying up to date on developments in the market landscape and industry,
anticipating the potential impact to your customers' experience, and being
ready to meet their needs can pay off. Thanks in part to our rapid
implementation of the Credential Manager API, customers can rest assured that
they can continue to rely on Dashlane to store and help them access services,
v no matter how authentication methods evolve."

--Rew Islam, Director of Product Engineering and Innovation at Dashlane