Prompt
why are my triggered in-app prompts not firing
Latest observation
Nov 1, 2026
OpenAI APIWeb search: off
There are a few common reasons triggered in-app prompts don’t fire:
-
Trigger conditions aren’t actually being met
- The user action/event may not be happening as expected.
- The prompt may require multiple conditions, a specific attribute, or a timing window.
-
The prompt is disabled or not published
- Check that the prompt/campaign is active.
- Make sure it’s live in the correct environment (prod vs staging).
-
The user already satisfied the frequency cap
- If it’s set to show once per user/session/day, it may be suppressed.
-
Targeting filters exclude the user
- Audience rules, locale, app version, device type, or user properties may block it.
-
Event tracking isn’t arriving
- The trigger event may not be sent from the app, or it may be delayed/misnamed.
- Confirm the event name and properties match exactly.
-
You’re not on the right screen/context
- Some prompts only fire after a screen load, route change, or specific app state.
-
A global suppression rule is active
- Do-not-disturb, quiet hours, inbox-only mode, or another prompt already showing can block it.
-
SDK initialization issues
- The in-app messaging SDK may not be initialized, or user identity may not be set when the event fires.
-
Caching / stale config
- The app may still be using old campaign data; force refresh or reinstall to test.
If you want, I can help you debug it step by step. The fastest path is to check:
- the exact trigger event name
- the audience/targeting rules
- the campaign status
- whether the event appears in logs/analytics
- whether another prompt is already displayed
If you tell me which platform you’re using (Braze, OneSignal, Firebase, Appcues, etc.), I can give you a more precise checklist.