Pre-Populating Existing Customer Data

Partner Pages and Embeds support pre-populating select fields on the application form, which is useful when you already have that info on hand for that user, or want the front-end to default to particular values.

How to Implement Pre-pop Fields (for Either Hosted Integration Type)

Regardless of the implementation type (Partner Page vs Embed), we support pre-pop for certain non-PII fields to decrease UX friction and increase app submit rates. Fields can be pre-populated by adding query parameters to the respective URL in the below format*:

?app.key_1=value_1&app.key_2=value_2

*The first query parameter appended at the end of a path should be denoted with a question mark (?); all following params should be denoted with an ampersand (&).

Where to Place Pre-pop Fields (Different by Hosted Integration Type)

For example, to add a default Requested Loan Amount to a Partner Page, append the param to the end of the URL path:

https://fiona.com/partner/fiona-loans/loans?app.loanAmount=10000

To add a default amount to an Embed, append the param to the end of the src string in the <iframe> tag:

<div>
    <script>...</script>
    <iframe class=... src='{provided_url}?app.loanAmount=10000'></iframe>
</div>

Supported Client Tag Keys

The following is a list of params that can be added to the URL:

*These fields will be overwritten if the user’s location is detected

Last updated