> 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/manage-optimize-channels.md).

# 管理 Optimize 渠道

<a href="https://pxa.impact.com/student/activity/1117602?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=opt-350&#x26;utm_campaign=help-center" class="button primary">参加 PXA 课程</a>

*优化渠道* 将为您提供更多有关您正在跟踪的各种渠道的信息。这些渠道可以帮助您了解合作伙伴驱动流量的路径，即流量如何在与合作伙伴互动和您正在跟踪的操作之间传递。Optimize Channels 收集的数据还将帮助补充您的 *渠道仪表板*，其中包含如下信息： *按月表现* 或 *子渠道*，所有内容都按渠道类型汇总。

{% hint style="success" %}
**注：** 从 *渠道* 功能是 Optimize 附加组件的一部分，并要求您在跟踪中传递 `CustomerStatus` 和 `CustomerId` 参数。 [联系支持](https://app.impact.com/support/portal.ihtml?createTicket=true) 以讨论将其添加到您的账户。
{% endhint %}

#### 访问 Optimize 渠道

1. 在左侧导航栏中，选择 ![](/files/dd9b9b71e0a8abffbc19dd6a3c4d28626449f744) **\[Optimize]**.
2. 在左侧导航栏中，选择 **设置 → 渠道**.
3. 要搜索特定渠道，请在以下位置下输入该渠道的名称 *渠道*.
   * 选择 ![](/files/34cdd2217d627a308c301c2567d5dfe7d669a2cc) **\[搜索]** 不会执行正则表达式搜索，因此您无需担心大小写或使用渠道的准确名称。
4. 查看该渠道。
   * 有关数据表中列的更多信息，请参阅下面的 *表格参考* 以了解有关该渠道本身的更多信息。
5. 从这里，您可以选择要执行的操作。

   * 在 *媒体*，查看 [媒体来源](/brand/zh/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/manage-optimize-media-sources.md) 的数量，这些媒体来源与特定渠道相关联。选择该数字可查看媒体来源的下钻详情。
   * 在 *报告*下，选择 ![](/files/40c04a21450a0fd96febc5a5204bf1c6e6a290de) **\[报告]** 以查看 *渠道仪表板* 针对特定渠道。这是您可以查看更多有关该渠道数据的地方，例如其 *按月表现*.

   <div data-with-frame="true"><figure><img src="/files/f4e7e087540f3965f257f9080f11a46ea989a178" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="success" %}
**注：** 如果您想启用新渠道、禁用旧渠道或编辑当前渠道， [联系支持](https://app.impact.com/support/portal.ihtml?createTicket=true).
{% endhint %}

<details>

<summary>表格参考</summary>

|         |                                                                                                                    |
| ------- | ------------------------------------------------------------------------------------------------------------------ |
| **表格列** | **描述**                                                                                                             |
| 名称      | 特定行中渠道的名称。                                                                                                         |
| 媒体      | <p>与某个渠道关联的媒体来源数量。</p><p>选择该数字以查看 <a href="/pages/259b1472c621d63f6aeb80492dd5821d571ddc2e">Optimize 媒体来源</a>.</p> |
| 信用组     | 查看与特定渠道关联的信用组。                                                                                                     |
| 报告      | 选择 ![](/files/40c04a21450a0fd96febc5a5204bf1c6e6a290de) **\[报告]** 以查看 *渠道仪表板* 适用于特定渠道。                             |
| 操作      | 编辑或启用特定渠道的跟踪。 [联系支持](https://app.impact.com/support/portal.ihtml?createTicket=true) 如果您想这样做。                       |

</details>


---

# 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/cross-channel-performance-insights/optimize-channels/manage-optimize-channels.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.