For example, a "Reminder Message" Event might log a metric, initiate a reminder message Chat Bot, and schedule a follow up reminder for the next day. This Event can be triggered at any point in the Journey via the Run Event Action.
Session Events are created in the Connections Builder by clicking on the '+' next to Session Events, which is nested under the Global section of the Tree. Once created, Session Events can be edited in the Inspector. Clicking on the Actions tab opens the Action Inspector Tab; this is where you'll build out the Action Chain that you want to associate with your Events. Under the General tab, you can also define variables that the Session Event will expect as input, allowing you to build out general-purpose Action Chains that behave differently depending not only on user input but also when and how they are called within a Journey.
Session Events are fired by the Run Event Action, which must be built out as part of a separate Action Chain.
Information passed to a Session Event as input can be accessed within the associated Action Chain by referencing the
For example, if a variable designated
name is passed as input to a Session Event, then to access its value within the downstream Action Chain, you would need to call on:
event namespace is implied when working in Events.
Updated 9 months ago