When content includes nested elements (collection with playlists), play rules are evaluated in this order:
Collection entry level - Evaluated first
Nested playlist level - Evaluated second (only if collection entry is eligible)
Playlist item level - Evaluated last
The player checks eligibility at each level before proceeding to the next. If any level fails, the content won't play.
✅ Do
Set rules at ONE level (collection entry, OR playlist entries within zones)
Test rules with a simple setup first
Document your rule strategy for your team
Use time ranges for time-sensitive content (menus, greetings)
Use Custom Recurrence (RRules) for complex scheduling patterns
Use labels for location-specific filtering
Use date ranges for seasonal or campaign content
Set lead zones when you have playlists in zones and multiple collection entries
❌ Don’t
Set conflicting rules at multiple levels (collection entry AND playlist)
Create rules that can never both be true simultaneously
Over-complicate with too many rule combinations initially
Forget that rules are filters (content must be eligible when checked)
Mix landscape and portrait layouts in the same collection if displays have fixed orientation