How do I configure different frequency caps for Push and In-App messages within the same recurring Customer Journey?

To set up a recurring journey where users enter frequently (e.g., every week) but receive specific messages less frequently (e.g., Push notifications only every 2 weeks), you should combine Journey entry settings with Tag-based logic.

Step 1: Configure General Journey Re-entry

Set the base frequency in the Audience-based entry element:

1. In Entry schedule, select Recurring entry, then Periodically.
2. In ENTRY EVERY, set the interval (e.g. every 1 week), then pick the days, the time and the timezone.
3. Check the journey's Campaign entry limit (canvas Settings > Campaign entry limit). Its options are fixed periods — a lifetime, a day, a week, a month, 3 months — so make sure the one you pick is not stricter than your entry interval, or users will be blocked from re-entering.

Step 2: Implement Channel-Specific Limits using Tags

Since the journey allows entry every 7 days, but you want a 14-day limit for Push notifications, use tags as "cooldown" markers.

Inside your main journey:

1. Check the tag: before the message element, add a Condition split element that checks a specific tag (e.g., push_cooldown).
2. Send & mark:
   • If the tag is absent (or indicates no cooldown): proceed to the Push element, and immediately after it add an Update user profile element that sets push_cooldown to true (or a specific value such as 2w-push).
   • If the tag is present: end the flow with Exit from journey, or route users to an alternative path.

Step 3: Reset the Cooldown Tag

You need a mechanism to clear the push_cooldown tag after the specific duration (e.g., 14 days). The recommended method is a separate "technical journey" that handles resets:

1. Entry: an Audience-based entry launching daily for users who have the push_cooldown tag.
2. Wait: a Time delay element matching the cooldown period (e.g., 14 days; a single delay can be up to 30 days).
3. Action: an Update user profile element that clears or resets the push_cooldown tag.

This setup ensures users flow through the main journey regularly but skip specific channels if their custom cooldown period hasn't expired.