Appendix E: Appending Client Tags to Leads Posted to Engine

Hosted Integrations (Partner Pages and Embeds) and Native API Integrations all support adding your unique Client Tags to track performance of specific campaigns or users. All Client Tag data is attributed to the lead level. The instructions here are the same regardless of the product vertical, as they all use the same underlying technical infrastructure.

Hosted Integrations

How to Structure Client Tags (for Either Hosted Integration Type)

Regardless of the integration type, Client Tags can be added via query parameters at the end of the respective URL in the below format*:

tag.{key1}={value1}&tag.{key2}={value2}

where the {key} represents your general identifier, e.g. clientId or subId, and {value} represents the value for that specific individual, e.g. "client1" or "client2."

Where to Place Client Tags (Different by Hosted Integration Type)

In the below examples, tag.clientId=c1 means the lead will be stored with a clientId of "c1", and a source of "email", which can now be provided in reporting.

Partner Page

To add Client Tags in a Partner Page, append the parameters to the end of the {provided_moneylion_url} as follows:

{provided_moneylion_url}?tag.clientId=c1&tag.source=email

Embed

To add Client Tags in an Embed, use the following syntax in the tags attribute on the opening custom moneylion-{some-product} tag as follows (with each key preceded by tag.):

tags="tag.clientId=c1&tag.source=email"

Native API (Build Your Own)

Client Tags for Native API Integrations can be added by including a clientTags attribute at the top level of the request body, where the value is an array of strings. We strongly recommend only including one element per array for ease of reporting/attribution - if you want two separate tags, include the second tag under a different key. There is no limit to the number of keys in the clientTags object. See the following for an example:

{   
    "personalInformation": {...},
    "financialInformation": {...},
    "clientTags": {
        "clientId": ["client1"],
        "trafficsource": ["email"],
        "campaignId": ["campaign1"]
    }
}

More Information

See the sample request in our API Reference for more info on the request body when posting leads to Engine's API.

See our GET Lead Client Tags endpoint for information on attributing lead analytics to your own client tags

Supported Client Tag Keys (for any integration type)

These are the keys that are currently fully supported. 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. Please note that the keys below are case-sensitive.

• agentId

• campaignId

• clientId

• deviceid

• medium

• sourceId

• subid

• subid1

• subid2

• subid3

• target

• trafficsource

• userid