Tracking

Capture how users interact with Link.

Overview#

You can track user behavior in Link by including the onUIEvent callback in your Link initialization.

The onUIEvent callback is triggered for specific UI events in Link, and although optional, including this callback can help with troubleshooting as well as optimizing conversion rates.

Callback format#

Add the line below to your Link initialization:

1onUIEvent: (payload) => console.log('onUIEvent', payload),

Callback payload#

The onUIEvent callback returns:

1. The name of the UI-related Event that triggered the callback.
2. A properties object, which can include:
   • deepLink (always) — Whether the user was directly connected to the Item.
   • userId (always) — ID of the user.
   • accountId (conditional) — ID of the user's account.
   • itemId (conditional) — ID of the relevant Item.
   • Event-specific properties (conditional) — See Events below.

Example:

1UIEvent (
2    "name": "mfa - opened",
3    "properties": {
4        "deepLink": false,
5        "userId": "019ac324-91b5-2e5b-dc96-c931e25da1e2",
6        "itemId": "item_123456789",
7        "type": "Login",
8        "mfaType": "sms_code"
9    }
10)

Events#

Intro screen#

Search screen#

Property definitions:

• term — The text entered in the search field.
  
• tab — The tab that was open when the user entered a search term or selected an Item. Ignored for empty (or deleted) search terms. Possible values: Popular, Payroll providers, Employers

Login screen#

Property definitions:

• errorCode — The account connection error relevant to the login screen that occurred. Possible values: auth_required, connection_unavailable, expired_credentials, invalid_auth, invalid_credentials, mfa_cancelled_by_the_user
• errorMessage — The account connection error message shown to the user.

MFA screen#

Property definitions:

• type — Whether MFA occurred during login or a deposit switch. Possible value: Login, DDS
• mfaType — The type of MFA. Possible values: sms_code, email_code, secret_question, email_link_confirmation, otp_code, email_message_confirmation

Success screen#

Account status screen#

Direct deposit opened screen#

Property definitions:

• allocationType — Which type of pay allocation was shown to the user. Possible values: percent, amount, none

Allocation type selection screen#

Direct deposit success screen#

Account error screen#

Property definitions:

• connectionStatus — The connection.status of the Account.
• connectionErrorCode — The account connection error that occurred.
• ddsStatus - The direct_deposit_switch.status of the Account.
• ddsErrorCode - The deposit switching error that occurred.

Link error screen#

Property definitions:

• errorType — The Link error that occurred.

Link closed#

Occurs when the user closes Link from any screen.

Property definitions:

• closeMethod — How Link was closed.
  Possible values:

  • footer_button — Link was closed by the user selecting the Done (re-nameable) button on a final screen.
  • x — Link was closed by the user selecting [X] in the upper-left of the screen.
  • null — Link was closed programmatically via an Argyle SDK, or when the onCantFindItemClicked callback is used, or any other event that causes Link to close.