In-app messages are a great way to reach customers while they’re actively using your mobile app — but showing too many of them at once can quickly become overwhelming and hurt engagement. Maestra lets you control how often in-apps appear to each customer, so you can keep messaging helpful instead of noisy.
Requirements
In-app frequency control requires SDK version 2.14.0 or higher.
Customers on earlier SDK versions will only see one in-app per session by default, regardless of the limits you configure.
Where to find the settings
Go to Settings → Communication Optimization → In-App Frequency Control.
Available frequency limits
You can configure three types of restrictions per customer. Each limit applies independently — an in-app must satisfy all active limits before it displays.
1. Per-session limit
The maximum number of in-apps a customer can see within a single app session.
2. Daily limit
The maximum number of in-apps a customer can see within a 24-hour period.
3. Minimum interval between in-apps
The minimum amount of time that must pass between two consecutive in-app displays. The interval is measured from the moment a customer closes one in-app to the moment the next one appears.
You can set the interval in:
- Seconds
- Minutes
- Hours
- Days
How frequency limits interact with targeting
If an in-app can’t be shown because of an active frequency limit (for example, the interval hasn’t elapsed yet), it won’t be queued. Instead, the in-app will only display the next time the customer re-qualifies for it based on its targeting conditions.
Priority in-apps
For critical communications that need to reach customers regardless of frequency limits, you can mark an in-app as priority in its general settings. Priority in-apps bypass all active frequency controls and display even if the customer has already hit their session limit, daily limit, or minimum interval.
Use this sparingly — reserve it for time-sensitive or business-critical messages where overriding the customer’s experience is justified.
Applying the changes
After configuring the limits, click Save to apply them. The new settings take effect immediately for customers on supported SDK versions. 
