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

Auto Insurance Marketplace

How to get started with a Partner Page integration for Engine's Auto Insurance 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 Auto Insurance Experiences

This feature currently requires Partner Manager involvement to launch – contact your assigned Partner Manager for support.

Short Form Experience

Client Tags & Pre-filling Customer Data

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

Tags vs. Pre-fill

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

For Auto Insurance specifically, please use subId1 for click ID & subId2 for placement id

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*:

*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 pre-populated 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.

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.

Auto Insurance Supported Query Parameters

Engine's Auto Insurance marketplace accepts the following parameters and values for customer data pre-population purposes:

Field
Parameter
Acceptable Values

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

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

Military Status

app.is_military

Boolean (true/false)

Home Owner Status

app.is_home_owner

Boolean (true/false)

The fields defined below are only used for Engine's legacy Auto Insurance experience (likely anything integrated prior to August 2026).

Age Range

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

Multiple Vehicle Status

app.has_multiple_vehicles

true

Insured Status

app.is_currently_insured

true

Last updated

Was this helpful?