Optimizing Link conversion

This guide contains tips for optimizing your existing Link implementation to help increase conversion and improve your users’ experiences with Link. If you are new to Link or don’t yet have a working Link integration, see Link overview for instructions on getting started with Link.

To evaluate the impact of changes to your integration, it's a good idea to implement conversion tracking before attempting to optimize conversion. For details, see Tracking Link conversion.

Many different steps can be taken to maximize Link conversion, and the exact impact of these steps will vary for each customer and use case. The recommendations below are provided in general priority order.

Link conversion is highest when users have the right expectations set going into Link. Your app should explain why you use Plaid, the benefits for the user of connecting their account, and that the user's information will be secure. It should also set the user's expectations around what information they will need to provide during the Link flow. Plaid should be configured as the default experience. For more details, including visual examples, see Pre-link messaging for optimizing conversion.

The returning user experience (RUX) allows customers at some banks who have used Plaid before to have a streamlined experience when using the Link flow. If you collect phone number data for your users and have it available when they enter the Link flow, implementing RUX will increase conversion for eligible users. For more details, see Returning user experience.

In general, initializing with a minimal set of products will both increase conversion and reduce your costs, although it may result in higher latency in your app's UI or require backup anti-fraud measures. For more details, see Choosing when to initialize products.

While supporting mobile app-to-app impacts only a small number of banks (currently only Chase), the impacts on conversion for eligible users is very large, as app-to-app flows can allow users to authenticate with biometrics instead of a username and password. For iOS, supporting app-to-app requires creating an apple-app-site-association file to support universal links. On Android, supporting app-to-app requires registering your Android package name. For more details, see the OAuth Guide.

While the vast majority of users can use Plaid's default Auth flows, some users, especially those at smaller banks and credit unions, have accounts that do not support those flows. Implementing micro-deposit-based Auth flows will increase conversion by allowing these users to link their accounts. For more details, see Auth coverage.

For apps with multi-language experiences, custom profiles improve conversion by allowing you to display Link in your user's preferred language. Calling /link/token/create with the country parameter set to your user's specific country, rather than all countries your app supports, will allow Link to show a more accurately targeted list of institutions. For Auth customers, calling /link/token/create with country set to just US is also required to enable the conversion-maximizing Instant Match and micro-deposit based Auth flows.

Plaid allows you to customize certain aspects of the Link UI. Customizing these in a way that matches your app -- for example, uploading your organizations's logo to be used on the Link consent pane or matching your brand colors can increase conversion. For more details, see Customizing Link.