> 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/cross-channel-performance-insights/optimize-channels/edit-an-optimize-channel.md).
# 编辑优化渠道
您可以在您的 Optimize Channels 之后编辑 [初始设置](/brand/zh/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-startup-guide.md) 已完成，因为您的营销渠道会发生变化并更新。
在编辑 Optimize Channel 时，impact.com 建议尽可能保持逻辑简单且易读。这将使对您的规则的持续支持更加有效和高效。
#### 编辑一个 Optimize channel
{% hint style="warning" %}
This feature is only available with specific impact.com editions or add-ons. If you see the .svg?alt=media\&token=91ff61f9-8618-4503-b0df-791e0353d124) **Optimize** icon, your account is eligible for the upgrade. Select the icon and get the Optimize add-on directly in the platform!
{% endhint %}
1. 从左侧导航栏中选择  **\[Optimize] → 设置 → 渠道**.
2. 在 *操作*中，选择  **\[更多]→ 编辑** 适用于您要编辑的渠道。
3. 更新该渠道的 **名称**.
4. 选择什么 **类型** 从下拉菜单中选择该渠道的类型。
5.  **\[开启]** **添加规则以识别渠道流量**.
6. 在这里，您可以管理渠道用于识别和归属组的规则。
* 详细了解您在配置以下内容时的选项 [识别规则](/brand/zh/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/set-up-rules-to-identify-channel-traffic.md) 和 [归属组](/brand/zh/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/credit-groups-explained.md)，Optimize Channel 的组成部分。
7. 选择 **保存**.
---
# 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/cross-channel-performance-insights/optimize-channels/edit-an-optimize-channel.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.
