Auto Insurance Marketplace
Standard Partner Page Integration
Basic Partner Page URL Syntax
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.
https://moneylion.com/network/{channel}/{zone}/Partner Page 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.
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>Auto Insurance Specific Partner Pages & Demos
This feature currently requires Partner Manager involvement to launch – contact your assigned Partner Manager for support.
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 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
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*:
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*:
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
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.
Auto Insurance Supported Client Tag Keys
Engine's Auto Insurance marketplace accepts the following parameters and values for customer data pre-population purposes:
Date of Birth
app.dateOfBirth
Date string of the format YYYY-MM-DD
Zip Code
app.zipcode
US 5-digit numeric ZIP code, e.g. 10001. No leading/trailing whitespace
Credit Rating
app.providedCreditRating
excellent
good
fair
poor
limited
unknown
Number of Vehicles
app.numberOfVehicles
Integer between 1 and 5
Current Issuer
app.currentIssuer
String issuer name matching the enum values from Engine's API Reference for the Schema AutoInsuranceIssuer
Age Range (legacy)
app.ageRange
AGE_RANGE_18_20
AGE_RANGE_21_24
AGE_RANGE_25_34
AGE_RANGE_35_44
AGE_RANGE_45_54
AGE_RANGE_55_64
AGE_RANGE_65_PLUS
Only insert these values if they are applicable, and set them to true
Military Status
app.is_military
true
Home Owner Status
app.is_home_owner
true
Multiple Vehicle Status (legacy)
app.has_multiple_vehicles
true
Insured Status (legacy)
app.is_currently_insured
true
Last updated
Was this helpful?