Custom events let you trigger Journeys and Wait Until step activation based on real user behavior. This allows you to send timely, relevant messages in response to key user actions.Example use cases:
A user signs up for your app → Start an onboarding Journey
A user enters checkout but doesn’t complete it → Re-engage with a reminder or offer
A gamer reaches a new level → Send an in-app reward or upsell
A user tries to cancel their account → Start a winback Journey
A custom event is composed of:
A name to identify the event in string format
An optional payload or properties in JSON format
The user’s alias that performed the event (External ID or OneSignal ID)
Depending on your use cases, users can perform events that you detect within your app, on your backend, or in a 3rd party service. OneSignal provides ways to track these events no matter where they are generated via our SDKs, API, or integrations.
Optional parameters about the event (e.g., plan name, product ID, price).
This event will immediately add the user with external_id user_12345 to a Journey with completed_onboarding as the custom event entry-rule trigger or wait until action.
Event-triggered Journeys let you immediately message users based on real-time activity—no need to wait for segment updates. You can start a Journey the moment a user takes a key action.
Here are a few examples of how you can use Wait Until:
Onboarding: Wait until a user completes setup before showing advanced tips
Promotions: Wait until a user adds a product to cart before sending a discount
(Coming Soon): Only continue for users who clicked a prior message
You can also define an expiration window. If the user doesn’t meet the condition in time, you can continue down a fallback path, send an alternate message, or exit the Journey.