Architect Journey Starter: On Event

The On Event Starter immediately takes users into the journey when they perform a specific event. This starter tracks user events across all platforms – website, mobile app, and offline environment. It helps you run real-time use cases since it takes users into the designated journey as soon as they complete a specified event.

The video above introduces the On Event starter.

your title goes here

An event is an action that the user can perform across the website, app, or offline environment. One such example is a product page view. Events help you track what users are doing. Moreover, you can segment and check users' actions in more detail. For instance, by using the product page view event, you can check which product or category the user visited. Some event examples are the Visit cart page, Make a purchase, Submit a form, Add an item to the cart, etc. Read more on Events & Attributes here.

This article explains the following:

When the user performs the event, they can only enter the journey once, unless they go through the same event again.

Your title goes here

The On Event starter does not consider the date-type event parameters. This means that you are not allowed to select any date-type event parameter of any event.

On Event starter

Additional segmentation

You can add more segments to your starter condition to target your audience more precisely. For example, you can take the users who perform the cart page view event and have a high Likelihood to Purchase value.

Users can enter the journey if they perform the selected event and meet the optional segment filter criteria. Additional segmentation

Your title goes here

Homepage view and mobile open events cannot be used in the On Event starter without selecting additional segmentation.

You can select predefined segments, standard segments, predictive segments, integrated segments, RFM segments, and saved segments to filter your users to take into the journey.

Tips & Tricks

Before creating your journey, you can consider the following tips and tricks.

Users may come from the Upsert User Data API or any other source without their language information. That’s why we suggest selecting the "All Languages" option in the launch settings pop-up.
You can use event parameters to narrow down the segments for a better-targeted audience.
You can use custom events in the On Event Starter.
We suggest using the On Event Starter if you have a time-sensitive use case.

Use cases

You can use the On Event starter to create the following use cases.

Welcome/Onboarding: Send a welcome email within one minute to users who have signed up to the website or mobile app.
Cart Abandonment: Trigger users who added an item to their cart.
Browse Abandonment: Trigger users who visited a specific product page.
Post-Purchase: Trigger users who completed a purchase.
Lead Generation: Trigger users who submitted a lead collection form.
User Actions on Channels: Trigger users who opened an email.

Requirements

To use the On Event starter, make sure you have completed the following requirements.

Insider Tag integration should be completed.
SDK integration should be completed for mobile app data reading.
System rules should be defined.
Events should be activated.
Events should be sent from the website, mobile app, and Upsert User Data API (if you use one of the above).