Pre-Populating Existing Customer Data

Engine Embeds support the ability to add certain tags with varying use cases, which are outlined in this section.

Use Cases for Client Tags

• Prefilling customer data for certain non-PII fields

  • Decreases friction in the user experience and increases application submission rates

  • Useful when you already have that info on hand for that user, or want the front-end to default to particular values

• Channel Partner Reporting

How to Implement Client Tags for Reporting & Customer Data Prefill

To add client tags in an embed, use the following syntax in the data-tags attribute within the embed script:

tag.key_1=value_1&tag.key_2=value_2

To prerefill fields in an embed, use the following syntax in the data-tags attribute within the embed script:

app.key_1=value_1&app.key_2=value_2

Sample Implementation

"<script 
      async src=\"https://www.moneylion.dev/network/{channel}/{zone}/web-component/generic-offers/index.js\" 
      data-tags=\"tag.clientId=c1&tag.source=email&app.providedCreditRating=&zipcode=\"
      data-embed-type=\"auto-mount\" 
></script>"

In the above example, clientId and source are available as tags for reporting purposes and the embed "credit rating" and "zipcode" fields will be prepopulated when the embed is rendered.

Supported Client Tag Keys

These are the keys that are currently fully supported across all Engine embed types. Please note that the keys below are case-sensitive:

• agentId

• campaignId

• clientId

• deviceid

• medium

• sourceId

• subid

• subid1

• subid2

• subid3

• target

• trafficsource

• userid

If a different key is needed, please reach out to your Partner Manager - we may be able to accommodate, but adding nonstandard keys will increase the time it takes Engine to report Client Tag values back to you and is therefore not recommended.

Engine Partner Pages support the ability to add certain tags with varying use cases, which are outlined in this section.

Client Tag Use Cases

• Prefilling Customer Data

  • Decreases friction in the user experience and increases application submission rates

  • Useful when you already have that info on hand for that user, or want the front-end to default to particular values

• Channel Partner Reporting

How to Implement Client Tags for Reporting & Customer Data Prefill

To add client tags to a Partner Page integration for the purpose of enhanced reporting, add query string parameters to the respective URL in the following format*:

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

To prefill customer data fields in a Partner Page for the purpose of decreased friction in user experience, add query string parameters to the respective URL in the following format*:

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

*The first query parameter appended at the end of a URL/path should start with a question mark ?; all subsequent parameters should start with an ampersand &.

Sample Partner Page URL

https://moneylion.com/network/{channel}/{zone}/search?app.loanAmount=10000&tag.clientId=1234

In the above example, clientId is available as a tag for reporting purposes and the partner page "loan amount" field will be prepopulated with the value of "$10,000" for the consumer when the page is rendered.

Supported Client Tag Keys (for any integration type)

These are the keys that are currently fully supported across all Engine partner page types. Please note that the keys below are case-sensitive:

• agentId

• campaignId

• clientId

• deviceid

• medium

• sourceId

• subid

• subid1

• subid2

• subid3

• target

• trafficsource

• userid

If a different key is needed, please reach out to your Partner Manager - we may be able to accommodate, but adding nonstandard keys will increase the time it takes Engine to report Client Tag values back to you and is therefore not recommended.