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

# Optimize チャネルを作成

あなたの後、さらにOptimizeチャンネルを作成できます [初期設定](/brand/ja/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-startup-guide.md) は、より多くのマーケティングチャネルを導入するにつれて完了しました。

Optimizeチャンネルを作成する際、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チャンネルを作成する

1. 左側のナビゲーションバーから、 ![](/files/80820a684046e77348a87fa4aae033fc6f04adf0) **\[Optimize]→ 設定 → チャンネル**.
2. 右上隅で **チャンネルを作成**.
3. チャンネルに **名前**.
4. 何を **タイプ** をドロップダウンメニューから選択します。
5. ![](/files/966a7b9c51811043ca7c1811ec6f6b9ef39fd26f) **\[オンに切り替え]** **チャネルのトラフィックを識別するルールを追加する**.
6. ここから、チャンネルのルールを設定して、グループの識別とクレジット付与を行えます。
   * 設定オプションの詳細については、 [識別ルール](/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 Channel を構成する要素です。
7. 選択 **保存**.

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


---

# 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/ja/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-channels/create-an-optimize-channel.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.
