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

# Einen Optimize-Kanal erstellen

Sie können weitere Optimize Channels erstellen, nachdem Ihr [der Ersteinrichtung](/brand/de/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-startup-guide.md) abgeschlossen wurde, während Sie weitere Marketingkanäle einführen.

Beim Erstellen eines Optimize Channels empfiehlt impact.com, die Logik so einfach und lesbar wie möglich zu halten. Dadurch wird die laufende Wartung Ihrer Regeln effektiver und effizienter. Erfahren Sie mehr über [Optimize Essentials & Pro](/brand/de/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/compare-optimize-essentials-and-pro-tiers.md).

#### Einen Optimize Channel erstellen

{% hint style="warning" %}
This feature is only available with specific impact.com editions or add-ons. If you see the ![](https://1651675991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpVKEIcehMut8QKRmaUZu%2Fuploads%2F5ikfGgRSMOFn089EEFxy%2Foptimize.svg%20\(1\).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. Wählen Sie in der linken Navigationsleiste ![](https://1698965099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1e02b2659c94fa0756772cc6c1880977fc9aba73%2F6ad16bf9b7edb0a28ab3574d313014f32392aa7f9508686b63bfacfafc7a9735.svg?alt=media) **\[Optimize]→ Einstellungen → Kanäle**.
2. Wählen Sie oben rechts **Kanal erstellen**.
3. Geben Sie dem Channel einen **Namen**.
4. Wählen Sie aus, was **Typ** welcher Art von Kanal dies im Dropdown-Menü ist.
5. ![](https://1698965099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Einschalten]** **Regeln hinzufügen, um den Kanalverkehr zu identifizieren**.
6. Von hier aus können Sie die Regeln Ihres Channels einrichten, um Gruppe zu identifizieren und zu gutschreiben.
   * Erfahren Sie mehr über Ihre Optionen zur Konfiguration von [Regeln zur Identifizierung](/brand/de/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/set-up-rules-to-identify-channel-traffic.md) und [Gutschriftengruppen](/brand/de/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/credit-groups-explained.md), den Bestandteilen eines Optimize Channel.
7. Wählen Sie **Speichern**.

   <div data-with-frame="true"><figure><img src="https://1698965099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FWxNPB6pGT4s3Oowz5oKU%2FScreenshot%202026-05-25%20at%2010.45.39.png?alt=media&amp;token=27904ba6-d0b7-47ca-b0fd-b3db460d20a1" 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 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/de/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-channels/create-an-optimize-channel.md?ask=<question>&goal=<user_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.
