How does the 'Wait for Trigger' element in Customer Journeys work, and why might my event not be triggering it for users?

The Wait for Trigger element pauses a user at that step until one of the events you configured is recorded for that user, or until the waiting period expires.

How it works

• The element branches on events (not Tags). You can configure up to three branches, each defined by its own event or set of events (up to 4 conditions per branch), plus an automatic Not triggered branch for users who match none of them.
• The event must be recorded while the user is waiting at this element. Events fired before the user reaches the step, or after the waiting period ends, do not count.
• The waiting period can be set up to 90 days.
• Enable Fixed waiting period if the user should always wait the full duration even when the event happens earlier.
• The events you want to watch for must already exist in your project before you can select them.

Why the trigger may not fire as expected

• Event timing. The event happened before the user reached the element, or after the waiting period expired — the user then leaves through the Not triggered branch.
• Waiting period too short. A 1-minute wait gives the user only 60 seconds to perform the action. For something like claiming a daily bonus, several hours or 24 hours is usually more realistic.
• Event not actually recorded. Check the user in User Explorer / Events history to confirm the event reaches Pushwoosh with the expected name and attributes.
• Multiple active sessions. If the journey allows multiple active sessions per user, configure the session-matching section so each incoming event is matched to the correct session.

See Wait for Trigger in the documentation.