An AJO daily entry cap does not reserve a profile for a 14-day wait

A profile matches two Read Audience journeys. The marketer wants the higher-priority journey today, exclusive enrollment during a 14-day wait, then normal eligibility later. An Experience League question describes this design tension. A one-entry-per-day cap does not itself express the entire 14-day business rule.

Model entry and occupancy separately

Adobe distinguishes entry capping, which limits entries during a period, from concurrency capping, which limits simultaneous enrollment. Both can use priority scores, but they answer different questions. A wait inside one journey means the profile may still be enrolled even after the daily entry window resets.

Inspect the arbitration window

Write down every journey sharing the rule set, each priority score, the schedule and the look-ahead setting. Adobe notes that entry-cap durations use UTC and that higher-priority upcoming Read Audience journeys can suppress lower-priority entries. Check the journey report’s exclusion reasons rather than inferring the winner from the canvas alone.

Test the intended release point

Use one controlled profile that qualifies for both audiences. Observe day-one entry, the middle of the wait, completion of the first wait and requalification during the later wait. If the business rule truly means exclusive occupancy for 14 days, configure and verify a concurrency or explicit eligibility control that matches that span; do not assume the daily cap provides it.

Adovo’s view

Priority is a tie-breaker, not a customer policy. Write the policy in calendar time and enrollment state first; only then choose the AJO controls that can prove it.