> 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/working-with-brands/contracts/click-payout-rules-explained-for-partners.md).

# 合作伙伴点击支付规则说明

当品牌与你签订合同时，他们可以设置适用于特定类型点击的自定义支付组规则。这些规则让品牌能够对点击支付进行精细控制，同时也可能让你因带来对品牌有价值的流量而获得更高的报酬。

从 2024 年 1 月起，你与品牌签订的新合同将允许每次点击获得这些更专门化的支付。这些变更称为 **CPC（按点击付费）V2**。在 CPC V2 中，点击会立即记录——不再有锁定期，且已记录的点击无法撤销。

所有新合同都将使用 CPC V2。你与品牌现有的合同不会受到影响，并将继续适用标准的 CPC V1 规则。不过，品牌可以选择更新现有合同，以利用更新后的点击支付选项。

{% hint style="success" %}
**我如何查看我的合同详情？** 请查看 [合作伙伴合同说明](/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/working-with-brands/contracts/contracts-explained-for-partners.md) 以获取查找和理解你与品牌合同的说明。
{% endhint %}

## CPC V2 的优势

作为合作伙伴，新的点击支付规则：

* 取消操作的锁定期
* 消除点击被撤销的可能性
* 让品牌在你带来更理想的点击时，可能以更高费率进行支付

## 合同示例

对于使用 CPC V1 的现有合同，与使用 CPC V2 的新合同相比，支付规则的结构不同。以下示例说明了品牌在每种合同类型下可能如何对点击采取不同的支付方式。

{% tabs %}
{% tab title="CPC V1" %}

* 每次点击的默认支付为 **$0.10**.
* 操作会在其记录当天结束后的 30 天后锁定。
* 点击可以被撤销或修改。
  {% endtab %}

{% tab title="CPC V2" %}

* 每次点击的默认支付为 **$0.10**.
* 每次点击的固定支付为 **$0.25** ，适用于在品牌的 *玩具* SKU 中，来自美国的产品点击，每天最多 100 次点击。
* 点击不适用操作锁定期。
  {% 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/working-with-brands/contracts/click-payout-rules-explained-for-partners.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.