> 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 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.