> 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与调整后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.