> 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归因]
```

## 引荐窗口配置

* **合同级设置** — 每份 [合同](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms.md) 都会为您与合作伙伴之间的关系设定独立的引荐窗口。
* **按操作日期确定规则** — 适用的引荐窗口由相应跟踪操作发生时（操作日期）生效的合同决定。
* **引荐窗口遵循生效合同** — 操作日期时生效的合同决定该操作适用的引荐窗口，即使该合同后来已更新或被替换。

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

当您更新 [合同的引荐窗口](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/modify-template-terms.md) 或 [将合作伙伴转至新合同](https://help.impact.com/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 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/contracts-and-template-terms/referral-window-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.
