[Limited Availability]{class="badge informative"}

Get started with custom channels get-started-custom-channel

On this page: Learn what custom channels are in Adobe Journey Optimizer, how they compare to custom actions, and the overall workflow for bringing any outbound HTTP endpoint into AJO so you can use it in campaigns and journeys.

AVAILABILITY
This capability is available in Limited Availability. Contact your Adobe representative to gain access.

Journey Optimizer’s Custom channels capability lets you bring any outbound channel into Journey Optimizer so you can use it in campaigns and journeys—just like any native channel. Using the Channel Builder, administrators can create and configure new channels without engineering involvement, and marketers can immediately start using them to communicate with customers.

What problem does it solve? why-custom-channels

Journey Optimizer natively supports Email, SMS, Push notifications, WhatsApp, LINE, and other channels. However, many organizations use messaging platforms that are not natively integrated—such as WeChat, Kakao Talk, Messenger, or an external provider—and want to use them in Journey Optimizer for orchestration and campaign creation while still delivering with their own vendor.

Custom channels fill this gap: they enable you to use any outbound HTTP endpoint as a full Journey Optimizer channel, unlocking:

  • Full channel capabilities – Optimization (content experimentation and targeting), OOTB reporting and monitoring, consent and governance enforcement, and expression fragments.
  • Unified orchestration – Manage all your messaging channels in a single place, regardless of the underlying delivery provider.
  • No-code setup – Admins configure the channel through the Channel Builder UI; no custom code or engineering effort is required.

Custom channel vs. custom actions custom-channel-vs-custom-action

If you have used custom actions in Journey Optimizer journeys before, custom channels address a different set of use cases.

Use custom channels when you need to send messages to end users through a platform not natively supported in Journey Optimizer—such as WeChat, Kakao Talk, or a custom messaging gateway. Custom channels are available in campaigns and journeys, and support:

  • Full personalization through the personalization editor, similar to native outbound channels
  • Visual/form payload editor, preview and proof
  • Content experimentation and targeting
  • OOTB reporting and monitoring
  • Multiple API credentials and channel configurations
  • RBAC/ABAC

Custom channels support POST as the only HTTP method.

Use custom actions when you need to retrieve data from or push information to an external system—such as a call center, logging platform, or offline database—as a step within a journey. Custom actions are available in journeys only and support GET, PUT, and POST methods.

TIP
As a general recommendation, use custom channels for channel use cases where you are sending messages to end users. For other connector-like use cases that are needed in journeys—such as retrieving data or triggering external systems—you can continue to use custom actions.

Use cases use-cases

Custom channels are ideal for:

  • Unsupported messaging platforms – Channels like WeChat, Kakao Talk, Messenger, Telegram, or regional messaging services that do not have a native Journey Optimizer channel.
  • Custom delivery providers – Organizations that have invested in an external provider they want to keep using for message delivery, but prefer to leverage Journey Optimizer for orchestration, personalization, and campaign management.
  • Legacy channels – Proprietary or legacy messaging gateways that expose an HTTP endpoint.
  • Industry-specific channels – Secure messaging for healthcare, banking alert systems, or government notification services.

How it works how-it-works

Setting up and using a custom channel follows the main stages below:

  1. Configure (Admin) – An administrator creates a custom channel in the Channel Builder, defining the endpoint, authentication, throttling policy, and message payload structure. A channel configuration is then created and linked to the custom channel.
  2. Create (Marketer) – A marketer adds the custom channel to a journey or campaign, selects a channel configuration, and authors the message payload using Journey Optimizer’s personalization editor.
  3. Send – When a profile qualifies, Journey Optimizer sends the personalized payload to the configured endpoint. The external system processes the call and delivers the message.
  4. Monitor (Admin/Marketer) – Administrators and marketers can monitor the custom channel’s performance and reliability through Journey Optimizer’s reporting and monitoring dashboards.
recommendation-more-help
journey-optimizer-help