> 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/credit-policies/credit-policies-overview.md).

# 归因政策概览

**参加 PXA 课程**

<a href="https://pxa.impact.com/student/activity/1099652?debug=true?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=fund-lp-150&#x26;utm_campaign=help-center" class="button primary">签约与付款（基础级）</a><a href="https://pxa.impact.com/student/activity/1117596?debug=true?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=con-350&#x26;utm_campaign=help-center" class="button primary">签约与付款（专家级）</a>

当客户的转化路径中出现多个合作伙伴时，归因政策决定哪位合作伙伴获得该次转化的归因。每个 [事件类型](/brand/zh/what-would-you-like-to-learn-about/platform-features/event-types/event-types-explained.md) 在您的计划中，会使用 3 种归因政策中的一种来设置其归因逻辑。

默认情况下，impact.com 会按最后点击进行转化归因，但您可以应用不同的归因政策，以反映您希望在客户旅程中如何奖励合作伙伴。

| 归因政策                                                                                                                                    | 工作原理                                                                                                 | 最适合                                                                                 |
| --------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| [最后点击](/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/credit-policies/last-click-credit-policy-explained.md)   | 在转化路径中促成最后一次点击的合作伙伴将获得 100% 的归因。                                                                     | 奖励促成成交的合作伙伴。这是一项 **推荐的** 归因政策。                                                      |
| [首次点击](/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/credit-policies/first-click-credit-policy-explained.md)  | <p>在转化路径中促成首次点击的合作伙伴将获得 100% 的归因，通常也会获得该次转化的全部支付金额。</p><p>此归因政策仅适用于某些 impact.com 版本。</p>             | 奖励将客户介绍给产品的合作伙伴。此政策 **不推荐** 用于大多数实施场景。                                              |
| [最后加购](/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/credit-policies/last-to-cart-credit-policy-explained.md) | <p>促使客户在结账前将最后一件商品加入购物车的合作伙伴几乎总是会获得 100% 的归因，通常还会获得该次转化的全部支付金额。</p><p>此归因政策仅适用于某些 impact.com 版本。</p> | 当“加入购物车”这一时刻比最终结账更能反映您所要衡量的合作伙伴影响力时。它是否适合推荐给您的计划，取决于 **具体情况** ，并应与 impact.com 代理讨论。 |

{% hint style="warning" %}
**不要自行修改您的归因逻辑：** 更改归因政策意味着您需要更新事件类型，这只能由 impact.com 代理来完成。请与您的 CSM 交谈（或 [联系支持](https://app.impact.com/support/portal.ihtml?createTicket=true\&accountType=PARTNER)）以了解进行任何归因政策更改。
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/credit-policies/credit-policies-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.