> 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/platform-features/tracking/set-up-tracking/cost-per-click-v1-and-pending-clicks-explained.md).

# 每次点击费用 V1 和待处理点击说明

{% hint style="warning" %}
**重要！** 本文介绍 impact.com 的旧版 CPC 跟踪功能，仅用于帮助您了解 CPC V1 的概念或查看历史数据。访问 [使用 CPC V2 设置您的点击结算规则](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/set-your-click-payout-rules-with-cpc-v2.md) 如果您需要有关为您的项目配置 CPC 结算规则的指导。
{% endhint %}

在 CPC V2 发布之前，CPC 事件类型允许品牌将点击转化为待处理操作，之后他们可以在向合作伙伴付款之前对其进行筛选并拒绝。品牌利用此功能来掌控预算，并避免因无效流量向合作伙伴付款。

impact.com 的 CPC 功能此后已升级，增加了可自定义的结算组、结算 *限额* 以避免预算超支，并通过内部缓解因素来避免无效流量。这使您可以专注于根据对您的项目带来最大价值的方式来调整您的结算。

#### CPC V1 报表

在 CPC V1 中，点击事件类型会收集合作伙伴一天内产生的所有点击，并将其汇总为一个 CPC 操作。以下是品牌用于管理和跟踪点击操作成本的 2 个报表。

{% tabs %}
{% tab title="待处理点击" %}
品牌可以在 [待处理点击](https://app.impact.com/secure/advertiser/engage/actions/clicks/click-actions-flow.ihtml) 屏幕上筛除无效点击。未被拒绝的点击会计入当天报告的操作中。
{% endtab %}

{% tab title="Click Tracker CPC 结算" %}
品牌可以在 [Click Tracker CPC 结算报表](https://app.impact.com/secure/advertiser/engage/additionalreports/report/viewReport.report?id=1828).
{% endtab %}
{% endtabs %}


---

# 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/platform-features/tracking/set-up-tracking/cost-per-click-v1-and-pending-clicks-explained.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.