Define who is allowed to enter a Journey, and when they enter it.
createdAt
date within the last 30 minutes. This journey might encourage users to finishing setting up their prorfile, and inform them about new features.
TRACK
event with the specified name. Event Entry Nodes are useful for what might traditionally considered transactional messaging. For example, journeys with Event Entry Nodes are appropriate for sending order confirmation, password reset, or order cancellation emails.
With every matching event, a new instance of the journey is created for the user. This is in contrast to Segment Entry Nodes, where only one instance of the journey can exist at any given time for each user.
ORDER_CANCELLED
events. This journey might include a message node that sends an email to the user, informing them that their order has been cancelled.
A user can have multiple instances of the journey running at the same time, if they trigger multiple ORDER_CANCELLED
events concurrently.
appointmentId
as the key.orderId
as the key.appointmentId
in the case of appointment reminders.
For example, the following appointment confirmation event could be used to trigger a journey:
APPOINTMENT_CANCELLED
event with the same appointmentId
, and want to route both events to the same journey instance.
orderId
or appointmentId
.