Use Case - Business event

Understand the applicable use cases for business events. Learn how to build a journey using a business event and which best practices to apply.

Hello, this is Russ. And in this video, I’m going to show you how to use a business event in Journey Optimizer. The learning objectives for this video are to understand the applicable use cases for business event, build a journey using a business event and understand the best practices. A business event in Journey Optimizer allows a brand to start a journey using a non-people related event. Common use cases include, an event is starting so notify the interested segment of individuals, a product has restocked let’s notify the users with a favorite for that product, a price drop has occurred, let’s notify users that are interested in those products. Let’s dive into the tool and show you how business events work. Here in Journey Optimizer, everything for a business event starts by configuring an event. You can go down to administration and click on “Configurations” and then click on “Events” to create a business event. You can go ahead and click “Create Event” and then this will prompt you to create a business event. Here, let’s label this of Luma, our athletic apparel brand and say, this is when there is a stock replenish event.
Here I’m going to say this is a business event underneath type, and then I’m going to select parameters for this event. First, I’ll pick a schema. This I’ll pick the product stock schema. Now let me actually open up in another tab, this schema and show you the setup for this business event.
So here I’ll go ahead and I’ll browse and show you what I had set up ahead of time. So here there’s demo system products.schema is what I’ll click on and you’ll see it has a few different things in it. I’ve got underneath my namespace, I have a product with a name, description price, and this ID called product ID. This is a field of type string that I’ve identified as my identity and primary identity using the demo system retail product ID identity namespace.
So, something that I did before creating the schema was I actually created an identity.
Before I show you the identity, an important piece to note here is that this schema is not enabled for profile. So, you’ll note that you do not have to pass this data to profile if you do not want to. The only requirement is to have an identity namespace that is non-people based. So here I’ll click on “Identities” and show you the identity that I’m using in this schema.
Here’s this product ID, and you’ll see it’s of type non people identifier. When you create an identity namespace, you give it a name, a symbol and then pick this non people identifier. It takes about 15 minutes for the schema to show up here. So, if you recently create a schema and identity, it will take 15 minutes to show up in this dropdown. Once it does, you can pick it and then you can select the fields that you’d like available on the journey canvas. So here let’s say we want the name, we want the ID, and we want the sku.
Additionally, you need to put in a condition. This condition says, whenever an event comes in as this schema, go ahead and look. And let’s say, I only want to trigger this business event when the name is equal to yoga pants.
Currently, equal to is the only operator that we offer, but you can change the sensitivity of the case. That’s what this means here with “is sensitive.” So now that we’re pretty sensitive, we’ll save this and this Luma stock replenish event can be used in a journey. Let’s hop on over to a journey canvas and show you what this can be used to do.
Here I’ll go ahead and create a journey.
After I label this journey, let’s say, Luma restock business events.
I can go ahead and let’s search for that new event that I had made, Luma. And you’ll see the icon for business event is this little briefcase and it’s sprinkled throughout this panel or palette. And there’s my replenish event that I’ll use on the canvas.
Now you’ll note that it automatically drops a read segment activity right after the business event. So here I’ll pick that read segment and I can go ahead and select any segment that I’d want to use and then I can proceed to build the journey as normal. A few best practices to remember when using a business event, make sure your non people-based identifier is in the schema for the business event and that it is marked as primary. The context data from the business event can be used downstream in the journey for a condition or for personalization. This is important when you want to narrow down the segment to the items that are passed in via your business event. With that, to recap the learning objectives here are you now know the applicable use cases for a business event. You also know how to build a journey with business events. And last, you know the best practices when dealing with business events. Thank you for your time. I’m looking forward to you using business events. - -