> 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/actions-and-payouts/chained-action-reports/referral-windows-for-chained-action-reports-explained.md).
# 链式动作报告中的推荐窗口说明
你需要了解 2 个推荐窗口： *链式操作推荐窗口* 和 *点击推荐窗口*。推荐窗口只能在 *模板条款* 部分下， **合同** 位于左侧导航菜单中。
1. 在左侧导航菜单中，选择  **\[Engage]** → **合同**.
2. 选择 **模板条款**。你可以修改或设置模板条款，并指定推荐窗口。
了解更多关于 [合同和模板条款](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/learn-about-template-terms-and-contracts.md).
{% tabs %}
{% tab title="链式操作推荐窗口" %}
该链式操作默认期限为 5 年，因此从父操作被跟踪到某个子操作被跟踪之间可间隔 5 年。超过 5 年后被跟踪的子操作将不会与其对应的父操作关联。此数值可以调整为更短的时间。
{% endtab %}
{% tab title="点击推荐窗口" %}
该链式操作默认期限为 180 天，因此从你的合作伙伴带来的初始点击到父操作被跟踪之间可间隔 179 天。如果父操作（例如应用安装）发生在初始点击后的 180 天之后，则父操作将不会被跟踪。根据业务决策以及事件之间对你的品牌最合理的安排，这个数值可以调整为更短的时间。
{% endtab %}
{% endtabs %}
示例场景
作为品牌，你希望将推荐窗口设置如下：推荐窗口和点击窗口都设为 45 天。
你还有链式操作：免费试用注册和付费订阅事件。你会批量导入这些付费订阅事件，并将归因政策设置为如下：免费试用注册获胜，然后级联到最后点击。
如果在 45 天后提交操作，会发生什么？为了使推荐窗口和点击窗口在文件于 45 天后发送时仍然适用，提交文件时提供的日期必须少于 45 天，或落在指定的推荐窗口和点击窗口内。如果操作日期超过 45 天，impact.com 会将其归因于点击；而如果点击窗口也超过 45 天，则会报错，且不会找到推荐方。
超出两个窗口的操作将出现错误原因： `NO_VALID_REFERRERS_FOUND OUTSIDE_ASSOCIATION_WINDOW`。你可以在 [无效转化](https://app.impact.com/secure/advertiser/engage/actions/admin/integrated/viewReport.report?handle=adv_invalid_conversions) 报告中找到这些操作。
---
# 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/actions-and-payouts/chained-action-reports/referral-windows-for-chained-action-reports-explained.md?ask=&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.