Journey prioritization vs frequency capping: pick the important path vs first-come send

What is the difference between journey prioritization and frequency capping?

Frequency capping limits how many messages someone gets in a window — often first-come, first-served. Journey prioritization decides which eligible journey wins when several qualify at once, by ranked importance — not who queued first.

One-liner: frequency capping = traffic light on message count; prioritization = podium for the important path. You need both; neither replaces the other.

On Iranian flash-sale days, promo SMS and new-user onboarding fire together. Without priority, the new user gets the wide discount SMS and onboarding loses. With capping alone, “whoever hit the queue first” wins — even if less important.

Path frame: Marketing journey vs campaign.

How does each work?

Frequency capping

A volume rule: max 2 promo SMS per 24h, max 5 marketing emails per 7 days. When the cap fills, later sends block or defer. Order is usually queue time, not business importance.

Journey prioritization

You assign ranks to journeys or journey families: onboarding > cart > flash sale > newsletter. When someone qualifies for several at once, the engine advances the higher rank and holds or drops the rest — even if the flash SMS was scheduled earlier.

Iran example: flash sale vs onboarding

A beauty shop runs Friday flash SMS and a 7-day welcome journey for same-week signups. Cap: max 1 SMS/day. Without priority, flash SMS at 10:00 takes the slot; noon welcome logic yields because the team treated SMS as “more queue-important.” The new user sees a wide discount before they know who the brand is.

Diagnosis

Practical fix

1. Ranks: welcome/onboarding = 1; cart = 2; winback = 3; flash = 4; newsletter = 5.
2. Promo SMS cap: 1 / 24h; email: 3 / 7 days.
3. New users first 7 days: onboarding outranks flash; flash only if a slot remains.
4. Transactional (receipt, shipping code) outside promo caps — separate label.
5. Judge with RPR and STOP, not send counts: Revenue per recipient.

SMS flow vs blast: SMS flow vs SMS campaign.

When which?

1. Fear STOP and channel cost? → Cap first.
2. Multiple live paths fighting? → Prioritize.
3. Always combine; priority without a cap is luxury spam.
4. Keep transactional out of promo caps.
5. Give lower-rank paths a timeout so people are not stuck.

Leadara mapping

Leadara implements this with events, segments, journeys, email, and SMS:

1. Journey families with a written priority contract (even if the UI is simple ranks, write the team agreement).
2. Channel frequency caps on promo actions.
3. New-user 7-day segment with a guard: flash only if onboarding done or slot free.
4. Mutual suppress between live journeys and blasts.
5. Metrics: RPR, STOP, onboarding completion — not FCFS send count.

Common mistakes

• Treating capping as prioritization
• One rank for every promo
• Choking transactional under promo caps
• Never revisiting ranks after a big campaign
• Optimizing only to “fill the cap”

Standup language

Go-live checklist

1. Rank table for live journeys written?
2. Promo caps separate from transactional?
3. New-user 7-day rule locked?
4. Timeout for deferred lower paths?
5. STOP and RPR beside sends on the dashboard?
6. Week blast suppressed against priority journeys?
7. Ranks reviewed after Yalda/Nowruz?

FAQ

What is the difference between journey prioritization and frequency capping?

Capping limits count; prioritization picks the winning eligible path.

Is one enough?

No; without priority you get FCFS; without a cap cost and STOP explode.

How do we separate transactional from promo?

Message-type label + separate caps; do not mix receipts with discounts.

What if two journeys tie?

Write a tie-break: earlier enrollment, or historically higher RPR.

Does Leadara have a separate priority engine?

You compose it with segments, entry guards, channel caps, and a team rank contract on journeys.

Right metric for priority?

Completion of the important path (onboarding/cart) + RPR − STOP; not “every slot filled.”

What is a priority timeout?

If the higher path does not become eligible in N hours, the next path may take the slot so the person is not stuck.

Bottom line and next step

Frequency capping is volume defense; prioritization is offense for the right message. This week, write ranks for five live journeys, lock the SMS cap, and put new users ahead of flash.

14-day pattern

Days 1–2: inventory journeys and blasts.
Day 3: agree ranks 1–5 with product.
Days 4–5: apply channel caps and suppress.
Days 6–10: run the next flash with the new-user rule.
Days 11–14: compare STOP, onboarding completion, and RPR to the prior period.

Weekly collision matrix

Before every flash sale, sketch a one-page grid: rows = live journeys; columns = weekdays. Each cell states priority and whether an SMS slot is free. The matrix takes ten minutes and prevents half of standup fights.

Example fill

If Friday onboarding and flash both qualify, P1 takes the slot; flash does not hit new users unless you defined a second slot.

Related reading

• Marketing journey vs campaign
• What is revenue per recipient
• SMS flow vs SMS campaign