# Closed Funnel和Open Funnel的定义

> **漏斗分析（Funnel Analysis）是一种关键行为路径追踪方式，帮助产品或数据团队观察用户在一系列事件中的转化情况**

### **funnel支持两种漏斗类型：**

* **Closed Funnel（闭合漏斗）**
* **Open Funnel（开放漏斗）**

并且漏斗支持两种计数方式：

* **Events**：统计事件数
* **Users**：统计用户数

<figure><img src="/files/FcVfcfy2qx7wXm9xMcgP" alt=""><figcaption></figcaption></figure>

1\. Closed Funnel（闭合漏斗)

**定义：**

* **事件顺序必须完全遵守设定顺序**
* **每一步必须连续发生**
* 任意步骤缺失或顺序错误，后续事件将 **不再计入**

**举例：**

假设漏斗步骤为：\
**Step 1: A → Step 2: B → Step 3: C → Step 4: D**

| 用户 | 事件触发顺序        | 计入层级       | 说明              |
| -- | ------------- | ---------- | --------------- |
| U1 | A → B → C → D | A, B, C, D | 严格按顺序，全部计入      |
| U2 | A → B → D     | A, B       | 缺少 C，停止在 B      |
| U3 | A → C         | A          | B 缺失，C 不计入      |
| U4 | B → C → D     |            | 起始事件 A 缺失，不纳入计算 |

#### 2. Open Funnel（开放漏斗）

**定义：**

* **要求事件依照指定顺序出现**
* **可以中途结束，但不能跳跃步骤继续推进**
* 一旦中断（跳过步骤），**后续事件即不再计入**

**举例：**

事件顺序：A → B → C → D

| 用户 | 实际事件触发顺序          | 计入层级       | 说明                           |
| -- | ----------------- | ---------- | ---------------------------- |
| U1 | A → B → C → D     | A, B, C, D | 顺序完整，全部计入                    |
| U2 | A → B → D         | A, B       | 缺 C，停止在 B                    |
| U3 | A → C             | A          | B 缺失，不能继续推进到 C               |
| U4 | A → C → D         | A          | 中间缺 B，C 和 D 不计入              |
| U5 | B → C → D         | B, C, D    | 缺少起始事件 A，不纳入漏斗               |
| U6 | A → B → C → C → D | A, B, C, D | 重复事件不会影响推进（只看顺序）             |
| U7 | A → C → B → D     | A          | 虽然都有，但 B 出现在 C 后，违反顺序规则，仅计 A |


---

# Agent Instructions: 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:

```
GET https://doc.appflow.ai/docs/subscription-analytics/closed-funnel-he-open-funnel-de-ding-yi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
