Ctrlk
API ReferenceControl Center
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Credit Cards Marketplace

How to get started with a Partner Page integration for Engine's Credit Cards Marketplace.

Standard Partner Page Integration

Partner Page URL Syntax & Components

All Partner Pages utilize custom URLs and tracking to ensure all transactions are correctly attributed. To integrate the Partner Pages on your website, you would place the following URL on your page in your desired location.

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

https://moneylion.com/network/{channel}/{zone}/

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

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

If implementing using an anchor <a> tag, you may consider having the link open in a new tab with a target="_blank" attribute:

<a href="https://moneylion.com/network/{channel}/{zone}/" target="_blank">Desired Link Text</a>

Different Partner Page Experiences

Note that the screenshots in this section reflect a Personal Loans Partner Page, not a New Marketplaces Partner Page.

Marketplace Entrypoints

There are two different experiences for users to start the initial step:

  • Explore Page

    • Displays static preview offers from Engine by MoneyLion’s network of financial institution partners as the first step of the user experience.

    • Offers can be sorted by credit rating, ZIP code, loan purpose, and amount. Users can click into a static offer to begin filling out the form.

    • Preview Step is recommended for partners who want to utilize offer values and financial institution brand equity to encourage users to enter the flow.

  • Search Funnel

    • Displays the first question of the form (i.e., “Why do you need a loan?”).

    • Using the Form Step, users can begin filling out the form immediately.

    • Form Step is recommended for partners who want to maximize funnel efficiency and minimize the number of clicks in the user flow.

Preview Step
Form Step

The Results Page

  • After completing and submitting the form, users are shown offers for which they are pre-approved or pre-qualified.

  • Users can sort offers in a variety of ways, including by APR, term length, and “recommended,” the latter of which relies on Engine by MoneyLion’s Rec Score to rank offers by likelihood of conversion.

Selecting the Auto-Redirect Option

  • Auto-Redirect is an option that allows users who receive pre-approved or pre-qualified offers to be automatically redirected to the top offer (powered by Engine by MoneyLion’s Rec Score) displayed on their Results Page after 10 seconds.

  • Auto-Redirect is recommended for partners who prefer to streamline the user experience.

Static Offers (ITA) Explore Partner Pages

LogoExplore Credit Cards | CardCriticsCardCritics

Prequal Search Partner Pages

LogoSearch Credit Cards | MoneyLionMoneyLion

Co-mingled ITA Explore & Prequal Search Partner Page

LogoExplore Credit Cards | ATM.comMoneyLion

Partner Page Brand Customization

Note that the screenshots in this section reflect a Personal Loans Partner Page, not a New Marketplaces Partner Page.

All Partner Pages can be co-branded with your company logo and colors to deliver a seamless customer journey. The headline is also customizable (with Engine by MoneyLion compliance approval).

Cobrand Example

Client Tags & Prefilling Customer Data

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

Client tags: Used for attribution and reporting (prefix tag)

  • Used to send your own metadata to Engine in order to enrich reporting and attribution with Engine data

Prefill customer data: Used as a query string parameter to send non-PII information (prefix app)

  • 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

How to Implement Client Tags for Reporting & Customer Data Pre-fill

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

To pre-fill customer data fields in a Partner Page, add query string parameters to the respective URL in the following format*:

*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

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

Below are the client tag keys that are currently supported. See Attribution Tracking for more information.

Most common

  • tag.clientId

  • tag.subId

  • tag.subId1

  • tag.subId2

  • tag.campaignId

Also supported

  • tag.agentId

  • tag.clickId

  • tag.deviceId

  • tag.medium

  • tag.sourceId

  • tag.subId3

  • tag.target

  • tag.trafficsource

  • tag.userId

Client tag keys are case-sensitive. subid and subId are separate reporting keys.

Example
Why

❌

?tag.sub1={}&tag.sub2={}

Unsupported tags

❌

?tag.subId1={}&tag.subId2={}

{} is a literal placeholder. Engine stores empty values.

❌

?tag.subId1=value1&tag.subId2=value2

value1 and value2 are literal text, not real click values.

✅

?tag.subId1=8f3a2b1c9d&tag.subId2=4e7c1a92f0

Each key has a real value for that click.

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.

Credit Cards Supported Query Parameters

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

Key
Purpose

app.annualIncome

Annual income (number)

app.firstName

First name

app.lastName

Last name

app.email

Email (valid formatting"

app.primaryPhone

Phone number

(XXX-XXX-XXXX; must be 10 digits or 11 starting with 1)

app.dateOfBirth

Date of birth (mm/dd/yyyy)

app.address1

Address line 1

app.address2

Optional, address line 2

app.city

City

app.state

State (valid state code, e.g. "CA")

app.zipcode

Zipcode

Last updated

Was this helpful?