> 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-reporting-and-analytics/run-an-advocate-program-report.md).

# 运行 Advocate 项目报告

impact.com 提供多种专为 Advocate 设计的计划报告，帮助您了解推荐计划的表现，并协助您手动发放奖励。

1. 从左侧导航菜单中，选择 ![](https://impact-1.gitbook.io/docs/emvxfLrwrlacc4y3y02Y/~gitbook/image?url=https%3A%2F%2F4048883401-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FwMLlMoFBtKJa8ptd3zaw%252Fuploads%252Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%252Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg%3Falt%3Dmedia\&width=300\&dpr=3\&quality=100\&sign=71dd50ef\&sv=2) **\[Engage] → 报告 → 导入与导出**.
2. 在页面右上角，选择 **创建报告**.
3. 输入一个唯一的 **报告名称**，例如： `用户详情 — Acme 计划`.
4. 选择一个 **报告类型**.
   * 如需查看报告类型及各自包含的内容，请参阅 [Advocate 计划报告详解](/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-program-reports-explained.md).
5. 选择 **报告字段** 并应用 **筛选条件** 相关的。
   * 可用的字段和筛选条件会因您选择的报告而异。
6. 选择一个 **报告格式** ，从下拉列表中： **CSV** 或 **Excel**.
7. 选择 **创建报告**.

报告将开始生成。根据请求的数据量，完成可能需要一些时间。报告准备好后，impact.com 会向生成该报告的人发送一封包含下载链接的电子邮件。生成的报告也可在以下位置查看 *导入与导出* 页面获取。

{% hint style="info" %}
**注意**：要将 UNIX 时间戳转换为人类可读的日期，请使用以下公式： `=DATE(1970, 1, 1) + (*X / 86400000)`。对于 `*X`，请使用要转换的单元格的 A1 引用格式。
{% 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 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-reporting-and-analytics/run-an-advocate-program-report.md?ask=<question>&goal=<user_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.