Attribution Tracking

Add your tags to Engine leads for attribution and reporting.

Format your tags

Every integration type uses {key} & {value} pairing

• {key}: Your identifier, e.g. clientId or subId

• {value}: The real alphanumeric value for that specific click, e.g. 8f3a2b1c9d

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.

---

Attribution Guides by Integration

Partner Page Embed Affiliate Link Native API Mobile SDK

Partner Page

Quick reference

Send via: URL query parameters

First tag: Start with ?

More tags: Separate each tag with &

Format & Example

Engine URL

<moneylion.com/network/channel/zone/?tag.clientId=abc&tag.subId=def&tag.subId1=xyz>    

Example with client tags

<moneylion.com/network/companychannel/loans/search?tag.clientId=8f3a2b1c9d&tag.subId=email-q1&tag.subId1=campaign-42>

1

Start with your Engine URL

• Engine provides the base URL, channel, and zone.

2

Add your tags

• Start with ?. Separate multiple tags with &.

• Add your tags to the end of the URL.

3

Review the completed URL

• Open the finished link.

• Confirm the address bar shows real values, not {} or value.

4

Verify and test

• Confirm every key starts with tag. and matches a supported key.

• Test the link, then ask your Partner Manager to confirm Engine received the values.

---

Web Embeds

Quick reference

Send via: HTML attribute string

First tag: Do NOT use ?

More tags: Separate each tag with &

Format & Example (No Auto-Mount)

<!-- Client tags: replace each {key} and {value} -->
<moneylion-{product} tags="tag.{key1}={value1}&tag.{key2}={value2}">

<!-- Engine script -->
<script
  async
  src="https://www.moneylion.com/network/{channel}/{zone}/web-component/credit-cards-search/index.js"
></script>
<!-- Client tags -->
<moneylion-credit-cards-search
  tags="tag.clientId=8f3a2b1c9d&tag.source=email"
></moneylion-credit-cards-search>

Format & Example (If Auto-Mount)

<!-- Engine script and client tags -->
<script
  async
  src=".../web-component/{product}/index.js"
  data-embed-type="auto-mount"
  data-tags="tag.{key1}={value1}&tag.{key2}={value2}"
></script>

<!-- Engine script and client tags -->
<script
  async
  src="https://www.moneylion.com/network/{channel}/{zone}/web-component/lending-search/index.js"
  data-embed-type="auto-mount"
  data-tags="tag.clientId=8f3a2b1c9d&tag.source=email"
></script>

1

Find your product tag

• Without Automount: Find your moneylion-{some-product} tag.

• With Automount: Use your product’s web-component script URL

2

Add the tag attribute

Do not use ?. Separate multiple tags with &.

3

Review the tag attribute

Confirm every key starts with tag. and uses a supported key.

4

Verify and test

• Confirm tags use the tag. prefix and are separated with & (no ? inside the attribute).

• Confirm you used tags on the custom element, or data-tags on an auto-mount script.

• Load the embed, complete a test lead, then ask your Partner Manager to confirm the values were received.

---

Affiliate Link

Quick reference

Send via: URL query parameters First query parameter: Start with ? More parameters: Separate with & Client tags: Start every key with tag. Limit: Engine keeps up to five tag.* parameters

Format & Examples

Client tag parameters

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

Destination URL with client tags

<offers.moneylion.com/channelTrackingOfferRedirects/{subAccountUuid}/{offerUuid}?tag.clientId=8f3a2b1c9d&tag.subId=email-q1>

If the URL already has query params, start with & instead of ?:

Append client tags

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

Destination URL with existing parameters

<offers.moneylion.com/channelTrackingOfferRedirects/{subAccountUuid}/{offerUuid}?partnerUserId=user-1&tag.clientId=8f3a2b1c9d&tag.subId=email-q1

Example

1

Start with your tracking link

• Use your tracking or redirect link.

2

Add your tags

• Add ?tag.clientId=c1&tag.source=email> to the end

• Use your tracking platform's macro when it supplies a click value.

3

Review the completed URL

• Click the link.

• Confirm the resulting URL contains a real value, not a macro or {}.

4

Verify and test

• Confirm every key starts with tag. and appears on the Engine destination URL.

• Click the link and confirm macros resolved to real values (not {}).

• Ask your Partner Manager to confirm the values were received.

One thing that's different:

On a Partner Page, your system usually already knows the real value.

On an Affiliate Link, your affiliate/ad-tracking platform (Everflow, HasOffers/TUNE, CAKE, Impact, etc.) fills it in at the moment of the click, using that platform's own macro. See below

Third-Party Tracking or Redirect Platform

1. Open your offer setup in your tracking platform (Everflow, HasOffers/TUNE, CAKE, Impact, etc.).

2. Find the field called "Destination URL," "Offer URL," or "Tracking URL."

3. Set it to end with tag. + your key name + your platform's click-ID macro:

   ?tag.subId2={your_platforms_click_id_macro}

4. Confirm it worked: click your own tracking link (or use your platform's link tester). The resulting URL should show tag.subId2= followed by a real, unique value:

   ?tag.subId2=8f3a2b1c9d4e

---

Native API Integrations

Quick reference

Keys: Use bare supported keys Values: Send each value in a string array Do not use: The tag. prefix

Format & Example

"clientTags": {
  "{key1}": ["{value1}"],
  "{key2}": ["{value2}"]
}

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

1

Add the clientTags object

• Add clientTags to the top level of your request body.

2

Add one value per key

• Give each key an array with one value. Use separate keys for multiple tags.

3

Review your request

• Use supported bare keys. Do not add the tag. prefix.

• Confirm every value is real, non-empty, and inside a string array.

4

Verify and test

• Confirm clientTags is on the lead request body with bare keys (no tag. prefix).

• Confirm each value is a string array.

• Submit a test lead, then ask your Partner Manager to confirm the values were received (or check GET Lead Client Tags).

More info: API Reference for the full request body, GET Lead Client Tags for reading tags back out.

---

Mobile SDK Integrations

Quick reference

Keys: Use bare supported keys Values: Send each value in a string array Do not use: The tag. prefix

Format & Examples

React Native

1. Add clientTags as a prop on <EngineSDK>.

2. Give each key a string array.

clientTags={{ clientId: ["client1"], trafficSource: ["email"] }}

Flutter

1. Add clientTags on the top-level EngineSDK widget.

2. Use a Map<String, List<String>>.

clientTags: { "clientId": ["client1"], "trafficsource": ["email"] }

Kotlin

1. Pass clientTags into the EngineSDK constructor.

2. Use Map<String, List<String>>.

clientTags = mapOf(
  "clientId" to listOf("client1"),
  "trafficSource" to listOf("email"),
)

Swift

1. Add clientTags on EngineSDKConfig.

2. Use [String: [String]].

clientTags: [
  "clientId": ["client1"],
  "trafficSource": ["email"],
]

1

Add clientTags

• React Native: add clientTags as a prop on <EngineSDK>.

• Flutter: add clientTags on the top-level EngineSDK widget.

• Kotlin: pass clientTags into the EngineSDK constructor.

• Swift: add clientTags on EngineSDKConfig.

2

Set your tag values

• React Native: give each key a string array. Use separate keys for multiple tags.

• Flutter: use a Map<String, List<String>>. Give each key one value per list.

• Kotlin: use a Map<String, List<String>>. Give each key one value per list.

• Swift: use a [String: [String]] dictionary. Give each key one value per array.

3

Review your configuration

• Use supported bare keys. Do not add the tag. prefix.

• Confirm every value is real, non-empty, and inside a string array.

4

Verify and test

• bearerToken, personalInformation, and clientTags are all set

• Tag values are unique/easy to find (e.g. sdk-test-001)

• SDK launches and the embed loads

• You complete a test lead

• Tags show up in reporting with bare keys (clientId, not tag.clientId)

• Values match what you sent

Client tags are only sent on the prefill path.

Across React Native, Flutter, Kotlin, and Swift, that means bearerToken plus personalInformation must be provided. Without those, the SDK opens the default embed URL and does not attach clientTags.

• Send prefill as separate named fields on the SDK (personalInformation, loanInformation, etc.).

• Legacy prefilledData deprecated July 2026