Banking (Deposits) Marketpalce

Standard Embed Implementation

Engine's embed code can be placed in any order within your page, but for optimal user experience we recommend placing the script tag within the same div where the content is being rendered.

Basic Embed Syntax

PLEASE NOTE: Your Engine representative will provide you with your specific code snippet. Do not try to reproduce from the sample snippet outlined below.

<script
  async
src="https://www.moneylion.com/network/{channel}/{zone}/web-component/{component-name}/index.js"
  data-embed-type="auto-mount"
></script>

This is a representative example of what our embed code looks like, and contains placeholders as defined below. Placeholders and will be replaced with precise values in the embed code provided to you.

Embed Components

• Channel: placeholder that will be replaced with precise values in the embed code provided to you.

• Zone: placeholder that will be replaced with precise values in the embed code provided to you.

• Component Name: corresponds to the specific product or Engine experience type that's being rendered.

• data-embed-type: enables Engine's auto-mount functionality; without this attribute, the component will not render.

  • Acceptable Value: "auto-mount"

Customization & Auto Sizing

The web component loads iFrame and will automatically fill the container. Embeds are rendered wherever you include our HTML tag on your page and will responsively scale to fill the space available to it.

Banking Specific Syntax

Engine's banking embed requires an additional tag to be included at the end of the standard script to be able to mount correctly: <moneylion-banking></moneylion-banking>

Full sample embed script looks like the following:

<script
  async
src="https://www.moneylion.com/network/{channel}/{zone}/web-component/banking/index.js"
></script><moneylion-banking
tags="tag.clientId=c1&tag.source=email&app.providedCreditRating=excellent&app.zipcode=93105\"
></moneylion-banking>

Component Names

• /web-component/banking/: A full application-style flow where consumers browse and compare banking deposit offers on your site, in a block that feels like part of your page instead of redirecting them elsewhere. It keeps the experience focused on exploring rates and products in context, so users stay in your environment while they shop for savings-related accounts.

Banking Embed Demo

Explore Savings | FionaFiona

Banking Experience Data Prepopulation

Engine's Banking experience does not use tags for the purpose of prepopulating consumer data like other Engine marketplaces do. This is because Banking doesn't require the same degree of fidelity when it comes to user information.

The one piece of consumer information that can be changed is zipcode. Instead of prepopulating with tags, Engine leverages programmatic geolocation-based information to prepopulate zipcode - the precedence is as follows:

• An explicit ZIP filter (if defined)

• The visitor's geolocation-derived zipcode (this is the default behavior for Engine embeds)

• A fallback zipcode (10001), only if geolocation is unavailable)

Implementing Client Tags for Reporting

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

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

Sample Implementation

<script
  async
src="https://www.moneylion.com/network/{channel}/{zone}/web-component/banking/index.js"
></script><moneylion-banking
tags="tag.clientId=c1&tag.source=email\"
></moneylion-banking>

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

Supported Client Tag Keys

Client tag keys are matched exactly, including case. For example - subid and subId are stored as separate tags and will appear as separate keys in your reporting.

Please send each key with consistent casing across all requests, and use the exact spelling shown above.

Below are the client tag keys that are currently supported:

• agentId

• campaignId

• clickId

• 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.

Embed Best Practices & Troubleshooting

Component Not Showing

1. Check the required attribute:

   1. Make sure data-embed-type="auto-mount" is present

2. Check browser console:

   1. Open developer tools and look for error messages

Loading Too Slowly

1. Make sure async attribute is present on the <script> tag

   1. This prevents block page load