> 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/reporting-for-partners/click-reports/click-tracker-cpc-earnings-report-explained-for-partners.md).
# 合作伙伴点击追踪器 CPC 收益报告说明
{% hint style="warning" %}
**重要！** 本文所涵盖的报告属于 impact.com 的旧版 CPC 跟踪功能，仅应用于查看历史数据。若要查看你的 CPC V2 可付费点击，请参见 [合作伙伴可付费点击数据报告](/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/reporting-for-partners/click-reports/payable-click-data-report-for-partners.md) 而不是前者。
{% endhint %}
在 CPC V2 发布之前，品牌可以筛选并拒绝超出合同范围或超过其付款预算的合作伙伴点击。impact.com 的 CPC 功能现在不再允许品牌拒绝点击，而是允许他们创建高度可自定义的付款规则，预先设定他们愿意为哪些点击付费。
#### 访问报告
1. 打开 **点击跟踪器 CPC 收益** 报告。
2. 在报告标题下，设置 **日期范围**下方，选择 **项目** 你要查看报表的范围，然后选择  **\[搜索]**.
* 查看 *表格参考* 如下以获取更多信息。
表格参考
| | |
| ------ | ----------------------------- |
| **表列** | **描述** |
| 日期 | 生成点击事件的日期。 |
| ID | 该点击事件对应的 impact.com 生成的行动 ID。 |
| 品牌 | 你促成该点击事件所对应的品牌计划。 |
| 事件类型 | 与该点击事件相关联的事件类型。 |
| 状态 | 该点击事件的行动状态（例如：已批准）。 |
| 可付费点击 | 你本可以就该点击事件获得付款的点击次数。 |
| 每次点击收益 | 该点击事件的每次点击收益（EPC）。 |
| 收益 | 某一特定事件类型的总收益。 |
| 税费 | 该点击事件所评估的税额。 |
---
# 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/reporting-for-partners/click-reports/click-tracker-cpc-earnings-report-explained-for-partners.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.