> 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/contracts-and-template-terms/referral-window-explained.md).

# 引荐窗口说明

推荐（或 cookie）窗口在合作伙伴驱动的点击或事件之后开始。如果客户在该窗口内购买，impact.com 会将功劳记给合作伙伴。了解这一时点有助于你预测归因并解决争议。

```mermaid
flowchart LR
    A[客户点击\n合作伙伴链接] --> B[推荐窗口\n计时器开始]
    B --> C{客户完成转化？}
    C -->|在窗口内| D[转化归因\n给合作伙伴]
    C -->|窗口过期后| E[转化未\n归因]
```

## 推荐窗口配置

* **合同级设置** — 每个 [合同](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms.md) 您与合作伙伴之间的每份合同都定义自己的推荐窗口。
* **按行为日期的逻辑** — 适用的推荐窗口将由对应被跟踪行为发生时生效的合同决定（行为日期）。
* **推荐窗口遵循当前生效的合同** — 在行为日期生效的合同将决定该行为的推荐窗口，即使该合同后来已更新或替换也是如此。

## 合同更新如何影响推荐窗口

当你更新 [合同的推荐窗口](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/modify-template-terms.md) 或 [将合作伙伴移至新合同](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/replace-a-partners-contract.md)时，该更改适用于在新合同开始日期当天或之后发生的行为。在上一份合同下发生的行为，将保留当时适用的窗口。

| 点击日期  | 当前生效的合同         | 归因窗口 | 转化截止于 |
| ----- | --------------- | ---- | ----- |
| 5月20日 | 当前合同（5月15日至31日） | 15 天 | 6月4日  |
| 6月5日  | 即将生效的合同（6月1日起）  | 1天   | 6月6日  |

在这个示例中，5月20日点击合作伙伴链接的客户拥有15天窗口，因此 impact.com 会将6月4日之前的转化计入合作伙伴名下。6月5日点击的客户拥有1天窗口，因此 impact.com 只会将6月6日之前的转化计入合作伙伴名下。

## 这为何重要

* **可预测的归因** — 由于窗口锁定到行为日期，你和合作伙伴都能准确计算转化何时会或不会被计入，而不受后续合同变更影响。
* **公平的合作伙伴报酬** — 合作伙伴的报酬依据其在带来流量时同意的条款，而不是事后追溯的合同更新。
* **排查未归因转化** — 如果转化未如预期归因，请检查该点击是否发生在窗口比当前合同更短的合同下。


---

# 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/contracts-and-template-terms/referral-window-explained.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.