← Back to the simulators Architecture note · 05 Reuse the data foundation across channels Add channels by reusing customer and decision foundations, not rebuilding them. Read the note → Try another decision Does your campaign drive purchases or just opens? → Would you choose the same subject line if you measured purchases instead of opens? {"day0":"Monday","day1":"Tuesday","day2":"Wednesday","day3":"Thursday","day4":"Friday","day5":"Saturday","day6":"Sunday","chEmail":"Email","chPush":"Push","chSms":"SMS","chWeb":"Web","metaLabel":"Technical details","consequenceLabel":"What happens to Laura","stateNote":"Sent or blocked describes what happened. To judge the outcome, look at which message Laura received and which she missed.","summaryMondayBoth":"On Monday, Laura receives both the newsletter and the cart reminder.","summaryEmailJourneyTitle":"Laura receives the cart reminder but misses her Gold upgrade message.","mNews":"Weekly newsletter","mCart":"You left your trainers behind","mStock":"Your size is back","mSale1":"The sale starts","mSale2":"Sale: −30% today","mOrder":"Your order confirmation","mTier":"You are now a Gold member","mNps":"How was your purchase?","mBan1":"Banner: free delivery for Gold members","mBan2":"Banner: sale","srcAction":"Action campaign: sends the newsletter directly.","srcEvent":"Event-triggered journey: abandoning the cart starts the sequence.","srcAq":"Audience Qualification journey: starts when the profile meets an audience condition.","srcOrch":"Orchestrated campaign: coordinates the two sale steps.","srcApi":"API-triggered transactional campaign: confirms the order.","srcRead":"Read Audience journey: evaluates an audience in a scheduled run.","srcWeb":"Web campaign: proposes a banner for the home page slot.","transactional":"transactional","priority":"priority {n}","stSent":"Sent","stShown":"Shown","stNoEntry":"Does not enter the journey","stNotShown":"Not shown","stCompetes":"Competes for the slot","stDiscarded":"Discarded","stQueued":"Sent after a delay","stCapped":"Blocked by the email limit","whyJcap":"Laura has already entered {n} journeys this week.","whyJcapLow":"Laura has already entered {n} journeys this week. This one has lower priority than the ones that got in.","whyRival":"Same slot as “{name}”, with higher priority: {a} against {b}.","whyNoPrio":"Without priority scores, this model does not choose a winning banner or count either as shown.","whyNoTz":"The profile has no time zone, so this model does not apply the quiet hours rule.","whyDiscard":"It falls in quiet hours. In this case, discarding it makes Laura exit the journey.","whyQueue":"It falls in quiet hours. It goes out when they end, at 09:00.","whyDay":"She already got a marketing email that day.","whyWeek":"She already got 3 marketing emails this week.","whyTransactional":"It is transactional. The frequency capping rule is for marketing and does not count it.","calLabel":"Laura’s calendar with proposed messages, their times and outcomes","keySent":"Reaches her or is shown","keyMoved":"Sent after a delay","keyUndecided":"Web winner not calculated","keyBlocked":"Does not go out","keyGhost":"Original time of a queued message","meterEmail":"Marketing email counter","meterJourney":"Journey entry counter","meterOf":"{used}/{max}","capNone":"no limit","capDay":"1 per day","capWeek":"{n} per week","kpiReach":"{sent} of {total}","kpiReachLabel":"delivered or shown in the model","kpiBlocked":"blocked or not shown","kpiUndecided":"web proposals with no calculated winner","kpiDelayed":"Delayed sends: {delayed}. Already included in the total of {sent} delivered or shown.","kpiChannels":"email / push / SMS received","summaryEmailOff":"With no email limit, Laura receives {n} marketing emails this week.","summaryEmailDay":"With 1 email per day, {n} marketing emails arrive and the limit blocks {blocked}.","summaryEmailWeek":"With 3 emails per week, {n} marketing emails arrive and the limit blocks {blocked}.","summaryEmailJourney":"The newsletter and cart reminder arrive on Monday. The Gold upgrade is blocked by the journey entry limit, not the email limit.","summaryQuietQueue":"The stock alert moves from {from} to {to}.","summaryQuietQueueBody":"Quiet hours delay the alert from {fromDay} to {to} on {toDay}. Laura receives it in the morning and it is counted only once among delivered messages.","summaryQuietOff":"The stock alert goes out at night, at {time}.","summaryQuietOffBody":"With quiet hours off, the alert about her size being back goes out at its scheduled time. The email limit does not change this push notification.","summaryQuietNoTz":"The stock alert still goes out at {time}: the time zone is missing.","summaryQuietDiscard":"Laura misses the alert that her size is back.","summaryJourneyOff":"Laura enters all four journeys this week.","summaryJourneyOffBody":"Entering a journey does not guarantee a send: the email limit and quiet hours are checked afterwards. Check each message’s status in the calendar.","prioOnTitle":"The Gold member banner takes the web slot","prioOnBody":"In this example, its priority of 60 beats the sale banner’s 40. One is shown and the other is left out.","offTitle":"With no email limit, two arrive on Monday","offBody":"Laura gets {n} marketing emails this week, two of them on Monday.","weekTitle":"The weekly quota runs out before Friday","weekBody":"Here, the newsletter, cart reminder and sale use up the 3 permitted emails before Friday. The Gold upgrade enters its journey, but the email limit blocks the send.","dayTitle":"Monday’s newsletter blocks the cart reminder","dayBody":"The 10:00 newsletter uses Monday’s allowance. The limit of 1 email per day blocks the 19:30 cart reminder, even if you would give it greater importance.","discardTitle":"Discarding leaves Laura without the stock alert","discardBody":"The stock alert falls in quiet hours. In this scenario it is discarded and Laura exits that journey; the alert is not recovered at 09:00.","noTzTitle":"The quiet hours rule does not apply","noTzBody":"With no time zone on the profile, the model sends the push alert at 23:30. Choosing to delay or discard has no effect until the profile has a time zone.","jcap2Title":"The journey quota works in order of arrival","jcap2Body":"The cart and stock alert use both entries, even if a later rule blocks one of their sends. On Friday, the journey limit blocks both the Gold upgrade and the survey.","jcap3Title":"Priority decides the last slot","jcap3Body":"On Friday the Gold upgrade and survey compete for the last entry. Gold gets in, with priority 80 against 20. Its email still has to pass the sending limit.","prioOffTitle":"Two banners for one slot","prioOffBody":"Both banners compete for the same home page slot. Without priority, the model leaves the winner unresolved: neither is counted as shown or blocked.","orderTitle":"The confirmation sits outside the marketing limit","orderBody":"In this example it is transactional and does not use the marketing allowance. The model does not cover other causes of delivery failure."} {"email":"day1","quiet":"queue","tz":"yes","jcap":"3","prio":"on"}
Journey Optimizer · coordinating messages
Are we sending Laura too many messages?
Laura gets messages from several teams at one shop. On Monday, a newsletter and a cart reminder both arrive. Try an email limit and quiet hours to see which messages arrive, which are delayed and which are blocked in this example week.
Illustrative scenario ↑ Back to the controls
Example assumptions
Example week, messages and priorities. The model treats permitted sends as delivered, including delays within the week. It does not simulate delivery failures or a web winner without priority.
The outcome for Laura
Her week, message by message
Ten proposed messages with their outcomes and times. Open each message’s technical details to see its source. The limit counters sit below.
Journey Optimizer rules
What each rule decides
In this model, the email limit counts in sending order. The journey entry limit uses priority when journeys arrive together.
The recommendation
Decide which message matters before setting the limit
Agree limits across teams and share them through rule sets. Check which campaigns and journeys use them: reducing volume does not guarantee the most useful message gets through.
- 01
Frequency capping per channel
Set the maximum per channel and communication type in shared rule sets. In this example, transactional messages have a separate category and do not use the marketing allowance.
- 02
Journey capping with priorities
Distinguish the entry limit from the limit on active journeys. This model uses weekly entries: priority decides between simultaneous arrivals but cannot reclaim slots already used.
- 03
Quiet hours that queue
Delay messages that will still be useful at 09:00. Check the profile time zone: in this model, without it the stock alert goes out at 23:30.
- 04
Spacing between sends
Check UTC counter resets and update delays in your configuration. This model simplifies counting: it does not reproduce delivery or counter update delays.