> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flinks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use a Custom Tag

> You can use custom tags to mark requests or groups of requests. This section will cover what a custom tag is and how to handle tag information.

### Account Selection and Tag

For specific use cases, it is important to know which account the user will want to work with.

For instance, for verifying an account, typically used for money transfers, knowing which account to draw money from is important to avoid NSFs.

<Note>
  <p class="h4">Selected Account Identification</p>

  You can store the information about which account your user has selected by collecting and keeping the `AccountId` along with the `loginId`.
</Note>

Custom tags can be used to mark specific requests or groups of requests according to your own context. For example, if you already have a specific UserId that you want to associate with a loginId, it can be done by using a tag.

<Note>
  <p class="h4">Note:</p>

  Different tags need to be assigned directly in the iframe URL using the "Tag" parameter.
</Note>

<Warning>
  <p class="h4">Never include personal information (PII) in tags</p>

  Tag values are passed through URLs, logs, and webhook payloads. They are **not** a secure channel. Do not include any PII, such as:

  * Email addresses
  * Phone numbers
  * Full names
  * Dates of birth
  * Government IDs (SIN, SSN, driver's license, etc.)
  * Physical or mailing addresses

  Use an opaque identifier (e.g., your own `userId` as a GUID) that maps back to PII inside your own systems.
</Warning>

### Handling AccountId and Tag

Using the same methods to receive the `loginId`, you are able to capture both `Tag` and `AccountId` information.

Below is an example of a redirected landing page URL. The `tag` value you passed in the iframe URL is appended to the redirect, alongside the `loginId`:

```text Redirect URL theme={null}
https://example.com/thank-you?loginId=8b35f6c8-e7b6-41d3-98f8-08d68b7f8d31&tag=YourTag&institution=FlinksCapital
```

Below is an example of a JavaScript event listener:

```json Json theme={null}
{
  "step": "REDIRECT",
  "institution": "FlinksCapital",
  "url": "https://example.com/thank-you?loginId=8b35f6c8-e7b6-41d3-98f8-08d68b7f8d31&tag=YourTag&institution=FlinksCapital"
}
```

If you're using Webhooks to receive your data, the payload will contain the chosen tag. Below is an example of a Webhook payload (transactions, balance, and holder have been abbreviated for simplicity):

```json Json theme={null}
{
    "ResponseType": "GetAccountsDetail",
    "HttpStatusCode": 200,
    "Accounts": [
        {
            "Transactions": [...],
            "TransitNumber": "77777",
            "InstitutionNumber": "777",
            "OverdraftLimit": 0,
            "Title": "Chequing CAD",
            "AccountNumber": "1111000",
            "Balance": {...},
            "Category": "Operations",
            "Type": "Chequing",
            "Currency": "CAD",
            "Holder": {...},
            "Id": "ae1dac72-70da-4626-fed8-08d682e1ff4a"
        },
        {...}
    ],
    "Login": {
        "Username": "Greatday",
        "IsScheduledRefresh": false,
        "LastRefresh": "2019-05-09T13:47:46.5227901",
        "Type": "Personal",
        "Id": "5e115eac-1209-4f19-641c-08d6d484e2fe"
    },
    "Institution": "FlinksCapital",
    "RequestId": "1243c283-e0ca-4fda-a5e4-343068430190",
    "Tag":"YourTag"
}
```

<Tip>
  Tags are also visible in the [Flinks Dashboard](/guides/dashboard/request-feed): you can use them to locate and filter the requests associated with a given tag.
</Tip>