> 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/ja/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-channels/create-an-optimize-channel.md).
# 最適化チャネルを作成
あなたの [初期設定](/brand/ja/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-startup-guide.md) は、より多くのマーケティングチャネルを採用するにつれて完了しました。
Optimize Channel を作成する際、impact.com ではロジックをできるだけシンプルで読みやすく保つことを推奨しています。これにより、ルールの継続的なサポートがより効果的かつ効率的になります。〜について詳しく見る [Optimize Essentials & Pro](/brand/ja/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/compare-optimize-essentials-and-pro-tiers.md).
#### Optimize チャネルを作成する
{% 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. ここから、チャネルのルールを設定して Identify and Credit Group を識別できます。
* 設定オプションの詳細を見る [識別ルール](/brand/ja/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/set-up-rules-to-identify-channel-traffic.md) および [クレジットグループ](/brand/ja/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/credit-groups-explained.md)は、Optimize チャネルの構成要素です。
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/ja/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-channels/create-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.
