> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-tracking/track-your-advocate-processes.md).
# 跟踪你的 Advocate 流程
流程可帮助你监控与你的相关活动 [计算字段](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/custom-and-calculated-fields/calculated-fields-explained.md) 和 [参与者表](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/filter-and-manage-advocate-participants.md)。无论你是在重新计算自定义数据点，还是在刷新特定用户的统计数据，此页面都能让你清楚了解已完成的操作、执行者以及执行时间。
您可以使用 *流程* 列表，以便排查更新、确认统计刷新已成功完成，并检查是否存在任何问题。
1. 从左侧导航菜单中，选择  **\[Engage]** → **数据源**.
2. 接下来，从选项列表中选择 **流程**.
#### 为什么要使用流程？
当你对以下内容进行了更新时，流程尤其有用： [计算字段](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/filter-and-manage-advocate-participants.md) 并希望确保这些更改已应用到正确的参与者记录中。一旦触发重新计算，后台流程就会运行以应用该逻辑，然后该流程的状态会记录在此处。它可确保更新已按预期处理。
**在以下情况后检查“流程”页面：**
* 触发计算字段刷新
* 查看其上次更新时间
流程参考表
| 列 | 说明 |
| ----- | --------------------------------------------------------------------------------------------------------------------------- |
| 名称 | 已运行的流程类型，例如： *参与者统计刷新*. |
| 发起人 | 发起该流程的用户的电子邮件地址。 |
| 创建日期 | 该流程被触发的时间。 |
| 已处理行数 | 受此次更新影响的参与者记录数量。 |
| 耗时 | 该流程完成所用的时间。 |
| 错误 | 处理过程中发生的任何错误。值为 0 表示成功。
如果你遇到任何错误，请联系 支持 寻求帮助。
|
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-tracking/track-your-advocate-processes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.