What is nudge fatigue?
Used in a sentence: Dismiss rates on every campaign went up after the festive push, so I think we're looking at nudge fatigue, not bad copy.
How it works
Fatigue builds when several teams run campaigns independently. Marketing has a sale banner, product has a feature tooltip, and growth has a referral popup, each reasonable alone. The user sees all of them in one session.
Users learn quickly that prompts interrupt them, and they start closing them without reading. The effect spreads beyond the noisy campaign: once a user expects prompts to be irrelevant, they dismiss the relevant ones too. Signals show up in the data as falling engagement across all in-app formats at once, not just one campaign. Left alone, it can lead to lower retention and more uninstalls.
Example
An e-commerce app runs a festive sale with a homepage popup, a cart reminder, a wishlist nudge and a new feature tooltip, all live together. Over the week, dismiss rates climb on every format, including the cart reminder that usually converts well. The team adds a global cap of one prompt per session, ranks campaigns by priority, and suppresses promotional prompts on the checkout screen.
Nudge fatigue vs banner blindness
| Nudge fatigue | Banner blindness | |
|---|---|---|
| What happens | Users actively dismiss prompts | Users stop noticing static banners |
| Cause | Too many interruptions | Repetitive placement and design |
| Fix | Caps, priority and suppression | Fresh design, placement and context |
Both reduce attention, but fatigue is about volume and interruption, while blindness is about predictability.
Best practices
- Set a global frequency cap across all campaigns, not only per campaign.
- Rank campaigns by priority so only the most relevant one shows when several qualify.
- Suppress prompts during payment, onboarding steps and other focused tasks.
- Keep a holdout group to check whether nudges help retention overall.
How to do this with Digia Engage
Digia applies frequency limits and suppression rules in the same place teams build campaigns. A growth team can set frequency caps on each campaign, use segments to exclude users who already acted, and keep prompts off screens where they don’t belong. Because every nudge runs through one layer, overlapping campaigns from different teams are easier to see and control, and changes go live without an app release. See the formats on the Nudges product page.
Frequently asked questions
- How do you know if users have nudge fatigue?
- Look for dismiss rates rising across many campaigns at once, faster time to dismiss, falling click rates on formats that used to work, and more users closing the app right after a prompt. If a holdout group with fewer nudges retains as well as or better than the rest, you are over-nudging.
- How many nudges per session is too many?
- There is no universal number. It depends on the app, the session length and how useful each prompt is. Set a global cap per session and per day across all campaigns, start low, and raise it only if dismiss rates and retention stay healthy for the users who see more.
Related terms
Read more
Part of the In-app engagement glossary.