Appendix E: Appending Client Tags for Partner Page and Embed Integrations

This page has instructions for appending your own Client Tags to leads coming through Engine's marketplace.

Partner Pages and Embeds 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.

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

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

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:

*The first query parameter for Embeds should not include a question mark ?, but every key/value pair of tags must be separated by an ampersand &

Supported Client Tag Keys

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