在此頁面上：瞭解Adobe Journey Optimizer中的自訂管道、它們與自訂動作的比較，以及將任何輸出HTTP端點帶入AJO的整體工作流程，以便用於行銷活動和歷程。
Journey Optimizer的 自訂管道 功能可讓您將任何傳出管道匯入Journey Optimizer，以便用於行銷活動和歷程，就像任何原生管道一樣。 使用頻道產生器，管理員可以建立及設定新的頻道，而不需要工程部門的介入，行銷人員可以立即開始使用這些頻道與客戶通訊。
它可解決什麼問題？ why-custom-channels
Journey Optimizer原生支援電子郵件、簡訊、推播通知、WhatsApp、LINE和其他頻道。 不過，許多組織使用的傳訊平台並非原生整合（例如WeChat、Kakao Talk、Messenger或外部提供者），且想要在Journey Optimizer中使用這些平台進行協調與行銷活動建立，同時仍由自己的供應商提供。
自訂通道填補此空白：可讓您使用任何輸出HTTP端點作為完整Journey Optimizer通道，解除鎖定：
- 完整通道功能 — 最佳化（內容實驗、目標定位和業務規則）、OOTB報告和監控、同意和治理執行，以及運算式片段。
- 整合式協調流程 — 在單一位置管理您的所有傳訊通道，無論基礎的傳遞提供者為何。
- 無程式碼設定 — 管理員透過Channel Builder UI設定頻道；不需要自訂程式碼或工程作業。
自訂管道與自訂動作 custom-channel-vs-custom-action
如果您之前在Journey Optimizer歷程中使用過自訂動作，自訂管道會處理一組不同的使用案例。
當您需要透過Journey Optimizer未原生支援的平台（例如WeChat、Kakao Talk或自訂訊息閘道）傳送訊息給使用者時，請使用自訂頻道。 行銷活動和歷程中提供自訂頻道，以及支援：
- 透過個人化編輯器完全個人化，類似於原生傳出頻道
- 視覺/表單裝載編輯器、預覽和校訂
- 內容實驗與定位
- OOTB報告與監控
- 多個API認證和通道設定
- RBAC/ABAC
自訂管道支援POST作為唯一的HTTP方法。
當您需要從外部系統（例如客服中心、記錄平台或離線資料庫）擷取資料或推送資訊至外部系統（例如客服中心、記錄平台或離線資料庫）時，請使用自訂動作，作為歷程中的步驟。自訂動作僅在歷程中可用，並支援GET、PUT和POST方法。
使用案例 use-cases
自訂管道適用於以下情況：
- 不支援的訊息平台 — 沒有原生Journey Optimizer管道的WeChat、Kakao Talk、Messenger、Telegram或地區訊息服務等管道。
- 自訂傳遞提供者 — 已投資外部提供者的組織，他們想要繼續使用傳送訊息的郵件，但偏好利用Journey Optimizer進行協調、個人化和行銷活動管理。
- 舊版管道 — 公開HTTP端點的專有或舊版傳訊閘道。
- 特定產業管道 — 醫療保健、銀行警示系統或政府通知服務的安全訊息。
運作方式 how-it-works
設定和使用自訂管道會遵循以下主要階段：
- 設定 （管理員） — 管理員會在 頻道產生器 中建立自訂頻道，定義端點、驗證、節流原則及訊息裝載結構。 接著會建立管道設定並連結至自訂管道。
- 建立 （行銷人員） — 行銷人員將自訂管道新增至歷程或行銷活動、選取管道設定，並使用Journey Optimizer的個人化編輯器編寫訊息裝載。
- 傳送 — 當設定檔符合資格時，Journey Optimizer會將個人化裝載傳送至設定的端點。 外部系統處理呼叫並傳遞訊息。
- 監視 （管理員/行銷人員） — 管理員和行銷人員可以透過Journey Optimizer的報告和監視儀表板來監視自訂頻道的效能和可靠性。
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page introduces Journey Optimizer custom channels, which let you bring any outbound HTTP endpoint into Journey Optimizer as a full channel using the Channel Builder, explains how they differ from custom actions, and outlines the configure, create, send, and monitor workflow.
Intents:
- Understand what custom channels are and what problem they solve
- Decide when to use a custom channel versus a custom action
- Identify use cases suited to custom channels, such as unsupported messaging platforms or custom delivery providers
- Understand the end-to-end workflow of configuring, creating, sending, and monitoring a custom channel
- Learn which capabilities custom channels support in campaigns and journeys
Glossary:
- Custom channels: A capability that lets you bring any outbound channel into Journey Optimizer for use in campaigns and journeys, like a native channel (product-specific)
- Channel Builder: The interface where administrators create and configure new custom channels without engineering involvement (product-specific)
- Custom actions: A capability for retrieving data from or pushing information to an external system as a step within a journey, available in journeys only (product-specific)
- Channel configuration: A configuration created and linked to the custom channel that a marketer selects when adding the channel to a journey or campaign (product-specific)
Guardrails:
- Custom channels support POST as the only HTTP method.
- Custom actions are available in journeys only and support GET, PUT, and POST methods.
- Configuring a custom channel is an administrator task performed in the Channel Builder; adding the channel to a journey or campaign is a marketer task.
Terminology:
- Canonical name: Custom channels — Acronym: n/a — variants: custom channel capability, custom channel
- Synonyms: “Channel Builder” = the UI used to create and configure custom channels
- Do not confuse: “Custom channels” (send messages to end users through a platform not natively supported, available in campaigns and journeys, POST only) ≠ “Custom actions” (retrieve data from or push information to an external system, available in journeys only, GET/PUT/POST)
FAQ:
- Q: What are custom channels? — They let you bring any outbound HTTP endpoint into Journey Optimizer as a full channel so you can use it in campaigns and journeys, just like a native channel.
- Q: When should I use a custom channel instead of a custom action? — Use a custom channel when you need to send messages to end users through a platform not natively supported, and use a custom action when you need to retrieve data from or push information to an external system as a step within a journey.
- Q: Which HTTP method do custom channels support? — Custom channels support POST as the only HTTP method.
- Q: What are the main stages of setting up and using a custom channel? — Configure the channel in the Channel Builder (Admin), create the message in a journey or campaign (Marketer), send the personalized payload when a profile qualifies, and monitor performance through reporting and monitoring dashboards.
- Q: Do I need engineering effort to set up a custom channel? — No, administrators configure the channel through the Channel Builder UI; no custom code or engineering effort is required.
- Q: What are typical use cases for custom channels? — Unsupported messaging platforms such as WeChat or Kakao Talk, custom delivery providers, legacy messaging gateways that expose an HTTP endpoint, and industry-specific channels such as healthcare or banking notifications.