← Back to the simulators Architecture note · 02 Separate operational state from customer state Immediate orchestration and queryable facts do not need the same representation. Read the note → Try another decision Are we sending too many messages to the same person? → How many messages reach Laura this week, and which ones are left out? {"flowLabel":"Sequence for the selected case","selectedMechanism":"Suitable mechanism in this example","summaryMechanism":"Suitable: {name}","compareMechanisms":"Compare all six mechanisms for this case","referenceMechanisms":"How each mechanism works","batchDetail":"The restriction is in Audience Qualification","modeTriggered":"Starts with an event or status change","modeScheduled":"Starts on a schedule or after daily evaluation","modeInbound":"Inbound experience during the promotion","flowCart1":"Laura adds to her cart","flowCart1Body":"An event starts her path.","flowCart2":"Wait for 2 hours","flowCart2Body":"Check whether she has already bought.","flowCart3":"Email if she has not bought","flowCart3Body":"A purchase prevents the reminder.","effectCart":"Laura enters with her event. The wait and purchase condition decide whether she receives the email.","flowOrder1":"Laura places an order","flowOrder1Body":"The ecommerce platform has that order’s details.","flowOrder2":"API request","flowOrder2Body":"The system requests a confirmation on purchase.","flowOrder3":"Order confirmation","flowOrder3Body":"One message for that specific purchase.","effectOrder":"The campaign reacts to the ecommerce request for that order. It does not wait for a scheduled audience send.","flowTierStreaming1":"Laura moves up to Gold","flowTierStreaming1Body":"Her profile qualifies for the streaming audience.","flowTierStreaming2":"Entry on qualification","flowTierStreaming2Body":"It is not instant: the example allows for Edge to Hub latency.","flowTierStreaming3":"Welcome email and push","flowTierStreaming3Body":"Laura follows her path from entry.","effectTierStreaming":"Laura enters when she qualifies for Gold, without waiting for the daily calculation. Edge to Hub latency still applies.","flowTierBatch1":"Members moving up to Gold","flowTierBatch1Body":"The change is captured in a batch audience.","flowTierBatch2":"After the daily calculation","flowTierBatch2Body":"Read Audience waits for evaluation to finish.","flowTierBatch3":"Email and push per person","flowTierBatch3Body":"Each profile follows its path after the read.","effectTierBatch":"Entry waits for the daily calculation; each profile then follows its own path. Read Audience supports this batch case.","flowNews1":"Subscribers with consent","flowNews1Body":"An audience prepared for the newsletter.","flowNews2":"Thursday at 10:00","flowNews2Body":"The schedule starts the send each week.","flowNews3":"One newsletter","flowNews3Body":"This case needs no follow-up steps.","effectNews":"The audience receives a weekly send at the scheduled time. An action campaign covers this case’s single step.","flowSales1":"Footwear customers","flowSales1Body":"Purchases are checked against open returns.","flowSales2":"Monday, Thursday and Saturday","flowSales2Body":"The calendar sets the group’s steps.","flowSales3":"Email, reminder and SMS","flowSales3Body":"Opens and purchases decide who continues.","effectSales":"The campaign queries related data and coordinates several scheduled steps. Each condition decides who receives the next message.","flowBanner1":"Gold members visiting the website","flowBanner1Body":"The experience requires a visit.","flowBanner2":"During the promotion","flowBanner2Body":"The campaign has start and end dates.","flowBanner3":"Free delivery banner","flowBanner3Body":"It appears on the home page for the selected audience.","effectBanner":"The campaign is active during the promotion, but the banner is seen on a website visit. It is not a message sent to an inbox.","onlyReactive":"Choose “Reacts to each customer” first.","onlyAudience":"Choose “Goes out to an audience” first.","onlyTier":"Only matters in the move up to Gold use case.","caseKicker":"The use case","needsCaption":"What it needs","mechCaption":"The six AJO mechanisms and how the profile enters each one","thMech":"Mechanism","thHow":"How the profile enters","famJourney":"Journeys","famCampaign":"Campaigns","mechEvent":"Event-triggered journey","mechAq":"Audience Qualification journey","mechRead":"Read Audience journey","mechAction":"Action campaign","mechApi":"API-triggered campaign","mechOrch":"Orchestrated campaign","howEvent":"Each profile enters when its event arrives, and moves at its own pace.","howAq":"Each profile enters when it qualifies for or exits a streaming audience.","howRead":"Reads an AEP audience once or on a schedule. Each profile follows its own path.","howAction":"A scheduled send, one-off or recurring, to an audience.","howApi":"An external system calls it via REST, with context in the request. Marketing or transactional.","howOrch":"A multi-step flow on the relational datastore. Everyone moves forward together.","fitTitle":"{name}: {label}","fitBest":"best option","fitPossible":"possible","fitWorse":"possible, but worse","fitLate":"possible, but late","fitNo":"not a fit","fitNoChannel":"channel not supported","fitBlocked":"cannot be published","fitBatch":"the option with batch","mythTitle":"Do journeys no longer support batch audiences?","mythBody":"Only in one place. Since September 2026, AJO will not publish a new journey with a batch audience in the Audience Qualification node: that needs streaming audiences. Journeys already live keep working. Read Audience does read batch audiences, and can wait for the daily evaluation to finish.","briefCart":"Laura adds a pair of trainers to her cart. If she has not bought within two hours, she gets an email. If she buys first, she does not.","needsCart":"Real time · Wait and condition · Per profile","briefOrder":"Laura buys and needs a confirmation with the order number and products, whether or not she accepted marketing messages.","needsOrder":"Transactional · Order data · Immediate","briefTier":"When Laura moves from Silver to Gold, she gets a welcome email for the tier and a push notification.","needsTier":"Status change · Near real time · Per profile","briefNews":"Every Thursday at 10:00, the newsletter goes to subscribers with consent.","needsNews":"Scheduled · Recurring · One step","briefSales":"For anyone who bought footwear in the last 12 months with no open returns: email on Monday, a reminder on Thursday to those who did not open it and an SMS on Saturday to those who did not buy.","needsSales":"Related tables · Several steps · Everyone at once","briefBanner":"While the promotion lasts, Gold members see a free delivery banner on the home page.","needsBanner":"Inbound channel · Web · While it lasts","cartEvent":"The add-to-cart event brings her into the journey. A 2-hour wait and a purchase condition decide whether the email goes out.","cartAq":"A streaming audience “added and did not buy” qualifies when she adds. The wait is still needed, and the audience rule is more fragile than the journey condition.","cartRead":"It reads the audience once a day at most. The email would arrive the next day.","cartAction":"A scheduled send does not react to what each customer does.","cartApi":"If the ecommerce platform already detects the abandonment, it can call the campaign. But the wait and the exit on purchase stay outside AJO.","cartOrch":"It is for batches: everyone moves forward together, not each person when they abandon.","orderEvent":"A purchase event can trigger a journey, but for a single message it is more pieces than needed.","orderAq":"It is not an audience: it is a specific order.","orderRead":"It runs in batches, not instantly.","orderAction":"It cannot be scheduled: it depends on each purchase.","orderApi":"Transactional API-triggered campaign. The ecommerce platform calls it with the order data and it needs no marketing consent. For very high peaks, high throughput mode reaches 5,000 transactions per second without using the profile.","orderOrch":"It is for scheduled batches.","newsEvent":"No event triggers a weekly send.","newsAq":"It does not depend on entering an audience.","newsRead":"A journey that reads the audience every Thursday works, but it is overkill with no later steps.","newsAction":"Recurring action campaign on the subscriber audience. One step, scheduled, with nothing else to manage.","newsApi":"No system triggers it.","newsOrch":"If the audience needs queries on purchases or products, or there are later steps. For a simple send it is more than needed.","salesEvent":"It is not triggered by an event from each customer.","salesAq":"It does not depend on entering an audience.","salesRead":"A journey can run the steps per profile, but the audience has to exist in AEP first. Related purchases and returns cannot be queried from the journey.","salesAction":"A single send: no reminders or branches.","salesApi":"No external system triggers it.","salesOrch":"It queries customers, purchases and returns in the relational datastore. Everyone moves together through email, wait, split by open and SMS. Up to 10 channel activities per campaign.","tierEvent":"If the loyalty programme sends a “tier change” event, an event-triggered journey is straightforward.","tierAq":"On the streaming audience “loyalty.tier = Gold”, the profile enters when it qualifies. Allow some margin: from the Edge to the Hub takes 15-30 minutes.","tierRead":"Reading the audience daily works, but it arrives the next day. With incremental read it only processes those who entered since the last read.","tierAction":"It does not react to each customer's change.","tierApi":"The loyalty system could call the campaign, but only for one message: the follow-up push would be left out.","tierOrch":"It is for scheduled batches.","tierAqBatch":"Since September 2026, AJO blocks publishing new journeys with a batch audience in Audience Qualification. Use a streaming audience or Read Audience.","tierReadBatch":"Read Audience with “Trigger after batch audience evaluation” starts when the daily evaluation finishes. With incremental read it only processes those who entered since the last time.","bannerEvent":"A journey can use the web channel after an event, but a permanent banner for an audience does not need one.","bannerAq":"Same again: the journey adds pieces for something with no steps.","bannerRead":"Same as the previous one.","bannerAction":"Action campaign with the web or code-based channel for the Gold members audience, with start and end dates.","bannerApi":"A banner is not called by an external system.","bannerOrch":"Orchestrated campaigns have no web or in-app channels."} {"kind":"reactive","reactiveCase":"tier","audienceCase":"news","audienceType":"streaming"}
Journey Optimizer · journeys and campaigns
Journey or campaign
Laura moves up to Gold in the shop’s club. Does her welcome follow the tier change or the daily audience calculation? Change how the audience is calculated and see which mechanism fits. Explore orders, carts and scheduled sends in the settings.
The use case
What happens in the selected case
Who enters, what starts the action and what they receive. The recommended mechanism comes from the same assessment available below.
Journeys and campaigns
Why it fits and what the alternatives are
Open the full comparison or check how profiles enter each mechanism. A journey need not start individually; a campaign need not start with a batch.
The recommendation
Four questions before opening AJO
Answer these, and the type of journey or campaign follows.
- 01
Is it triggered by something a customer or system does, now?
Event-triggered journey. If your backend triggers it and it is a single message, API-triggered campaign.
- 02
Does each customer move at their own pace, or all at once?
Read Audience can start a journey from a batch; each profile then follows its own path. An API-triggered campaign reacts to a request. Check the entry and steps of the specific mechanism.
- 03
Does the audience come from the profile or from related tables?
From the profile: AEP audience. From related purchases, products or bookings: orchestrated campaign, which queries the relational datastore.
- 04
Is it a transactional message?
Transactional API-triggered campaign, which does not need marketing consent. For very high volumes, high throughput mode, which does not use the profile.