> 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-reports/creator-reports-overview.md).

# 创作者报告概览

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FSw5bbwkQhH6hEKDn9GkK%2Fcrea-150-3.mp4?alt=media&token=09cb5ef7-98de-405c-ad02-ba3b50d75df9>" %}

## 报告指标明细

创作者报告汇总 [活动](/brand/zh/what-would-you-like-to-learn-about/creator-program/creator-campaigns-for-brands/configure-a-creator-campaign.md) 来自各种来源的指标，例如 impact.com 的绩效数据，以及社交媒体数据等外部来源：

* **社交媒体指标**—社交媒体帖子指标与 [活动任务](/brand/zh/what-would-you-like-to-learn-about/creator-program/creator-campaigns-for-brands/add-or-remove-creator-campaign-tasks-as-a-brand.md) 相关，这些任务由创作者提交供您审核。每种社交媒体平台都有独特的指标，例如点赞、评论、分享、浏览等。这些指标会显示在您的创作者绩效报告中，并反映帖子上的总活动量，包括自然流量以及任何放大或付费推广指标。指标按特定时间范围跟踪：

  * **生命周期指标：** 从活动开始到设定结束日期之间的指标。
  * **增量指标：** 从设定开始日期到设定结束日期之间的指标。

  请参阅 [*社交媒体指标比较*](#social-media-metrics-comparison) 部分，了解每种帖子类型会跟踪哪些指标的更多信息。
* **impact.com 绩效指标**—impact.com 的绩效指标用于报告那些带来流量并最终促成转化（如线上销售）的跟踪链接。这些指标包括链接点击次数、每次链接点击的动作数、与每次链接点击相关的成本等。
* **固定费用和产品赠送指标**—这些指标始终按活动跟踪，并与创作者完成任务所获得的报酬相关。这些指标不与跟踪链接绩效挂钩。

### 社交媒体指标比较

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

{% hint style="success" %}
**已包含放大活动：** 创作者报告中的社交媒体指标反映帖子上的所有活动，包括任何放大或付费推广指标。不过，根据双方对活动的归因方式不同，数值可能与其他跟踪来源有所差异。
{% endhint %}

| 社交任务            | 可用的社交媒体指标                                                               |
| --------------- | ----------------------------------------------------------------------- |
| Instagram 帖子    | <p>• 评论</p><p>• 互动</p><p>• 点赞</p><p>• 触达人数</p><p>• 浏览量</p><p>• 分享</p>   |
| Instagram Reels | <p>• 评论</p><p>• 互动</p><p>• 点赞</p><p>• 触达人数</p><p>• 分享</p><p>• 视频浏览量</p> |
| Instagram 故事    | <p>• 互动</p><p>• 浏览量</p><p>• 触达人数</p><p>• 分享</p>                         |
| TikTok 视频       | <p>• 评论</p><p>• 互动</p><p>• 点赞</p><p>• 触达人数</p><p>• 分享</p><p>• 浏览量</p>   |
| Facebook 帖子     | <p>• 评论</p><p>• 互动</p><p>• 展示次数</p><p>• 点赞（反应）</p><p>• 分享</p>           |
| YouTube 视频      | <p>• 评论</p><p>• 互动</p><p>• 展示次数</p><p>• 点赞</p><p>• 分享</p><p>• 浏览量</p>   |
| Twitter/X 帖子    | <p>• 评论/回复</p><p>• 互动</p><p>• 展示次数</p><p>• 点赞</p><p>• 浏览量</p>           |
| Twitch 视频       | • 浏览量                                                                   |
| Pinterest 图钉    | <p>• 展示次数</p><p>• 浏览量</p>                                               |

{% hint style="success" %}
**未知帖子类型：** 这些指标与活动任务无关联，来源于在活动之外生成的跟踪链接。
{% 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/creator-program/creator-reports/creator-reports-overview.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.