> 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/creator-program/creator-campaigns-for-brands/check-your-hired-creators-performance.md).

# 检查你已聘用创作者的绩效

通过查看各种绩效报告来跟踪和审查活动数据。

#### 查找活动绩效报告

1. 在左侧导航栏中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **活动管理器 →** [**创作者**](https://app.impact.com/secure/advertiser/engage/campaigns/influencer-campaign-manager-flow.ihtml).
2. 在 *活动管理器* 界面上，选择 **活跃** 选项卡以查看你当前所有活跃的活动。
   * 每个活动都会提供最重要洞察的摘要。
     * 申请人数
     * 你邀请了多少人
     * 谈判中总数
     * 你录用了多少人
     * 任务总数
     * 已花费预算
3. 将鼠标悬停在你要管理的活动上，并选择 **管理活动**.
4. 在你所选活动的界面上，选择 **绩效**.
   * 此选项卡将为所选活动提供创作者、平台和活动绩效指标。

**进一步了解活动报告**

请参阅以下文档，了解创作者活动绩效报告：

* [内容与活动概览报告](/brand/zh/what-would-you-like-to-learn-about/creator-program/creator-reports/content-and-campaign-overview-report.md)


---

# 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/creator-program/creator-campaigns-for-brands/check-your-hired-creators-performance.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.
