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 limits with Tag-based logic.

Step 1: Configure General Journey Re-entry

Set the base frequency for the journey in the Audience-based Entry block: 1. Enable Scheduled / Periodic launch. 2. Set "How much time should pass between entry and re-entry?" to your minimum desired interval (e.g., 7 days). 3. Ensure the Campaign-level frequency capping (in the top panel) is set to No limits or sufficiently high to prevent conflicts with your specific journey logic.

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 Tag: Before the message element, add a Condition or Splitter to check for a specific tag (e.g., push_cooldown). 2. Send & Set: * If the tag is absent (or indicates no cooldown): * Proceed to the Send Push element. * Immediately after sending, add a Set Tag element to set push_cooldown to true (or a specific value like 2w-push). * If the tag is present: * End the flow or proceed to an alternative path.

Step 3: Reset the Cooldown Tag

You need a mechanism to remove the push_cooldown tag after the specific duration (e.g., 14 days). The recommended method is creating a separate "Technical Journey" to handle resets:

1. Entry: Configure it to launch daily for users who have the push_cooldown tag.
2. Wait: Add a Time Delay element corresponding to the cooldown period (e.g., 14 days).
3. Action: Add a Set Tag element to remove or clear 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.