> 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/tracking/stand-down-policy-explained.md).
# 停摆政策说明
impact.com 的 [停让政策](https://app.impact.com/pcontent/stand-down-policy.ihtml) 是一种最佳实践，可防止某些合作伙伴——尤其是使用浏览器扩展、工具栏或购物车内解决方案的合作伙伴——在另一位合作伙伴已记录点击后干扰购物体验。一旦购物者与跟踪链接（例如来自创作者、内容发布者、返现计划或优惠券网站）互动，则 `afsrc=1` 参数会自动附加到所有由合作伙伴驱动的流量的落地页 URL 上。任何竞争性的扩展都必须退让，不得通过触发弹窗、激活新的跟踪链接或更改客户的购买路径来试图覆盖原始点击。
#### 运作方式
1. 消费者点击来自合作伙伴网站的链接后，会被带到品牌的落地页。
2. 该 `afsrc=1` 参数会自动附加到落地页 URL 上。
3. 竞争的合作伙伴，例如浏览器扩展，会检查将消费者重定向过来的链接，并识别出这是一个 impact.com 跟踪链接。
4. 随后，该扩展必须遵守停让政策，并且不应向该消费者展示任何扩展弹窗。
#### 在您的模板条款中查看停让政策
您可以通过查看您的模板条款的 *通用条款* 部分。
1. 在左侧导航栏中，选择  **\[Engage]** → **合同** → **模板条款**.
2. 将鼠标悬停在相关模板条款上，然后选择  **\[更多]** → **查看条款**.
3. 向下滚动到 *通用条款* 部分，然后查找 *停让政策*.
#### 禁用停让政策
{% hint style="warning" %}
**警告：** 默认情况下，您的计划已启用停让政策，我们建议您保持启用，以建立良好的合作关系。明确声明您遵守停让政策将为合作伙伴提供更好的机会，以维持其作为转化赢家的地位。
{% endhint %}
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在右侧，位于 *跟踪*，选择 **常规**.
3. 在 *停让政策* 部分下，选择  **\[复选框]** **在所有模板条款中启用停让政策**.
4. 选择 **保存**.
---
# 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/tracking/stand-down-policy-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.
