To prevent excessive messaging and improve the user experience, we have introduced journey-level frequency capping.

This feature ensures that communications—such as abandoned browse reminders—are sent only a specified number of times per day per user, reducing over-communication. This feature provides greater flexibility and control over messaging frequency, ensuring a more balanced and effective communication strategy.

What’s New?

• Journey-Specific Frequency Control: Set a limit on the number of communications sent to a user within a specific journey, preventing multiple triggers in a single day, week or month.
• Customizable Per Journey: By default, global frequency capping values are applied, but you can now override them at the journey level. For example, if the global cap allows 5 emails per day, you can set a journey-specific cap of 1 email per day. You can keep the original settings unchanged if no modifications are needed.
• Better Messaging Control: Helps reduce spam-like behavior and enhances user engagement.

How to Use:

1. Enable the frequency capping option while creating or editing journey settings.
2. The settings page will display global frequency capping values by default.
3. Customize the capping limit for this specific journey as needed.

Important Update to Not sent reasons in reports: With this update, you will start seeing following change in the ’not sent’ reasons in the reports for messages not sent due to frequency capping settings:

• "Dropped: Global frequency cap" – Message was not sent due to the global frequency limit.
• "Dropped: Journey-level frequency cap" – Message was not sent due to the journey-specific frequency limit.

Learn more: Create Journey Documentation