Troubleshoot feedback, surveys, or messages that do not appear
Check the complete delivery path instead of repeatedly publishing the same experience.
Last updated 9 September 2026
On this page
Start with a specific example
Record the app, experience, test identity, platform, and approximate time. Choose one expected trigger action. This gives you a concrete case to inspect and makes it easier to distinguish missing activity from a rule that did not match.
Work through the checks
Connection: does the test build use the correct app configuration, and has it activated an anonymous or identified user?
Consent: has the user granted the relevant feedback, survey, or in-app consent? Tracked-event delivery also needs the appropriate analytics consent.
Lifecycle: is the experience active rather than draft, paused, or archived?
Platform: is this device or browser eligible? For Web, check the allowed origin and enabled platform.
Audience and trigger: do the actual properties and recorded event match the saved rules?
Timing: check campaign dates, delay, once-only behavior, and frequency caps.
Check the real product
A live preview in the composer is a rendering check. It does not reserve delivery, record an impression, or guarantee that a customer qualifies. Test in the connected app or website and allow the SDK and incoming activity to finish processing.
Use your assistant to investigate
If you have an AI connection, ask it to explain delivery for the specific experience and user. Treat an unknown result as missing evidence, not a pass. Share the relevant identifiers and timestamps with support or your developer when a check remains unresolved.