Adobe Journey Optimizer Use Cases: 10 Journey Examples

A journey in Adobe Journey Optimizer is an automated flow where each customer moves at their own pace: they enter on an event or an audience, get messages across channels, wait, go through conditions and exit once they hit the goal. If you already know what Adobe Journey Optimizer (AJO) is and want to know which journeys to build first, and how, this is the playbook: ten journeys, each with its trigger, steps, the data you need, the KPI and the mistake we see most often.

At WolfSellers we implement Adobe Journey Optimizer on Adobe Experience Platform (AEP) for companies across North America and Mexico. If you're still evaluating the product, start with what Adobe Journey Optimizer is and how we implement it. Everything we say about Adobe features comes from Adobe's Experience League documentation, reviewed in November 2026.

---

The 10 Adobe Journey Optimizer journeys at a glance

The timings in each journey are our starting points, not Adobe rules: tune them to your buying cycle.

Before you build: campaigns, entry types, re-entrance and frequency

Journey or campaign: which one to use

Adobe's rule of thumb: if each customer should move at their own pace with real-time logic, it's a journey; if it's one message to an audience on a date, it's a campaign.

Orchestrated campaigns require a license that includes a Journey Optimizer campaigns package. If a message triggered by API needs follow-up steps, Adobe recommends a unitary event journey.

The four ways a profile enters a journey

On recurring read audience journeys, incremental read means that from the second run on, only profiles new to the audience enter.

Entry, re-entrance and exit rules

1. A profile can't be in the same journey twice at the same time, not even across live versions.
2. Re-entrance is on by default, with a 5-minute wait period you can raise to 90 days. Turn it off for one-time journeys.
3. Blocking re-entrance doesn't last past 91 days, because AJO deletes a profile's journey data 91 days after entry. If something must never repeat, add a condition on a profile attribute.
4. Supplemental identifiers (order, policy or subscription number) create one journey instance per identifier, up to 10 concurrent instances per profile. They don't work in audience qualification journeys.
5. Exit criteria remove the profile at any step when an event happens, such as a purchase, or when it qualifies for an audience.

Waits, conditions and business rules

• Wait: a fixed duration (up to 90 days), a date calculated with an expression, or Send-Time Optimization. No profile spends more than 91 days in a journey.
• Conditions: the Optimize activity replaced the old Condition activity; that's where you set conditions, path targeting and path experiments.
• Reactions: the Reaction activity branches on whether the customer opened or clicked a message from the same journey, with a timeout from 40 seconds to 90 days.
• Experience events: since July 8, 2025, new organizations can't use them in condition expressions. Adobe recommends audiences, computed attributes or Adobe Data Distiller.
• Business rules: per-channel frequency caps for marketing messages (per hour, day, week or month, optionally across several channels), journey caps with priority scores, and quiet hours.

10 Adobe Journey Optimizer journey examples, step by step

1. Welcome and onboarding for new customers

Goal: turn a sign-up into a first purchase or an app install.

How it enters: a unitary event for account creation or subscription, or qualification into a streaming new-customer audience. Adobe suggests both.

Steps and conditions:

1. Immediate welcome email delivering what you promised at sign-up.
2. Wait 2 days.
3. Condition: did they buy or install the app? Check it with an audience or a profile attribute.
4. If not, a second message by SMS or push, if they consented to that channel.
5. Exit criteria: purchase event.

Channels: email, SMS and push.

Data you need: a sign-up event with an identity (email or CRM ID), consent per channel and a commerce.purchases event.

Success metric: share of new sign-ups with a first purchase in 30 days.

Common mistake: leaving re-entrance at its default. A duplicate sign-up sends the welcome again.

2. Cart abandonment

Goal: recover the sale from someone who added items and didn't check out.

How it enters: a unitary event for add to cart. If you'll send a single message and your ecommerce platform already detects abandonment, an API-triggered campaign also works.

Steps and conditions:

1. Wait based on your buying cycle. Adobe's example uses 24 hours without completing checkout.
2. Exit criteria on purchase.
3. Email with the cart items.
4. Reaction: if they don't open or click within 2 days, push or SMS.
5. Exit after 7 days without a purchase, also as in Adobe's example.

Channels: email, push and SMS.

Data you need: XDM commerce.productListAdds and commerce.purchases events with productListItems (SKU, name, quantity, price and image).

Success metric: recovery rate (orders over entries) and recovered revenue.

Common mistake: personalizing only with the event that started the journey: anything added later never reaches it. For the latest cart, Adobe recommends computed attributes or Data Distiller.

3. Browse abandonment

Goal: turn a product view into a cart.

How it enters: a daily read audience with incremental read, over "viewed products in the last 24 hours and didn't add to cart." We don't trigger it on every product view: unitary events share the 5,000 TPS limit with all your real-time journeys.

Steps and conditions:

1. The audience runs once a day.
2. Condition: exclude anyone already in the cart journey.
3. One message with the last product viewed and alternatives.
4. Exit on add to cart or purchase.

Channels: email and push.

Data you need: a commerce.productViews event and an AEP computed attribute with the last product viewed (MOST_RECENT function), a use case Adobe documents.

Success metric: clicks that end in a cart or an order within 7 days.

Common mistake: counting anonymous visitors. You can only message profiles with a known identity and consent.

4. Order confirmation and shipping updates

Goal: keep customers informed and cut "where is my order?" contacts.

How it enters: for a single message, a transactional API-triggered campaign fired by your order system, the example Adobe gives. For the full sequence, a unitary event journey with the order number as a supplemental identifier.

Steps and conditions:

1. Order placed: immediate confirmation.
2. "Shipped" event from your logistics system: message with the tracking number.
3. "Delivered" event: delivery confirmation, which also triggers journey 5.

Channels: email, SMS and push.

Data you need: order number (commerce.order.purchaseID), items, total, address and tracking number in the payload.

Success metric: messages delivered on time and fewer order-status contacts.

Common mistake: slipping promotions in. Adobe defines the transactional type for non-commercial emails, which reach even people who unsubscribed from marketing.

5. Post-purchase and review request

Goal: get the review and set up the next order.

How it enters: a unitary delivery event, the example Adobe uses for feedback requests.

Steps and conditions:

1. Wait until a date calculated from the event, for example 3 days after delivery.
2. Email asking for a review.
3. Reaction: if they don't open within 3 days, one reminder.
4. Exit when the review is submitted or after 10 days.

Channels: email and push.

Data you need: a delivery event with date and SKU, and a "review submitted" event.

Success metric: reviews over delivered orders.

Common mistake: counting from the order date. And in a calculated wait, don't append Z or a time zone offset to the date: Adobe warns profiles can get stuck.

6. Replenishment based on the consumption cycle

Goal: reach customers before they run out (pet food, supplements, ink cartridges).

How it enters: a daily read audience with incremental read, over "their last purchase in this category was N days ago," where N is the product cycle.

Steps and conditions:

1. Entry a few days before they run out.
2. Message with a one-click reorder link.
3. Wait 3 days, with exit on purchase.
4. Reminder by push or SMS.

Channels: email, push and SMS.

Data you need: purchases with SKU, category and quantity, plus a computed attribute with the last purchase date (MAX). Computed attributes look back up to 6 months and, with windows longer than 7 days, refresh weekly or monthly; fast refresh updates them daily.

Success metric: repurchase within the expected cycle.

Common mistake: one cycle for the whole catalog, or ignoring quantity: someone who bought two bags takes twice as long.

7. Back in stock or price drop

Goal: alert interested customers when a product returns or its price drops.

How it enters: a business event, the case Adobe documents for back-in-stock and price-drop alerts. The event belongs to no profile; AJO adds a read audience with the interested customers (for example, people who saved products in that category). If your per-SKU "notify me" list lives in your store, it's simpler for the store to send one unitary event per customer.

Steps and conditions:

1. The event arrives with SKU, stock or price.
2. Read audience (AJO adds it automatically).
3. Optional: an inventory check through an external data source.
4. Message with a direct link to the product.

Channels: email and push.

Data you need: a time-series schema with a non-person primary identity and the _id and timestamp fields.

Success metric: orders of the alerted product within 48 hours.

Common mistake: long journeys. When another business event arrives, AJO ends the path of anyone still inside.

8. Win-back for lapsed customers

Goal: reactivate customers who stopped buying.

How it enters: a recurring read audience. Adobe's example runs every 30 days over profiles inactive for 90 days or more.

Steps and conditions:

1. Message with what's new, no discount.
2. Wait 7 days; exit on purchase.
3. A second message with an incentive, if your margin allows.
4. If there's still no response, drop them from marketing sends and move them to paid media through an Adobe Real-Time CDP destination, a pattern Adobe documents in its re-engagement use case.

Channels: email and paid media.

Data you need: last purchase date and last engagement date.

Success metric: share who buy again within 30 days.

Common mistake: emailing people who haven't opened anything in a year. It costs you deliverability.

9. Policy or plan renewal

Goal: get the customer to renew before expiration (insurance, telecom plans, memberships).

How it enters: a daily read audience over "expires in 45 days," with the policy number as a supplemental identifier: a customer with two policies gets one instance for each, with that policy's details in the message.

Steps and conditions:

1. Notice at 45 days with a coverage or plan summary.
2. Wait 30 days. After each wait, AJO re-reads the profile.
3. Condition: already renewed? If so, exit.
4. Custom action to the CRM so an agent calls.
5. Wait 12 days and send a final reminder.

Channels: email, SMS and a custom action to the CRM.

Data you need: the policy or plan with ID, expiration date, product and assigned agent, from your policy admin or billing system.

Success metric: renewals before expiration.

Common mistake: designing a year-long journey: no profile stays more than 91 days.

10. Loyalty: tier change and expiring points

Goal: retain your best customers and drive redemption before points expire.

How it enters: two journeys. Tier change: streaming audience qualification (Adobe's example is reacting the moment a customer reaches Gold). Expiring points: a daily read audience over "expire in 30 days."

Steps and conditions:

1. Tier: immediate congratulations with the new benefits and points balance.
2. Tier: in-app message or content card on the next visit.
3. Points: notice at 30 days with the balance and ways to redeem.
4. Points: if they haven't redeemed, push 7 days before expiration.

Channels: email, push and in-app.

Data you need: tier, balance and point expiration from your loyalty platform, with the tier streamed. We cover program design in digital loyalty programs.

Success metric: redemption before expiration and retention by tier.

Common mistake: using a batch audience for the tier change: Adobe no longer lets you publish new journeys that way. And on publishing, customers already in the tier don't enter, only those who qualify afterward.

How to measure journeys in AJO and Customer Journey Analytics

The AJO interface shows about 91 days; for more, analyze in CJA. The questions worth asking that data are in Customer Journey Analytics analysis examples, and the product itself in Adobe Customer Journey Analytics for enterprises.

To find out whether a change works:

1. Content experiments in campaigns randomly split the audience across variants. A purchase counts for a variant if it happens within 7 days, under the same identity.
2. Path experiments with Optimize test different sequences. They aren't available in business event journeys.
3. A holdout group in the journey properties measures incremental lift; Adobe lists it as limited availability.

Journeys across Mexico and North America: time zones, consent and peak seasons

Time zones. A journey's time zone can be fixed or taken from the profile. Mexico City is on UTC-6 year-round since it dropped daylight saving time in 2022, while Quintana Roo is on UTC-5, Sonora on UTC-7 and Baja California on UTC-8 (UTC-7 in summer). If you sell across Mexico, the US and Canada, store the time zone on the profile: when quiet hours use the recipient's local time, AJO doesn't enforce them for profiles without one.

Frequency caps run on UTC. The daily counter resets at 00:00 UTC: 6 p.m. in Mexico City, and 7 p.m. Eastern in winter or 8 p.m. in summer. The weekly counter resets at that same moment on Saturday. A "one email per day" cap allows one at 5:30 p.m. and another at 6:30 p.m. in Mexico City.

Consent. Manage consent per channel under the laws of each market and your privacy notice. For Mexican customers, the LFPDPPP (art. 7) generally accepts implied consent, as long as the privacy notice was made available and the person didn't object; financial or asset data requires express consent, and sensitive data express written consent (art. 8). Watch one AJO default: an empty consent field counts as consent, so load that data before the first send.

WhatsApp. AJO sends WhatsApp natively through Meta's Cloud API, in journeys and campaigns. You need Meta Business Manager, a WhatsApp Business account with a verified sender name and number, and approved templates. Meta requires explicit opt-in and applies the 24-hour conversation window; the native integration doesn't support third-party BSPs. For US audiences, note that Adobe's documentation says Meta has temporarily suspended delivery of marketing templates to US phone numbers since April 2025.

Peak seasons. Mexico's El Buen Fin runs November 13–17, 2026, followed by Black Friday on November 27 and Cyber Monday on November 30:

1. Don't publish new journeys during event week; have seasonal journeys built and tested beforehand.
2. Use a business event for flash sales and price drops, and a capped rule set for promotional messages.
3. Avoid waits with the same fixed time for everyone: Adobe warns they release every profile at once. The operational side is in how to prepare your ecommerce for El Buen Fin 2026.

Common mistakes when launching journeys

1. Launching ten journeys at once with no caps or priorities.
2. Using batch audiences in audience qualification or exit criteria. Adobe no longer publishes new journeys built that way.
3. Building conditions on experience events, which new organizations can no longer use there.
4. Leaving re-entrance at its default on one-time journeys.
5. Designing journeys longer than 91 days: the profile drops out and isn't counted in reporting.
6. Skipping a conversion-based exit, and reminding customers who already bought.
7. Profiles without a time zone when quiet hours use the recipient's.
8. Measuring opens only. If the email client blocks images, the open isn't recorded.
9. Skipping test mode, which by default shortens each wait to 10 seconds.
10. Building on dirty data. If identity doesn't stitch the store customer to the app user, the journey messages them twice. We cover it in data governance in Adobe Experience Platform.

Adobe Journey Optimizer journeys: frequently asked questions

How many journeys should you launch first?

Two or three. At WolfSellers we usually start with order confirmation, cart abandonment and welcome, because they run on events nearly every store already has. Once those are live and measured, add the ones that rely on computed attributes, such as replenishment or win-back.

Does a transactional message belong in a journey or a campaign?

If it's a single message fired by your order system, a transactional API-triggered campaign. If more steps follow (shipped, delivered, review), a unitary event journey.

Does AJO replace Marketo Engage?

Not necessarily. AJO orchestrates real-time, high-volume journeys per person; Adobe Marketo Engage remains the B2B automation tool for leads. For account-based journeys there's Adobe Journey Optimizer B2B Edition, and we explain when to use each in our AJO article.

Do you need Real-Time CDP to build these journeys?

AJO runs on the Adobe Experience Platform profile: what you can't skip is getting your events and attributes into AEP with a reliable identity. Real-Time CDP adds activation to external destinations, such as the paid media step in win-back. We explain it in Adobe Real-Time CDP.

How do you avoid overwhelming a customer who's in several journeys?

With per-channel frequency caps for marketing messages, journey caps (entry and concurrency) with priority scores, and quiet hours.

Related services

If this topic is relevant to your business, these services from WolfSellers can help you implement it:

• Adobe Experience Platform
• eCommerce Marketing
• Business Intelligence