> 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/cross-channel-performance-insights/optimize-reports/optimize-metrics-explained.md).

# 优化指标说明

本文解释了 impact.com 如何在客户可能采取的不同场景中，将一次转化（如销售或注册）的归因分配给特定合作伙伴，从单次点击到涉及多个合作伙伴的旅程。

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-3f637e61c18d18e166c36929a49e76f223a6bd16%2F5ac8d86bacce165f35650574a7d731df01f02293fe6eefdc447e422952dc0774.png?alt=media" alt=""><figcaption></figcaption></figure></div>

<details>

<summary>单步路径</summary>

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-dd5e75825a0144c1ad42ba5ab8df3f98d60c5831%2F31fea35b0541b3a8a2f4508bd98e8a459adc387e7c0447677bbe164427a42fde.png?alt=media" alt=""><figcaption></figcaption></figure></div>

在最简单的情况下，客户点击某个合作伙伴的链接并完成转化。该 *成交者* 因此获得归因。两者的 *参与点击数* 和 *参与次数* 均为 1。

</details>

<details>

<summary>两步路径（一个合作伙伴）</summary>

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1299f6c8adcf344046192b6dee38ee8a1bf55175%2F5bc390f21e7c84f666529c8ef9a5605ccc737f171e572d23b7044d1c4301c1cc.png?alt=media" alt=""><figcaption></figcaption></figure></div>

在此路径中，客户两次点击同一合作伙伴的链接，该合作伙伴同时充当 *引介者* （第一次点击）以及 *成交者* （第二次点击）。该 *成交者* 点击赢得归因。该 *参与点击数* 为 2，但 *参与次数* 仍为 1，因为只涉及一个唯一合作伙伴。

</details>

<details>

<summary>3步路径（一个合作伙伴）</summary>

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-518ca6f9b9448f66515fae02ead4236561dd5280%2F18ee032d978ad8f38d6dc4b34cdae2582f045327ba755cda4d7583db92c46aab.png?alt=media" alt=""><figcaption></figcaption></figure></div>

在此路径中，这个单一合作伙伴现在承担所有角色： *引介者* （点击 1）， *影响者* （点击 2），以及 *成交者* （点击 3）。成交者获胜， *参与点击数* 为 3，且 *参与次数* 为 1。

</details>

<details>

<summary>N步路径（一个合作伙伴）</summary>

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-09b0a93fa0f1e4d8174bafa06f8d8fa2ca60b2a4%2Fe7bc2d12707cfcb74ce1521368c924df3f3adf4c088dd4935cc01841bde6901e.png?alt=media" alt=""><figcaption></figcaption></figure></div>

这将规则推广到来自同一合作伙伴的任意 N 次点击。该合作伙伴作为 *引介者*，并在所有中间点击中作为 *成交者*。该 *成交者* （点击 N）赢得归因。该 *参与点击数* 为 N，但 *参与次数* 始终为 1，因为只有 1 个合作伙伴。

</details>

<details>

<summary>双合作伙伴路径</summary>

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-2c5928b7b1ef78367a1923a9d2889775e4287a51%2Fd25fe3d3b3c6c8e87de1c21a9cbada36df9cb82e870281c161af7c7bef0cd74b.png?alt=media" alt=""><figcaption></figcaption></figure></div>

当涉及 2 个或更多合作伙伴时， *成交者* 并不总是 *获胜者*。 *成交者*.

在合作伙伴 A 有 3 次点击而合作伙伴 B 有 1 次点击的情况下， *参与点击数* 总数为 4，但 *参与次数* 仅为 2（A 一次，B 一次）。

</details>

<details>

<summary>多合作伙伴路径</summary>

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-349946ffdf7b94a92acda5435b6e93851a589b82%2F1d477f7f76271eb811e7bf71cc55cb0debb9d06c21b60a2c1ad429610b632924.png?alt=media" alt=""><figcaption></figcaption></figure></div>

与双合作伙伴路径一样， *获胜者* 可以根据合同条款是像合作伙伴 B 这样的合作伙伴，而不一定是 *成交者* （合作伙伴 D）。在每次点击都来自不同合作伙伴的情况下， *参与点击数* （4）和 *参与次数* （4）将相等。

</details>


---

# 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/cross-channel-performance-insights/optimize-reports/optimize-metrics-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.