What is suppression logic?
Used in a sentence: Add suppression logic so the upgrade banner never shows on the payment screen or to anyone who upgraded this week.
How it works
A campaign has targeting rules that decide who is eligible, and suppression rules that remove users from that list at the moment of display.
When a trigger event fires, the SDK checks the user against each suppression rule before rendering anything. Rules usually look at three things. User state: has the user already converted, or do they have an open complaint? Context: is the user on a checkout or payment screen? Recent history: did they just see or dismiss a similar message?
If any rule matches, the message is skipped silently. The user stays in the campaign and can see it later once the rule no longer applies.
Example
An e-commerce app runs an abandoned cart nudge that fires when a user leaves the cart screen. Without suppression, it also reaches users who just completed the order in another tab, and users who left the cart to enter a UPI PIN. The team adds three rules: hide from anyone who placed an order in the last hour, never show during payment, and skip users who saw a cart reminder today.
Suppression logic vs frequency capping
| Suppression logic | Frequency capping | |
|---|---|---|
| Question it answers | Should this user see it at all? | How often can this user see it? |
| Based on | User state and context | Past impressions and time |
| Example | Hide during payment | At most once a day |
Suppression filters out the wrong moments. Capping then limits repetition for everyone who is left.
Best practices
- Suppress every campaign for users who have already completed its target action.
- Keep a shared list of sensitive screens, such as payment and KYC, where promotional messages never appear.
- Suppress related campaigns for a while after a user dismisses one, not just the same campaign.
- Review suppression rules whenever you launch a new campaign, so overlaps are caught early.
How to do this with Digia Engage
In Digia Engage, exclusion rules sit inside each campaign alongside targeting and frequency limits. A growth team can suppress users by events or segments already tracked in CleverTap, MoEngage or WebEngage, such as “order placed” or “payment started”. Rules are checked when the trigger fires, and changes go live without an app release. The Nudges product page shows the formats these rules apply to.
Frequently asked questions
- What are common suppression rules for in-app campaigns?
- Common rules hide a message from users who have already done the target action, users on sensitive screens such as checkout or payment, users who just saw a similar campaign, users with an open support ticket and very new users still in onboarding. Many teams also suppress messages that clash with a higher-priority campaign.
- Why is suppression important in fintech apps?
- Fintech users are moving money, so a badly timed prompt can interrupt a payment, cause a mistake or reduce trust. Suppression keeps promotions away from payment and KYC screens, away from users with failed transactions or pending disputes, and away from users who have already invested. It also helps avoid messages that conflict with compliance requirements.
Related terms
Read more
Part of the In-app engagement glossary.