Use Case Playbooks, self-serve templates to deploy use cases in a few clicks

Hey, welcome. My name is Daniel Wright, Senior technical marketing engineer at Adobe. I create a lot of videos and tutorials for platform which are available on experience. Again, recently I had the opportunity to create some content about our new feature, which we’ll be talking about today. Use case playbooks available for real time customer data, platform and Journey Optimizer. And I’m excited to welcome our guests for today. So our first guests Senior Evangelist for experience Cloud and platform Mr. Rudy Shumpert. Who has been. Up and then the other corner senior product manager and mastermind behind use case playbooks. Rohit Buzzer, a row here. All right. So we’d like to start our experience league live episode is getting to know our guests a little bit. Rudy, we’ve been teasing the audience about your rational fear of alligator, as you want to tell us a little bit more about that. Sure. So, you know, long time ago when I was much younger and much more foolish, we went on a canoe trip to the Okefenokee Swamp and the alligators on the bank went on into the water and under the canoe and the chute on its back rubbed the back of the canoe. And it was a and I’ve never been back to that swamp again. Never will. Yeah, yeah, yeah. I always read about people playing Frisbee golf in Florida and their Frisbee goes in, the lake is gone. And they got to recover that that 15 million pieces of plastic and terrible. So good. Yeah, yeah row hit. You’d love to cook and your specialty is toast and omelets. Now I get that omelets require some skill, but toast. Really? Is there. Is there more to that than putting a piece of bread in the toaster? What are your secrets? Well, the secret is, you know, I assumed keeping the wife happy was some good toast and omelet. That’s all. And it was our honeymoon. And we had traveled somewhere, and I burned the toast. And unfortunately, I couldn’t even, you know, there was no more bread left in the freezer. So I had to serve my wife with the burnt toast and omelet. And that’s when my wife had been teasing me. But since the last eight years of our marriage, that this is your specialty, the toast and the omelet. So that’s the story behind toast. Okay. Did you did you manage to. To save the toast in some way? Did you scrape the burnt part or. I tried. I guess I had done the job so bad that even after scrapping and everything, I couldn’t save the day. But you’re still married, So it’s the attempt that counts. All right, All right. So let’s get down to business here. So, Rudy, why don’t we start with you. Can you tell us a little bit about use case playbooks? Why did we build it in the first place? What was the was a problem customers were having that we’re trying to solve? Absolutely. So, yeah, I’m really excited to talk about these use case playbooks today and excited to see Rohit show them in greater detail afterwards. So the two major challenges that we’re trying to address here is kind of blank page syndrome. So really trying to help customers be able to fully leverage and discover the power out of Adobe Experience platform and really get value out of it faster. So, you know, sometimes, you know, we have a brand new customer, they get access to all of the toy toys and tools and kind of platform, and they’re like a little overwhelmed of what to do first and how to go about it. So this helps them get past that initial hurdle. The other part is just to help grow, you know, the product playbooks in both quantity and quality. So what we’re talking about here is, you know, trying to help customers get up to speed faster and to be able to really leverage the value of making more of these products work together so greater adoption and greater engagement across the tools. So let’s talk about what they are so right now, use case playbooks. You know, when you boil them down, there are curated set of use case templates and they’re right now they’re sorted out by industry and by application. So you can go in and say, Hey, you know, I want to, you know, put together a playbook to help me with my abandoned browsing in merchandise for a retail customer in order guide you through the process of how to creating all of that for you. And what it does is it takes these marketing goals of I want to fix my have a better abandoned cart or abandon browsing experience and help it get it into production and working for you much faster and it’s done by these playbooks for each specific specific use case. And so like this one here, abandoned browsing and merchandise customers can look through them, look through the catalog, select the one, take a look at the map, see if they’ve got the products that are required. This is an important call out because each use case will show you which products are required. So as Rohit is going through the demo here in a few minutes, what you really do pay attention to this part because this is key. So that way you can see exactly what you already have access to and what you can put into place today. The next part about that is that I really want customers to pay attention to. The demo is the sandboxes, so we do not automatically put the use case playbooks in your production or current development sandboxes. You’re going to have to create a new development sandbox and put the suffix of UCP use case playbook in the title for them to show up. The reason is we want you to be able to play with it, get some comfortable with it, you know, build up some competencies in working with the playbooks and then make it super easy for you to move these into your production instances. Yeah. And that’s that’s one of the things I like about the way I wrote it and team built this feature because like I see the playbooks as kind of like, you know, you open up word and you know, maybe you’re writing your resume for the first time and they have a template for a resume. You wouldn’t use the template. It resume. You’ve got to customize it. So it represents you in in you know, what you’ve done in your career. And similarly, these playbooks, you’re you’re going to want to customize them to really fit the needs of your business. So by keeping them in that development sandbox and then, you know, going through those steps to, to move it to your other environments, I think helps enforced good good use of them. Right in it. And it lets customers use it in a safe environment. I mean, in a safe sandbox, which is what it’s designed for, is to be able to really test the system out without worrying about messing up anything in production. So gives off the greatest flexibility. And then after they’ve deployed it in that development sandbox and they’re comfortable with it, you know, this building materials page or this detailed page will list out the journeys, the schemas, the segments, all the different messages that you may have built in. It allows you to publish it in a different sandbox. So even though we’re, you know, you have to build things in that development sandbox, the Rocket and team have built in that capability so that you can easily publish all these objects into more of a production sandbox. And so as he goes through the demo here in just a minute, I really want customers to think about as they’re watching this. These are the things I want them to have in their mind, or they’re thinking this of like, Well, how does this apply to me? How can I use it? Is that we’re really trying to, you know, help you get the maximum value out of your investment by making implementation of these some of these use cases much faster. We want to be able to demonstrate the value of what you’ve already invested in to your stakeholders much faster. Also, being able to take these technical use cases or these marketing use cases and have the technical part done in a large part for you really helps build more collaboration between I.T and marketing. And again, you know, this, this has really helped customer expand the adoption and you know, the more you use the different features and functionality within platform and the various products, you know, the more benefit you’re going to get from it. And so that’s what we want customers to maximize their current investment with Adobe and to get the most value out of it. So I’m super excited that Rohit is not going to take it away and show us all these cool features, but keep all these talking points in mind that you’re looking at it because he’s going to show you some really cool stuff here. Awesome. Let’s see where. All righty. Good morning. Good evening and afternoon, everyone, from wherever you are joining in the world. So this is a net new product from it’ll be use case playbooks. So what I’m going to do is going to do a quick demo for all of you and then we’ll keep on talking more about it. Right. So this is the homescreen of use case playbooks on the left hand side, you can see various filters like product required Edu, CTP Industries. So we are coming up with three industries right now being sports and live entertainment, travel and hospitality and various marketing channels which you can filter. So Rohit, just ask. So you have those three industries. What like what if I’m a customer who works in the insurance industry? Does that mean I can start using playbooks yet? What’s my way? Or is there some way that I could use them and get value out of them? Absolutely. Great question, actually. So there are two parts to the answer. So if you look at the nature of use cases that we have today, some are very industry specific and some are very generic in nature. For example, abandoned car, abandoned roads where we have given them an industry flavor. But we know when we were doing the beta program there was a large insurer which is part of the beta program, and they had taken one of this common use cases. If I remember correctly, it was abandoned garde, and then they customized the journey, the schema and the segment according to their requirements, and they made able to, you know, play around with it, take it to their development environment and to production subsequently. So what I learned from this is that while it might not suit a specific industry completely, but then even though a particular playbook is not available for the corresponding industry, definitely still gives a jumpstart to customers because industries. Mm hmm. And do you plan to add additional industries to the playbooks? Oh, yes, absolutely. So I think we are already working towards healthcare, commerce, and I think retail more more retail use cases. There’s other industries that as well can provide the signal for us, but we continue to have more industries added and all of it subsequently to this playbooks. What we also intend to do subsequently is, you know, introduce some kind of authoring capabilities or SDK whereby we want to empower our customers, partners to be able to bring their own playbook. Right. And their own playbook and, you know, take it to various spaces within their company organizations. So that’s something that we want to do subsequently. Oh, that’s great. And you know what? Some somebody just asked that in the chat. So it’s great to have that one answered. In just a reminder, you know, anyone who’s who’s listening live, feel free to ask questions and and we’ll try to answer them for you here. So cool. Yeah. What’s what’s next? Okay. All righty. So, yeah, so I talked about the filter functionality. You can search for specific label sort playbooks by name. You have a grid view and the list view, all of this cool functionalities out here. And then, you know, you have two types of playbooks. So for activation is typically all the artists ATP playbooks. We haven’t named them for activation. So let me click on one of the playbook based on clicking that, it will take us to the Playbook display page. So on the Playbook display page, you can learn more about the playbook. Basically what this playbook does, what more creative goal it supports, which industry, which is the targeted persona and what products are required to make this playbook work. Now, the good part here is even if someone does not have the corresponding product license, for example, I need your license which is needed to make this playbook work. They would still be able to browse through all the content in a Playbook display piece. They would not be able to create an instance to. So when I talk about create instance, basically it’s a CTA which will help you instantiate this particular playbook. Think of it as a particular version of the playbook that you own, right? So once you click on Create instance, you get a set of AP objects that get generated like segment schemas, journeys of all of them. And then if you want to make edits to the journey according to your company’s requirements, you can edit it and save the instance with a name that you are able to identify. So that again and again, whenever you need to refer it back, you can go back and open the instance directly. Here we have something called as a mind map, and mind map is basically, you know, it’s something which helps the to understand the overall journey that a customer will undertake. And it also helps to let the marketing and the data engineer or the martech person, both of them, come on to the common page in terms of what they expect out of the use case to do this. To give you a small example, while I would use case supports out of the box that if Sara abandons browsing for her works, then she qualifies to be part of the segment or audience, which will then be receiving some kind of communication. So this thing that here you have left browsing a particular page for a particular item and so on and so forth. But depending on your company philosophy is the nature of business, you might want to change that to like 24 hours, 48 hours, 2 hours, whatever is needed. Right? So these are the finances that you can finalize here. Yeah. I love I love this mind map feature because I think too often a lot of confusion when folks are trying to implement journeys and the segments is they’re not on the same page of exactly what they mean for the particular use case. So the way that this breaks it out with Sarah, browse the website. Then she abandoned the browsing and then they get a reminder message. Makes it nice and clear for folks whether they’re more on the marketing side or they’re more on the technical side. I, I love the visual representation. So the more visual things like that and the more they can make it more clear of what is being addressed, the better. Yeah, is probably easy to take a screenshot of that too and put it in a PowerPoint if you got to present it to other people at your company. Just a quick visualization with what it’s going to do. I you know, when I first saw that, I was like, okay, somebody browses the website and then you’re able to send them an email. I’m guessing that there is some sort of authentication required in order to be able to, you know, what their email address is and so that will be something that is some maybe it’s the identity graph and platform so we can link their experience, cloud ID and the website to their email address so that something like that can be done right? Absolutely. Absolutely. We have intentionally kept the technical details out of the loop here just to make different kinds of personas like marketing, also comfortable when they are looking at this use cases could be probably one of the first instances. The web they can actually, you know, look at this use cases, discover different playbooks, different kind of use cases that they want to do for their organization and even, you know, play around with those best out, best those use cases. All of those is what they can do subsequently. Cool you moving on from here. So you have some more details around the playbook itself. So who’s the target audience? What marketing channels, for example, here we the Journey addresses all the three marketing channels, email, decimals and push. And then finally you’ll see what are the technical assets that get generated for this particular playbook. So, for example, here have one journey, one audience, two schemas, customer profile and even schema entry messages, right? So I’ve already created pre created some instances. So let me click on one of those just to save some time. Right. So make I have already said that these are the various technical objects that get created for this particular playbook. You have the journey, you have the schemas, the custom provide schema that even schema and audiences state. So you can on clicking on each of this, it takes you with the journey, it takes you to the audience and subsequently when you click on the schemas, it basically perspective schema pages. I wondering open the journey, right? So if I want to let’s say I did something in the journey, of course it would not be 100% of what I want to do so I can make changes to the journey, you know, and then save some specifics around it. And once I do that, I can actually come back and save this instance with a name, with which I identify. Right? I can write some notes. As with this aspect of the journey or whatever I want to save as Nordstrom and save this. You know. RO There’s a question that came in related to this maybe, and maybe there are two ways of answering it. It looks like Karen is someone who maybe uses a shared partner sandbox. So we when you have an account like is it possible to we know you need to create a new sandbox with UCP in the name. Is it possible to create multiple playbooks sandboxes in a single account or can you only create one playbooks sandbox per account? That’s a great question and I will fight that for a couple of minutes. But I want to flash an important point that I think I have we have not talked much about earlier. I think Rory briefly touched upon it, but I think I should talk more about it. So one important aspect is unlike all other B products, use case playbooks is not going to be available out of the box in your normal development and your normal production sandboxes. What we expect and it’s something by choice because we are generating schemas and all of it, we don’t want the schemas and all that we generate to mess around with your union schema in the development and both of you being in schema in your production sandbox of our customers. So what our customers need to do to be able to use use case playbooks is, you know, take one of the empty sandboxes that they have and you know, they basically need to do three things and it’s up here in the documentation that we have. They need to name the sandbox with the suffix das you should be. And then they need to do some settings, some permissions and all that they need to provide. And then subsequently they need to set up the ADR services If they are looking at only RTC repeat licenses that they have, they probably don’t need to set up video services. But if they are also looking at EDU playbooks and they have video licenses, it is advised that, you know, so sick of these use surfaces. So the three things they need to do name the sandbox with suffix bash. You simply look at the documentation and do all the settings and then, you know, ultimately set up the surfaces, video surfaces. So once you are able to do that, three things you’re use Case Playbook is now available. It would be available on your left panel like this. On clicking on this, you arrive at the Playbook homepage. Now, one important aspect is while all these objects are getting generated in your inspirational sandbox, which is which you just created for your organization, and you can of course, just answer that question. You can, of course, always have more than one sandbox and you want to utilize them for creating or configuring use case playbooks. Of course you can do that. There is no that is more restriction on the number of sandboxes on which you can. Okay. And if if say, Rudy and I were sharing a sandbox, the other way to say share responsibly is to do what you showed a few minutes ago. If Rudy creates an instance of abandoned browser, he should rename it and and I should name lines indicate, Hey, this is mine. And I think that when you create an instance, it will create a new instance of, in this case, the journey and the audience. Yes, so maybe we should rename those. But the schemas again, say Rudy and I created this exact same playbook. This schemas that are two instances is would use would be the same schema, right? It’s not creating the same schemas over and over again. For instance. Right? That’s correct. So journeys and audiences and destinations in case of artistic playbooks, they are created over again and again. But schemas are shared across between playbooks. So let’s say you make some changes to the schemas, Daniyal, and add some fields to it. So when Rudy tries to, you know, recreate some instances or create some new instances, then those new instances will also leverage this object. You have added some fields to, okay, good already. So one important aspect now is that we need to ultimately our aim is to, you know, take all these objects to our development sandbox because we are in the inspirational sandbox and, you know, let’s try doing that. So there is a CTA here where we can create a package directly which only contains these objects that we just generated and maybe edited. For our instance. So the package is successfully created. Let’s go to sandbox. And we should mention it because packages are a relatively new feature. It came out last fall for platform and the idea behind the packages is to facilitate moving things from one of your sandboxes to another sandbox, which is ideal for use case playbooks because that’s the whole point you start and the inspirational playbooks sandbox, and then you can use this feature to move it to another development and sandbox. And for more information on that, on Experience league, they’re going to look up sandbox tooling, correct? Absolutely. Related products that you need to look up. Okay. So you’ve created this package now with that instance of your placement. Right? So one thing I want to talk about is you need to look at the status here in case it successfully will see that it is published, in case it’s failed. Then you will see that it is the status show is canceled subsequently. Right. So you need to ensure that the status is published. That means the package is now available to be imported in your development sandbox. So let me try and import this package into the development sandbox. So yes. And this the package name. So what happens is when we’re importing to a different sandbox, you calculate all the dependencies, right? So the first thing that you need to do without which you can proceed is you would need to map the two schemas from use case playbooks. Right? It provides schema and the event schema, both of them to your development sandbox schema of choice. Whatever schema you want is is yeah word. And was two for the for the playbooks sandbox in order to create you know everything you know uniformly as templates you sort of have some standard schemas that are part of that sandbox. But you had mentioned to me in one of our calls how during the beta for this feature, the customers in the beta there are schemas were, were very different. And so this is a really important step in the process to to make, to customize the playbook for you. It’s not just about, you know, modifying the audience and the journey, but this, this process here of, of mapping things to the way you build your own schemas. Right? Absolutely. So what we recognized when we were doing the beta for this product is that, you know, data engineers gave us a feedback that, you know, this is all great, that you are generating all these objects out of the box and giving us this template. But as data engineers, we have to rebuild all of it in our development. And both because, you know, our schema is going to be very different from the schema, which is primarily the Adobe Standard Field and Brooksby schema that you have used to develop this playbooks, right? So the time to value will not actually, you know, we’ve not got the actual time to value because we have to recreate all the objects. So that’s to be third letters. So you know, bring this new feature for data awareness where the first step we do is map the schemas to the development sandbox, schemas of the customer and subsequently, you know, the journeys, the segments, all of them get auto converted to the new schema that the customer has just mapped. So that’s how they save a lot of time. And we get actual, you know, time to value kind of benefit. Now like here in the mapping where it doesn’t show you the the full list but just the fields that are relevant for the use case that you’re putting together. I think it’s a lot less confusing that way, that you’re not overwhelmed with irrelevant fields, because I know most of the schemas I’ve seen have way more than three frames, but I really like what have done here with limiting it to just what is critical for this use case to work. Absolutely. That’s a that’s a great point. You know, so we thought that to make it computationally less intensive because if you go for typical schemas, it will have a lot more fields than three or four or five translate. So we try to make it computationally less intensive. It’s practical that we just mapped the fields that are used in objects like the SEC, manage the journeys and all of them and not map all the fields. That is, we save on a lot of computational resources as well as the time to do the mapping. The good part is let’s say you make changes to the schema in the inspirational sandbox where you have use case playbooks and you want to, you know, import your own instance of game for the same playbook. Let’s say you have already imported the playbook and you want to get your another instance right. So the mapping will be done once again. So it’s not like once done and the mapping will not be done for that playbook again ever. Right? So every time you perform an import of a package containing the app objects for that particular playbook, the mapping exercise would be done all over again. MM So it seems like there’s a couple of places where you can customize these templates. You can customize them in the playbooks sandbox, and then you can customize them further once you import them into one of your real development sandboxes. So I guess probably every customer will have a different preference for how they they do that, right? Right. Absolutely. And one more thing that I wanted to point out is we also encountered some scenarios where, you know, our use cases from the playbooks. They had a certain type of fields or certain fields which was not present in customer’s chosen schema, the union schema. So what we saw this to the customer, they would typically get a prompt that, you know, you have fields missing in the chosen schema and you need to go back to your schema in the schema page. Basically you need to click on the schemas tab here. You need to go back and add respective fields to the schema to which you are trying to do the mapping and then come back and continue with the process. This flow will actually pause. Okay, You will not be able to go ahead. There were some suggestions when we are building the product on and we read them to mind whether should we give an option to be able to, you know, for customers to be able to add fields directly on the mapping page itself. But then we subsequently decided against it because what we discovered is that not all, not everyone in the customers who have permissions to add fields the schema. So we want them to go through the process of, you know, getting the right approvals from their respective responsible people and, you know, be able to add the fields to the schemas and come back in, let’s say. For right ahead. There’s a question from Jamie about the question is, will personalization implementations and templates and journeys be updated as part of this mapping? All I need to go into the templates after import and update those references. And I’m guessing Jamie’s asking about like if you wanted to show like the name of the product that the person abandoned Browse and the personalization within the email message that is sent to them. Right. Do all of those references get updated in the mapping process? I guess no. So in that specific email template, we strongly recommend customers that they should go and, you know, change the content of their email according to the requirements and intentional. Because what we have observed is we can give one template, but customers typically have their own standard template, own logo and their own lingo on which they want to use to write an email to us. Right? So that’s intentional that we want customers to visit the template and illustrated that message template and all of that and be able to edit it. But the vintage, yeah. So like in maybe you could just open up the journey that that instance created it for, for done and this screen and just take a look at some of them. So it said this will create like an email template for the sake of the of you know showing the use case. But what you’re saying is a customer is not going to actually use this email, but we need to provide something to give them a sense of the message. So they said, Gotcha. Well, forget this. This is a template. And, you know, it’s it provides a lot of the building blocks. But absolutely, I think that’s a great call out there. And I’m glad that Jamie asked that question so that it surfaced up during this is that, you know, it does need to be modified. And that’s another reason why this isn’t put straight into production, that it’s put into that inspirational sandbox. So it gives you time to work out all of these wrinkles and to fine tune it and make it perfectly suited towards your business and your company and your messages the way that you want them to sound. Because, like it said, everybody is going to have a different style and philosophy and approach to the messages. Well, coincidentally, really, I have a side hustle doing mail order indoor plant e-commerce. So I get to use the assemblies out of the box. So that’s great for me. There you go. There already. We have a sentence here. So the package import has been successful. In case I just want to also talk about how do you, you know, identify what are the causes of failure in case, you know, you see this console state is the ideal way to do is click on this view job details and then you know, on clicking this, it takes you to a button and you can see more detail set on what is the root cause of the problem that you encountered. So typically, if you encounter some issue and you are trying to raise a bug or an issue, then the right way to do that is click on view Job details. Identify what is the root cause like go to the JSON file and look at what is the root cause, What is in land masses that you see. Take a screenshot of that and send that across to us. That will help us as a team to actually identify what is the potential problem that you might be facing. I have a question. You went through the Create package screen pretty quickly while we were talking about other stuff. I want to know if before you create that package and bundled up, let’s say you create the instance, but you decide that you want a couple of extra journeys in there, you want to change the logic around. So if you created some objects that are not part of the objects that are created with the instance. So let’s say Daniels, he’s selling those plans, but he wants for more different types of journeys in there. Can you add those to the package when you’re building that before you put a production, or does it have to be just the ones created from the instance? Yeah. So that all parts of there are two parts of the question and let me answer them. The first is can you edit the journey in the use case playbook instance? The answer is of course, yes, you can edit the journey to whatever extent you want to. You can save the journey, right? And then when you create the package, you get the editor journey that you have just created already to add whatever. Right now the second part of the question is do you have the possibility to add more journeys to this package? Basically? So basically, on the bill of material page, let me just go back to the answer to that is as of now, no, we don’t provide that option for you to be able to add more feel on the more objects, technical objects to this particular bit of material instance for which you are creating a package. But what you can definitely do is you can create more journeys, save those journeys, write with a different name, and you can of course go to sandboxes. And there is another way. Now we have released the Sandbox Tooling project. I don’t know if you guys are aware or not, so using that sandbox tooling, you don’t get the city state out of the box, but definitely you get an option to create a package and then import the objects. So using sandbox tooling, you can definitely, you know, create any number of package and perform import of any number of packages to your target sandbox. That’s a little bit. I’m guessing one of the most common issues like moving things from the Playbook sandbox to another development sandbox is user permissions, right? Because I noticed, like in order to create an instance, I needed to have user permissions to create schemas, create journeys, create the messages and audiences. And I’m guessing if you then try to import to a different sandbox, you would need to have those same permissions in the sandbox you want to move to. Typically. Yes. Typically, yes. That’s how it needs to be configured. But in the long term product roadmap, we are trying to, you know, make it much more easier right now, like our users need to do specific settings and that kind of needs to reflect in their target sandbox as well. In most cases. But I mean, six months down the line, this entire process will become much more easier and it will not be gated. Yeah, I was just wondering about like best practices for setting the permissions. And maybe maybe the best way is if you have you know, for people who are doing the migrations and who, you know, have lots of privileges in the domain development sandbox, maybe the role that gives them those permissions, you just add the use case playbooks, sandbox to that role so they can do the same things. And playbooks that they need to do in the main dev sandbox. And if you want to give other people limited rights to use sandbox is to say just view things and you could create a separate role with those limited permissions. So lots of people can go to the playbooks and play around and then you have people who actually export them and import them to another sandbox or, you know, they just have one role that has the, you know, all of the permissions laid out to make it easier to you to manage that. The accident and all of those steps, I believe, are detailed on experience, league and the documentation as far as creating the sandbox, going through all those steps just like you did. So we’ll make sure that the links to those are kind of in the in the show notes or the post that usually goes up after that. So the folks that are listening along or watching this later, you know, there will be an easy to find resource for that. But yeah, I know it may seem like there’s a lot of steps, but all of those are detailed really great in the documentation. So there is. Right there is a question is about the licenses. And then I have a follow up question to that. So the question was, is access to the playbooks dependent on the project license? Meaning can I only access this if I have an AP product license? The answer is no. You would be able to access playbooks even if you don’t have licenses. So by that I mean you can click, you can see this playbooks, you can see the playbook, you can identify what other playbooks are present. Once you click on a specific playbook display PS2, you will see that if you don’t have the license, then this create instance CPAs grayed out and you will not be able to create instances, right? You will not see any specific instances for this playbook. So you will, you know. If you would need to have Journey Optimizer or Real-Time CDP write one of those two. Yes you of need. If you just had Adobe Analytics for example, you wouldn’t be able to access playbooks. You need to have Journey Optimizer time. CDP Yeah, I mean the answer to that is you will still be able to set up playbooks. You will still be able to, you know, see this display page and you can click on individual playbook pens, but that’s about it. You will not be able to create any instances or nothing more than this. You will just be able to see the speed and that’s about it. Okay, So you need to have one of those two products. But if you only had real time CVP, you’d still be able to see the journey, optimize their playbooks and poke around. Okay. Yes. And so my follow up question, looking at the gallery page here, I see there are two playbooks that look kind of similar at the top that abandoned browsing merchandise and abandoned browsing merchandise for activation. But and then the next set I see has a similar abandoned Browse product, abandoned Browse product for activation. What’s what’s the difference between the two of those with clear names? Yeah. So merchandise is a keyword that we have used for sports and live entertainment industry. And then product is something which is for retail industry and then you know, for activation is a addictive or verb that we have used for all active sleep playbooks. So across the board, if you see that a playbook is ending with the suffix for activation, that means this is more of an artistic kind of playbook. So if you wanted to do that, you know, more multichannel, abandoned browse, you would say to they send the email messages and also do display advertising. You would want to create instances of both versions of that playbook. Mm hmm. Right. Cool. Absolutely. And oh, there is one thing I want to mention with the with a with the Journey Optimizer playbooks, there is that that step that you mentioned to create that the channel configurations and Journey Optimizer in this sandbox. But for customers you know maybe you don’t do push messaging yet maybe you only do SMS and email you know only configure the channels that you use. If you only configured two out of the three, when you right click create instance button, you’ll get a little message saying, you know, indicating that you don’t have all three channels configured. That’s okay. You can dismiss that and it will still create all of the objects in the playbook. But if you if you, you know, open the journey and looked at it, you’d see that the the push message had been created, but it’s not fully wired up because there wasn’t that channel configuration for it to linked to. So you would just want to, you know, remove that branch of the journey, you know, that had the push stuff and you could still, you know, just get rid of that from the journey and use it, you know, for your push and email messages. So don’t be scared off by that, that you know, that warning. Yeah. I just wanted to add maybe one last point and it is you know, so with use case playbooks, when you try to create a package grade or rather import imported use case Playbook package, you’d only be able to import it to the development sandbox. Of course you would not be able to directly import it to your production sandbox, and that’s intentional. The entire lifecycle, the way we envisage most of the customers are taking a Playbook instance to grow. It would be you take objects from a playbook instance that you have modified to your requirements, then you map the schemas and now you have your journey segments, all of them available in your development sandbox. You test them out with your own data, in your environment, in your development environment, and like you do once you’re satisfied with the testing, you move them to production, maybe you move them to your broad sandbox. So that’s kind of the lifecycle We also want customers to take with all the objects and all the playbook instances which are present for you playbooks as well. And that’s why, you know, it’s kind of that you need to you cannot like jump directly to the broad sandbox, but you need to go from the use of inspirational sandbox to the development sandbox and from development to the broad sandboxes. Okay. So you anticipate customers doing that end to end testing of, you know, with their sample files actually generating the emails to those after you’ve migrated the the playbook to your own development sandbox. Okay, cool. Jim. Jamie is really excited about being able to create their own playbooks. Are you able to comment on an ETA for that? Yeah, so sometimes you see it, but we don’t know exactly when, but definitely some time to see if we will release that feature. Mm hmm. Cool. And and then Jamie was also wondering, are there any playbooks that use campaigns instead of journeys or. Not yet we like, now have only journeys and activity units. Mm hmm. And I wanted to mention to you, because it seems it seems like Jamie has a lot that they want to see in playbooks and the experience league community is area. You can post questions and discussions and I think there’s also a type idea. So any of those product feature ideas that you have, it’s a good idea to post it there. And I believe the community managers then will scrape them in and and create tickets from them. Envy is asking what if my instance didn’t have available attributes as per the playbooks set up? What should I do in that case before importing that package? Do I need to update my schemas accordingly? Yeah, I think you know, if you know your schemas like the back of your hand, of course as a defender you would know. And when you are looking at a particular playbook instance and you look at the schema and see that, you know, let’s say the journey of a segment utilizes a particular field, let’s say, for example, I’m just making it up. Let’s say, you know, your journey depends on the date of birth of the customer. So if the date of birth is greater than, let’s say, 20 years, then only they qualify for the particular segment. Right? And then, you know, and if you don’t have a date of birth, let’s say in your union scheme, including, then you may want to do, you know, go back and add that field and then, you know, perform the import of package from use case playbooks like that. You know, you will be able to complete the entire input process in just one shot. That’s definitely a good practice. So yeah, and I recall you had mentioned earlier that you specifically didn’t allow like they move like moving a new field into the other development sandbox, right? Yeah. Like you do have to go to your other developments, add that data birth field in order to be able to then write that map right on that important. Yeah, that is. Yeah. Good, good, good question. There. V.J. is asking we see most of the use cases around abandoned process and get a message. Do you have any other types of use cases? The right way to learn quite a lot. So I would strongly urge you there are more than 45 use cases that we have right now, so urge you to install the product and use it and take a look at it and give us more feedback. But there must be more different categories of labels. Yeah, and I think one thing that will help with that is if you like, use that industry filter because as you pointed out, like you’ll notice that, you know, for abandoned Browse, there might be three very similar looking versions of that one for each industry. So if you put the industry filter on, you’d probably, you know, get a, you know, sort of remove those duplicates, as it were. Right? Absolutely. I strongly advocate that. So if you are looking for particular, even if you’re not from a particular industry and still exploring playbooks, I would still ask you to filter by specific industries and look, take a look at the Playbook Gallery page. That’s that’s a very good way to go about it. All right. I think we as I think we got through. So the questions. Are. So why don’t we move on to our unrelated cool tip and I believe really will be contributing our unrelated cool tip today. I’m awfully fond of travel and so whenever I travel for for work or or with the family, I always take the little foam earplugs because, you know, sometimes hotels can be noisy, so can other family members. So it’s always super handy to have. But the cool tip is these little foam earplugs work perfectly to fit in the little people in the hotel doors. So if you’re a little paranoid like I am sometimes, you know, it’s a great little thing you have this. I’d like to apologize to all the hotel rooms where I’ve inadvertently left these because I always forget to remove them as I’m checking out. But super handy if you didn’t bring any of these with you and you’re still curious, you know you want to block that whole I find the sugar packets or the sweetener packets that they always stick in the coffee machine, fit in that little peephole as well. So that’s, that’s great. That’s great that. Oh, really? So if, you know, if we’re at the summit in a couple of months and we want to mess with you and we know where your room is, just show up with a clothes hanger and pop that out each night and you’ll you’ll wonder. You’ll be wondering what’s going on with that. That’s the thing that’s you’re you’re a workaround for that an improved peephole blocker for for our next episode of Summit. All right. Thanks everyone, and thanks for coming on to experience league watching this episode of Experience League Live again, all of the documentation and tutorial videos for use case playbooks are on experience league. And thanks again to our guests, Rudy and Rohit. Thanks everybody.