在此页面上：了解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
自定义渠道非常适合：
- 不受支持的消息传送平台 — 微信、Kakao Talk、Messenger、Telegram等频道或没有本机Journey Optimizer频道的地区消息传送服务。
- 自定义投放提供商 — 已投资于外部提供商且希望继续使用外部提供商进行邮件投放的组织，但更愿意利用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.