Create events

Hello, my name is Russ Lewis and I am going to show you in this video how to create an event in Adobe Journey Optimizer. The learning objectives for this video include the ability to discuss the differences between events, then list the requirements for platform schemas and datasets to be used, configure an event, specify the streaming endpoint for you to send the event, and then specify the payload for an event. Let’s dive in! Though there are several different event types in Journey Optimizer, I would say the easiest one to start with is the segment qualification. This one has a use case where let’s say Sarah Rose joined the Ultra Athlete segment. So in Journey Optimizer, you can use the event type of segment qualification and pick a segment to show when someone does this. So here, let me open up a journey and show you the canvas where these events lie and where you can pick this event type. So here, let me click on create journey. And you’ll see in the palette here, let’s name this the segment qualification example. Here in this event, we have segment qualification. I drag it to the canvas and here I would then select the appropriate segment that I need for the journey. Pretty simple and straightforward. Let’s say your next use case here is Unitary. Say Sarah Rose signed up for the email newsletter. There’s a core aspect to this where a person is involved. Sarah Rose, and then she does something. And there are two different ways to set up this kind of event. One, we call system generated. This means that the system that is observing Sarah Rose signing up for the newsletter needs to send in what we call an orchestration ID. This says this event corresponds to this ID and can be used to start a journey. This is best to use when you have a system like say a call center or a point of sale system that you can go ahead and put these identifiers on a limited number of events. And you can then use these to trigger the journeys. The second path here is called rule based. This one does not require implementation updates to say pass in this orchestration ID. But instead can be used to write rules and filter out hits from let’s say a system like Adobe Analytics. So this can be very convenient to use something you’ve already implemented that may be forwarding information over to AJO and then turn those into events that you use for the journey. So here, let me actually go over to our events. I’ll go to configurations. And in configurations, you can click on the events menu. Here when I’m managing events, you’ll see a list of my existing events. I’m going to pick one and show you what a unitary event looks like. So here I mentioned call center. Let’s say call center interaction. I look at this and I can see under event ID type, we have system generated. Then we have a schema that we’ve selected and then some fields. What’s important is picking that profile identifier or having that profile identifier in the schema that you’re using. We’ll go over that requirement here in the next section. But this is what a unitary event looks like. If I go to, let’s say, a website checkout event. Here’s an example of a unitary rule-based event. So when it’s rule-based, what we do is we write a rule to identify when this actually qualifies. So here under event ID condition, we’re saying in the event type commerce.checkouts. Then let’s use this as an event and trigger a journey with this event ID. So it’s a flexible way to be able to write conditions and trigger different events. There is a list of these different operators that you can use when you do rule-based. I’ll pick one of these here. Then I’ll go to the condition. Let’s just say I put something out there. And here we can say equal to or case insensitive. So from here, those are the different types of events. The last event type that I want to cover is our business event. This particular use case says my inventory is restocked for a specific product. This requires a non-person ID as the primary identifier. And it is always paired with a read segment step. So here I’ll pull up, say, LumaStock replenish event. You can see it’s of type business. We still pick a schema. In that schema, we have the ID and we also have a rule we want to put in here. So this rule is required to identify when we want to trigger this business event. And then you can save this and use it in a journey. So quick recap of requirements in the two different types. We’ll say unitary event requires a person-based identity marked in the schema. So if I go back over here and let’s pick on that website checkout. And there’s this demo system event schema for website. I can go to my schemas. And let’s go ahead and pick particular schema. So we’ll search for web. Let me see. Event retail v1.2, I believe it was. You’ll note that this is enabled for profile. That is not a requirement. But what is a requirement is that there is an ID in here. And so if I go and I look for my identifier, I’ll see that there’s actually an orchestration event ID in here. As well as let’s go back over here. This ECID. So we have profile identifiers, the ECID of core. So under identification, core ECID. Over here. And we’ll look for this, this, this. Here are all these different IDs that are person-based. So that’s a requirement. If I flip over to a business event, you’ll also see a similar pattern. Except for the ID in this particular schema is a non-person-based ID. I go back. And I look at that particular schema. Here I’ve got demo system, product stock schema. Expand. I can see here’s product ID. That little thumbprint indicates that this is identity. And I can use it. You also need that condition in a business event. And so here, I showed you this condition that is required. Next, what I will show you quickly is the streaming endpoint that you can specify and how to get the payload for an event. Here in all these journeys, if you use a particular event in a journey, you can go to the actual event itself and click on this little eyeball to view what the payload should look like. And so if you’re configuring your endpoint or webhook to send this in, you can copy and paste this JSON into that system. You need to replace anything that says string with a dynamic value that’s coming from your source system. So you can see here, there are several different strings like SKU, currency code, name. These are all tokens that you would use. You would replace string with the token from the system that’s sending this in. That’s how you get the payload. The streaming endpoint is something that you can either get from the sources here. So if I click on sources in the navigation, you can pick a source that we have available out of the catalog. Or you can pick a source for a streaming endpoint. And so this will give you a data inlet and you can stream data directly into AJO using that URL. So here we’ve got it loading up. And you can see there’s analytics. It’s already configured. We have different integrations with all these partners. But if you want just a HTTP API, you can go ahead and go here and you can say add data. I’m going to show you some that I’ve already created by clicking on view accounts. You can see here that call center interaction. If I click on this, you’ll see an endpoint that I can use for streaming. That’s it. I hope this was helpful to you all. And look forward to the events that you create. Thank you.