> For the complete documentation index, see [llms.txt](https://help.blinger.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blinger.io/documentation/section-apps/tagging-accounts.md).

# Tagging accounts

## General information

The function "Account tagging" is necessary, if you need to help the operators distinguish the accounts from which the users came, to be able to analyze them further.

Use case:

* a company needs to connect several accounts of one channel, for example, 4 WhatsApp accounts and they need to understand, which user and from which channel contacting them.

## How to set up?

### Step 1. In Apps tab click on "Edit" for the integration with one of the channels

![](/files/-Lmdl_rUeNclrf_jyCW2)

### Step 2. Enter in "Tags" field the value, which you would like to define for the integration

To delete a tag you should click on "x".

![](/files/-LmdleB800uQAayViFy8)

{% hint style="success" %}

### The function is set up!

{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.blinger.io/documentation/section-apps/tagging-accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.