Adobe Omnichannel Customer Engagement, Product by Product

Adobe omnichannel customer engagement means every channel works from one shared customer profile instead of its own list. Adobe Experience Platform and Real-Time CDP hold that profile, with its identities, audiences and consent. Journey Optimizer, Adobe Campaign and Adobe Target act on it across email, SMS, push, app and web. AEM supplies the content, and Customer Journey Analytics measures what happened.

This post looks at the whole stack rather than one tool. You'll see which product does which job and a channel-by-channel table. Then come three worked examples, a build order in three stages, common pitfalls and what drives the cost. For journey design inside Journey Optimizer, such as channel choice, exit rules and frequency caps, read our post on omnichannel customer journeys with AJO.

What does omnichannel customer engagement mean in Adobe's stack?

In Adobe's stack, omnichannel means shared data and shared rules, not simply more channels. Say a customer leaves a cart in your app. They should see the same offer and consent treatment everywhere, and every channel should stop once they buy.

Adobe builds this on Adobe Experience Platform (AEP). Journey Optimizer is one of four applications built natively on AEP, alongside Real-Time CDP, Customer Journey Analytics and Adobe Mix Modeler. It shares AEP's Real-Time Customer Profile, identity graph and data governance, so it works from the same customer data without a separate integration.

A quick naming note. At Adobe Summit in April 2026, Adobe introduced Adobe CX Enterprise, grouped around customer engagement, content supply chain and brand visibility. You'll still see the Adobe Experience Cloud name on many Adobe pages. The product names below are the ones Adobe's documentation uses today.

Which Adobe product does what?

Each product owns one job, and trouble starts when two products try to own the same one. Here's the split as Adobe's documentation describes it.

Experience Platform and Real-Time CDP: the data layer

Real-Time CDP brings known and anonymous data from many enterprise sources into customer profiles. Identity Service links the identifiers one person leaves behind into an identity graph. These include a CRM ID, an email address and a browser cookie. So when someone browses anonymously on a tablet and later logs in, that tablet activity joins their known profile.

Segmentation Service then builds audiences in three ways. Streaming segmentation updates membership as new data arrives. Batch segmentation runs every 24 hours. Edge segmentation evaluates instantly on Adobe's Edge Network, for same-page and next-page personalization. Destinations then send audiences to ad platforms, marketing tools and other systems. Our guide to Real-Time CDP covers the basics.

Journey Optimizer: real-time journeys and campaigns

Adobe Journey Optimizer (AJO) runs real-time, event-triggered journeys and scheduled campaigns from one application. In a journey, each person moves at their own pace, through waits, conditions and branches. Action campaigns send to an audience on a schedule. API-triggered campaigns send one message when another system calls, such as an order confirmation.

AJO's native outbound channels are email, push, SMS, MMS, RCS, iOS Live Activities, direct mail, WhatsApp and LINE. On the inbound side it covers in-app messages, web, code-based experiences and content cards. Its Decisioning feature keeps one catalog of offers and picks the best one for each person using rules and rankings. Custom actions call third-party systems that AJO doesn't reach natively. For complex, multi-step batch work on relational data, AJO also has orchestrated campaigns.

Adobe Campaign: batch programs at scale

Adobe Campaign v8 is built for large, multi-step batch programs, and Adobe runs it as a Managed Cloud Service. It also has a real-time messaging server for transactional sends, such as password resets. Some teams run Campaign and AJO side by side. AJO can even send email, push and SMS through Campaign's transactional messaging. Our Journey Optimizer vs Adobe Campaign comparison explains how to split the work.

Adobe Target: onsite and in-app personalization

Adobe Target handles testing and personalization on websites, mobile sites and apps. Target Standard covers A/B tests and rules-based targeting. Target Premium adds Automated Personalization, Auto-Target and Recommendations.

Real-Time CDP can share audiences and profile attributes with Target, and since August 2026 so can Journey Optimizer. Same-page and next-page personalization need the Web SDK or the Edge Network API.

AEM: the content layer

Adobe Experience Manager (AEM) supplies the content. Its Content Fragments are structured, channel-neutral pieces of content that any app can pull through a GraphQL API. AJO can use AEM Content Fragments in its email content. After you publish a fragment in AEM, it reaches real-time (unitary) journeys in about five minutes.

Customer Journey Analytics: cross-channel measurement

Customer Journey Analytics (CJA) reads data from Experience Platform and lets you analyze it in sequence across channels. Call center, point-of-sale and online data can sit in one report. CJA can also take in AJO's data to show the impact of journeys, campaigns and offers.

Marketo Engage and AJO B2B Edition: the B2B layer

For B2B teams, Marketo Engage runs lead-based programs. Journey Optimizer B2B Edition adds account journeys built around buying groups, so a whole account moves through stages together. It runs on Experience Platform, including Real-Time CDP B2B, and can work alongside lead-based campaigns in Marketo Engage.

What should you use for each channel or job?

Use the shared profile for everything, then pick the product by timing and surface. Treat this table as a starting point. Your licenses and existing tools can change the answer.

Where two products overlap, such as web personalization in both Target and AJO, decide once per use case and write it down. Our page on the Adobe Campaign and Journey Optimizer integration shows how the two messaging tools can share audiences and definitions.

How does omnichannel marketing with Adobe work in practice?

The pattern is always the same: one event or audience, one set of rules, several channels. These three examples are illustrative, not client results.

Cart recovery

A shopper adds items in your app, then leaves. The cart event starts an AJO journey. After a wait, app users get a push, and people without the app get an email. If they come back to the website, Target or AJO's web channel can show the same cart on the homepage. Once the order event arrives, the journey ends on every channel at once.

Onboarding

A new bank customer opens an account. A journey sends a welcome email, then an in-app message on first login, then a push if a key setup step is still missing. Each step checks the profile first, so someone who already set up their card doesn't get the reminder. The monthly newsletter stays in a scheduled campaign, outside the journey.

Next best offer

A telecom provider wants one offer per customer, shown the same way everywhere. Offers live in the Decisioning catalog with eligibility rules and a ranking. The website asks for a decision through a code-based experience. The email pulls the offer into a placement, and an SMS carries a short version. Because each channel asks the same engine, customers are far less likely to see one price in email and another in the app.

How do you build Adobe omnichannel engagement in stages?

Build it in three stages: data foundation first, then journeys, then decisioning and measurement. In my experience, teams that start with journeys end up coming back to fix the data.

Stage 1: data foundation

• Agree which identities you'll use, such as CRM ID, email, phone and app or web IDs, and how they link.
• Model profile and event data in Experience Data Model (XDM) schemas.
• Stream the events that will trigger journeys, and batch the rest.
• Capture consent for each channel and load it onto the profile.
• Build a few audiences and send one to a destination, to prove the profile works.

Stage 2: journeys and channels

• Start with two or three valuable journeys, such as cart recovery and onboarding.
• Add channels one at a time, with a consent check on each.
• Set exit rules and contact limits before you scale.
• Decide what stays in Campaign or in scheduled campaigns.

Stage 3: decisioning and measurement

• Move offers into Decisioning so every channel uses one catalog.
• Share audiences from the profile with Target for onsite and in-app work.
• Report in Customer Journey Analytics across online and offline data, with holdout groups.

As an indicative planning range, stage 1 often takes 3 to 6 months. Stage 2 adds another 2 to 4 months for the first journeys. These aren't Adobe figures. Source systems, data quality, the number of channels and the state of your consent data all move them.

Where do omnichannel programs usually go wrong?

Most problems come from four places: identity, consent, data latency and channel silos.

Identity. If your app, website and CRM use different IDs that never link, one person becomes three profiles. Three journeys can then message them at the same time. Pick a primary identity early and test the graph with real records.

Consent. AJO leaves out people who opted out, but by default it treats an empty consent field as consent. The Web SDK only enforces the data collection choice automatically, so other preferences need enforcing in your own processes. Automated consent policy enforcement comes with the Healthcare Shield or Privacy and Security Shield add-on.

Data latency. Not every audience is real time. Batch audiences refresh once a day. An event-triggered journey can take up to 5 minutes to run its first action. An audience qualification step can take up to 10 minutes to start listening. Match each use case to the speed it really needs, and don't stream data you only use in batch.

Channel silos. If the email, app and web teams each keep their own rules, customers still feel three brands. Shared audiences, one offer catalog and a single owner for contact rules fix this more than any tool. Our post on why programs need one accountable implementation team goes further.

What drives the cost of an Adobe omnichannel platform?

Adobe doesn't publish prices for these products, so your cost comes from what you license and how you use it. These are the drivers worth sizing first.

• Profiles. Real-Time CDP is licensed per 1,000 person profiles. AJO counts engageable profiles, meaning people you tried to engage in the past 12 months. Anonymous profiles you engage count too, which is why Adobe recommends a 14-day expiry for ones that haven't been seen or engaged.
• Package and edition. Real-Time CDP comes in B2C, B2B and B2P editions, each in Prime or Ultimate. AJO's product description lists journeys in its Journeys and its Campaigns and Journeys packages, so check which one you hold.
• Channels and volume. AJO channels come as add-ons: Outbound Delivery, Mobile, Web or All Channels. The Outbound Delivery and Mobile add-ons allow an average of up to 60 email or push messages per engageable profile a year. You can buy more message packs.
• Decisioning and privacy. Decisioning is a separate AJO add-on. The Shield add-ons, extra sandboxes and extra data volume cost more again.
• Analytics. CJA is licensed on rows of data, the daily average of rows available for analysis.
• People. Implementation, content production and the team that runs journeys each week are real costs too, so budget for them next to the licenses.

Our Journey Optimizer pricing factors page goes through these drivers in more detail.

What should you do next?

Start small with Adobe omnichannel customer engagement, but start with the data. Here's a short checklist for the next month.

• List your channels, the tool that sends each one today and who owns it.
• Map the identifiers each system holds and how they'd link.
• Check how consent is captured for each channel and whether it reaches the profile.
• Pick two journeys with clear revenue or cost value, and note the data each needs.
• Decide which work stays in batch, in Campaign or in scheduled campaigns.
• Agree how you'll measure, including a holdout group.
• Size profiles, channels and message volume before you talk to Adobe.

DWAO is an Adobe Gold Partner with Adobe-certified consultants across Real-Time CDP, Journey Optimizer, Campaign, Target and Analytics. You can see how we activated Tata Consumer's first-party audiences with Real-Time CDP. If you'd like a second view on your build order, our omnichannel marketing page is a good place to start.