> 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/incrementality-faq.md).
# 增量常见问题
增量衡量每个合作伙伴所带来的真实价值，显示如果没有该合作伙伴，哪些转化本不会发生。这有助于确保你不会削减那些实际上正在推动增量销售的合作关系。增量应用于 [增量仪表板](/brand/zh/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-reports/incrementality-dashboard-explained.md) 和 [按合作伙伴划分的增量性报告](/brand/zh/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-reports/incrementality-by-partner-report.md).
增量仪表板回答哪些问题？
该 [增量仪表板](/brand/zh/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-reports/incrementality-dashboard-explained.md) 提供可帮助回答以下问题的洞察：
* 每个合作伙伴贡献了多少增量价值？
* 如果我移除一个合作伙伴，我会损失多少收入？
* 我是否对某些合作伙伴支付过少或过多？
增量百分比是什么意思？
*增量百分比* 显示合作伙伴的行为或收入中有多少份额真正带来了额外价值。
* *高增量百分比* = 合作伙伴正在推动真实的额外价值（例如，许多独立、介绍或收尾触点）。
* *公式*：模型中的总分数信用 ÷ 合作伙伴参与的总订单数。
增量百分比是如何计算的？
该计算使用了 *U 型时间衰减归因模型* ，该模型会为所有触点分配功劳，而不仅仅是最后一次点击。首次和末次互动被视为最重要，因此它们获得比中间互动更高的权重。
该计算的 *7 天时间衰减模型* 意味着越接近转化的互动获得越多功劳。例如，转化前 1 天的互动比转化前 8 天的互动权重高两倍。转化路径中的首尾步骤也会获得额外权重。
该模型确保那些帮助开启或结束旅程，或在接近转化时做出贡献的合作伙伴获得更高权重。
什么是调整后 CPA 和调整后 ROAS？
*调整后 CPA/ROAS* 通过仅显示增量行为或收入来考虑增量性。这些指标可帮助你设定公平的绩效目标：
* 调整后 CPA = 你在仍能获得价值的情况下可支付的最低每次行动成本。
* 调整后 ROAS = 你可从增量价值中预期获得的最高广告支出回报。
为什么调整后 ROAS/CPA 可能与标准 ROAS/CPA 不同？
在末次点击模型下，如果另一个渠道“抢先一步”转化了用户，合作伙伴可能无法获得其贡献的功劳。增量报告会更公平地分配功劳，通常会显示某个合作伙伴带来的价值比原本被认可的更多。
我如何利用这些洞察来做决策？
* 识别哪些合作伙伴正在推动真正的增量销售。
* 比较标准与调整后的 CPA/ROAS，看看你是否支付过少或过多。
* 利用这些洞察来决定是优化、重新谈判，还是扩大合作关系。
---
# 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/cross-channel-performance-insights/optimize-reports/incrementality-faq.md?ask=&goal=
```
`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.