> For the complete documentation index, see [llms.txt](https://aican.gitbook.io/aican/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aican.gitbook.io/aican/aican-system/menu/data-analysis/customer-tags.md).

# 客户标签

## 简介

客户标签用于统计各客户标签的使用情况，帮助您了解不同标签对应的客户数量与占比，方便分析客户组成与标签分布。

***

## 筛选条件

<div data-with-frame="true"><figure><img src="/files/N2lLRXgr5BMUnKcQTDyc" alt=""><figcaption></figcaption></figure></div>

支持以下筛选条件：

* 渠道类型
* 渠道名称
* 客户标签

> #### 说明
>
> * 渠道类型与渠道名称会同时生效，仅显示符合条件的数据。
> * 已删除的渠道仍会显示于筛选列表，并排列于最下方。
> * 已冻结的渠道仍会显示于筛选列表。已删除的客户标签不会显示于筛选列表中。
> * 筛选条件仅影响页面显示结果，不影响客户占比的计算方式。

***

## 页面内容

#### 标签使用数（横向柱状图）

<div data-with-frame="true"><figure><img src="/files/ramonblM1VYTb9u4AbAM" alt=""><figcaption></figcaption></figure></div>

显示各客户标签对应的客户数量，并依照数量由高至低排序。

***

#### 客户标签明细

<div data-with-frame="true"><figure><img src="/files/pEJclFYc1MfxG8cmtwHr" alt=""><figcaption></figcaption></figure></div>

显示以下统计数据：

* 标签名称
* 客户数
* 客户占比

> #### 说明
>
> * 单一客户可同时拥有多个标签，因此每个标签都会分别计入统计结果。
> * 客户占比＝标签客户数 ÷ 总客户数。
> * 由于同一位客户可拥有多个标签，因此所有标签占比的总和不一定等于 100%。

{% hint style="info" %}

#### 提醒

建议搭配渠道类型、渠道名称与客户标签等条件进行筛选，以便分析不同渠道的客户分布情况。
{% 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://aican.gitbook.io/aican/aican-system/menu/data-analysis/customer-tags.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.