AJO October 2026: Custom Channels GA, Stop Action, Validate

Adobe Journey Optimizer's October 2026 updates make custom outbound channels generally available, add a Stop action to the journey canvas, and introduce an on-demand Validate button. Together they change how teams plug in non-native messaging channels and how they keep large journeys manageable. A limited-availability authentication option for custom actions and several Coworker skills fill out the month.

Key takeaways

• Custom outbound channels reached General Availability on 2 October 2026, and gained Decisioning in the payload, business rules, and selection in API-triggered campaigns.
• The Stop action (12 October 2026) removes a profile from up to five inbound activities or experiences from inside a journey, separate from journey exit.
• The Validate button (9 October 2026) runs configuration and message checks when you choose to, instead of repeatedly during editing.
• HMAC-signed JWT authentication for custom actions (13 October 2026) is Limited Availability and requires a request to your Adobe representative.
• Coworker skills for performance, hygiene and execution timing are worth trying on a few journeys first, and their output belongs in a review, not straight into production.

What changed in Adobe Journey Optimizer in October 2026

The month's changes fall into three groups: channels, journey authoring, and AI assistance through Adobe CX Enterprise Coworker. The table lays them out with their availability dates so you can see who needs to look at what.

Adobe also lists several items as coming soon, with the warning that they are subject to change. Those include AI recommendation cards on the home page when a journey alert fires, journey creation from the Coworker right rail, fewer step events for wait and event activities, and a unified calendar for campaigns, journeys and orchestrated campaigns. Plan around the shipped items, and watch the others rather than building anything on them.

Custom outbound channels are now generally available

The biggest item for most enterprise teams is the move of custom outbound channels from Limited Availability to General Availability, dated 2 October 2026. Administrators can bring any outbound HTTP-based messaging channel into Journey Optimizer through a no-code Channel Builder. Adobe names WeChat, Kakao Talk, Messenger and proprietary providers as examples.

Why this matters in practice. Plenty of organisations run a regional messaging app, an in-house notification service, or a partner's delivery API that never fit into email, SMS or push. The usual answer was a custom action in a journey that fired a webhook and hoped for the best. That worked, but the message sat outside the normal tooling. Reporting was separate, consent checks were manual, and content could not be tested like native messages.

With a custom channel, the same capabilities native channels have apply: personalization with the expression editor, content experimentation, preview and proof, out-of-the-box reporting, and consent and governance enforcement. It is available across campaigns, journeys and orchestrated campaigns.

The GA release also adds three things:

1. Journey Optimizer Decisioning can be used in the custom channel payload through the Personalization Editor, the same way as in code-based experiences.
2. Business rules can be applied to custom channels, as they already can on native channels.
3. Custom channels can now be selected in the channel list for API-triggered campaigns, which was not possible before.

The business rules item deserves attention. If you capped frequency on email and push but had a custom action sending a third kind of message, those caps never saw it. Moving that traffic onto a custom channel brings it under the same rule set. That is a governance gain you can explain to a compliance lead in one sentence.

Who should migrate existing webhook flows, and who should wait

Not every custom action should become a custom channel. A useful test: is the thing you are sending a message to a person, on a channel, that you would want to report on, personalize, test and govern like any other message? If yes, it is a candidate. If it is a system-to-system call, such as updating a CRM field or notifying an internal queue, it stays a custom action.

Teams that gain the most:

• Markets where a messaging app matters more than email, and where the current send path is a webhook with hand-built payloads.
• Teams whose consent or frequency rules are currently enforced by convention instead of by the platform.
• Groups running orchestrated campaigns that need the same channel available in both campaign and journey contexts.

Teams that can wait: anyone with a stable, low-volume webhook that nobody complains about and no governance gap. Migration has a cost, and the benefit has to be larger than that cost.

A sensible first step is small. Pick one channel and one journey. Build the channel in Channel Builder, replicate one message, and use preview and proof to compare it to what the old path produced. Check the payload that reaches the provider, not just the screen. Only then plan the rest. Your provider's API documentation and Adobe's own custom channel documentation are the places to confirm field mappings and authentication specifics.

The Stop action and what it does to journey design

The Stop action, available from 12 October 2026, is a new activity on the journey canvas. It removes a profile from up to five inbound activities or experiences directly from a journey. Adobe describes it as decoupling inbound disqualification from journey exit.

That phrase is easier to understand with a scenario. Suppose a customer is in a journey that also keeps them eligible for an inbound offer experience. They complete a purchase partway through. Before, if you wanted the inbound offer to stop appearing, you often had to end their journey or build an awkward parallel construct to signal disqualification. With the Stop action, the journey can carry on, perhaps sending an order confirmation and a follow-up, while the inbound experience quietly stops applying to that profile.

What to do with it:

• Audit live journeys for places where a profile leaves a journey early only to stop an inbound experience. Those are candidates for simplification.
• Document which inbound activities or experiences each Stop action targets. The cap is five per action, so a journey that needs more will need more than one action.
• Test with a profile that is in the inbound audience and one that is not, and confirm the experience stops for the first and nothing changes for the second.

What not to do: do not rip out working exit logic just because a tidier option exists. Change journeys when you are already editing them for another reason, and keep a version history so you can compare behaviour.

On-demand validation and large journey canvases

The new Validate button, dated 9 October 2026, runs configuration checks, including message checks, when you are ready to test or publish. Adobe's stated aim is to reduce repeated checks during editing and help keep larger journey canvases responsive.

For designers working on big canvases, the change is mostly good news. Constant background checking is a drag on large journeys, and deferring it should make editing feel lighter. The trade-off is behavioural. Errors that used to appear as you built may now appear only when you press Validate. Someone who is used to being told about a misconfigured action the moment it is added will find out later.

So update the habit and the checklist. A short pre-publish routine works well:

1. Press Validate before every test run, not just before publishing.
2. Fix everything it reports, message checks included, before sending test profiles through.
3. Press Validate again after the fixes, since a fix in one place can expose a problem elsewhere.
4. Record the result in the change ticket so reviewers can see that validation happened.

If you have a QA step that assumed the editor would catch problems continuously, rewrite it. The most likely failure here is not a bug in the product. It is a team that assumes validation already happened.

HMAC-signed JWT for custom actions

This one is narrow. Certificate-based custom authentication now supports JWT client assertions signed with your OAuth client secret, using HS256, HS384 or HS512, in the client_secret_jwt style. It is an alternative to Adobe's RSA certificate. Configurations that do not specify an algorithm continue to use RS256, so nothing changes for existing setups.

The availability date is 13 October 2026, and it is in Limited Availability for a set of customers. You need to contact your Adobe representative to request access. Do not plan a release around it until you have that answer, and expect details to change before wider availability.

Who should care: integration engineers whose downstream API expects a client-secret-signed assertion and who have been unable to use Adobe's certificate approach. Everyone else can ignore it for now. If your security team asks, the right answer is that existing authentication is unchanged and this is an option for specific partner requirements. Confirm exact configuration steps in the Custom actions and External data sources documentation.

Coworker skills: what to try and what to skip

Three Coworker skills landed in October 2026, all in Adobe CX Enterprise Coworker chat.

• The Business Performance Analysis skill (7 October 2026) analyses journey performance and gives concrete optimization recommendations.
• The Journey Hygiene Analysis skill (20 October 2026) scans journeys for configuration hygiene issues and suggests fixes. The first release has seven checks, covering missing or generic names, stale draft journeys, stale live journeys, oversized journeys, long-existing closed journeys, and similar action or event names.
• The journey execution timeline skill (1 October 2026) works for Read Audience journeys only. It analyses execution duration, P95 and P99 latency, export-job-creation-to-first-profile latency, and latency by journey, version and recurrence, and identifies the slowest versions and runs.

The hygiene skill is the easiest win. Naming and clutter problems are tedious, rarely urgent, and expensive when a new hire inherits a sandbox full of journeys called Test 2 final. Run it, and treat the list as a cleanup backlog. Be careful with stale live journeys in particular. A journey that looks quiet may be seasonal. Check with the owner before changing anything.

The execution timeline skill is valuable if you run large scheduled Read Audience journeys and care about when messages actually go out. Compare its numbers against what your own monitoring shows before trusting it for service-level conversations. If you do not use Read Audience journeys, skip it.

The performance skill is the one to approach with the most scepticism. Recommendations are only as good as the question asked and the context around it. Use it to generate hypotheses, then verify with a controlled test.

A rollout plan and how to measure the results

A staggered rollout beats a big-bang adoption. Here is one way to divide the work.

Measurement should be modest and honest. For custom channels, compare delivery and error behaviour before and after migration, and check that reporting now shows the channel alongside native ones. For validation, track how many issues are caught before a test run versus after; the direction you want is fewer surprises late. For the Stop action, count journeys simplified and confirm no regression in inbound targeting. For hygiene, count the items resolved. None of these needs a dashboard project. A shared spreadsheet and a monthly review will do.

Where an implementation partner helps, and where you can manage alone

Much of this is within reach of a competent in-house team. The Validate habit, the hygiene cleanup and a first Stop action replacement are configuration work that a journey designer can do with the documentation open.

A partner earns their fee in the harder places:

• Designing a custom channel for a provider with a complicated API, particularly where authentication, payload structure and Decisioning inside the payload all interact.
• Moving a large estate of webhook-based sends onto custom channels without a gap in consent or frequency enforcement.
• Rationalising a sprawling set of journeys where exit logic, inbound experiences and governance rules have grown tangled.
• Judging whether a Limited Availability capability such as HMAC-signed JWT is worth the dependency on an Adobe programme.

If you are weighing outside help, start by reviewing Adobe Journey Optimizer partners and use find partners to narrow by region and specialism. When you are ready to write a brief, the Adobe Journey Optimizer RFP template gives you a structure for scope, channels, integrations and success measures. Name your custom channel candidates explicitly in that brief, since partners price them very differently depending on the provider API involved.

Three things not to do. Do not migrate every webhook because a new feature exists. Do not rely on a Coworker suggestion as the only review of a live journey. And do not build plans around items Adobe lists as coming soon; they may change or arrive later than expected.

Sources

• Adobe Experience League: Journey Optimizer release notes — October 2026 updates for channels, journeys and Coworker skills, last updated 22 October 2026.