Prompt
why are my in-app messages not showing to the right users?
Latest observation
Nov 1, 2026
OpenAI APIWeb search: off
There are a few common reasons in-app messages end up showing to the “wrong” users, and most of them come down to targeting, identity, or timing issues.
Common causes
-
User identity mismatch
- The app may be using an anonymous ID, while your message is targeted to a logged-in user ID.
- If the user hasn’t been identified correctly, the platform can’t match them to the intended audience.
-
Segment / audience rules are too broad
- A segment may include more users than you expect because of:
- OR vs AND logic
- stale attributes
- default values
- missing filters
- Example: “country = US” but the app never updates country, so many users fall into the default bucket.
- A segment may include more users than you expect because of:
-
Event-triggered messages are firing on the wrong event
- If the trigger event is similar to another event, the message may appear at the wrong time.
- Check event names, properties, and case sensitivity.
-
Attributes aren’t being synced correctly
- If user traits like plan, role, locale, or lifecycle stage aren’t sent properly, targeting rules won’t work as expected.
-
Delayed data propagation
- Some systems take time to process new user data or segment membership changes.
- A user may briefly appear in or out of a segment before the data updates.
-
Multiple message campaigns overlap
- More than one in-app message may qualify for the same user.
- Priority/order rules may cause the “wrong” one to display.
-
Testing in the wrong environment
- Production vs staging/dev users may be mixed up.
- Test users may share identifiers with real users, or the SDK may point to the wrong workspace/project.
-
Message display rules
- Frequency caps, cooldowns, or page/screen targeting may cause messages to appear in places you didn’t expect.
What to check first
- Confirm the user is identified with the correct ID.
- Verify the exact segment rules.
- Check the triggering event name and properties.
- Inspect the user profile to see what attributes the system has for them.
- Look for overlap with other active campaigns.
- Test with a single known user and a very simple rule set.
Best debugging approach
- Pick one user who should receive the message.
- Open their profile in your messaging platform.
- Confirm:
- user ID
- segment membership
- attributes
- recent events
- Temporarily simplify the campaign:
- one segment
- one trigger
- no exclusions
- Re-test and narrow down the issue.
If you want, I can help you debug this more specifically if you tell me:
- which in-app messaging platform you’re using,
- how the audience is targeted,
- whether it’s event-based or segment-based,
- and an example of a user who should/shouldn’t see it.